<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Mar 17, 2016 at 2:13 AM, Brendan Perrine <span dir="ltr"><<a href="mailto:walterorlin@gmail.com" target="_blank">walterorlin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, 16 Mar 2016 19:30:20 +0100<br>
David Planella <<a href="mailto:david.planella@ubuntu.com">david.planella@ubuntu.com</a>> wrote:<br>
<br>
> Hi all,<br>
><br>
> Apologies for the delay, which was on my end. We've been discussing the<br>
> topic on our team call and we'd like to propose a meeting with the docs<br>
> team. While the original e-mail covers the issue in great detail, and we've<br>
> got some ideas, we'd like to get the doc's team views and come up together<br>
> with a plan moving forward.<br>
><br>
> I'd like to propose some dates for a meeting, to be reviewed around the end<br>
> of the week to pick a date. If you are a member of the docs team or if you<br>
> are interested to help, please choose the date(s) that work for you. If you<br>
> are willing to attend and the timezones are an issue, please let me know as<br>
> well, and I can add an extra choice:<br>
> <a href="http://doodle.com/poll/dqsryhnkfwgantb2" rel="noreferrer" target="_blank">http://doodle.com/poll/dqsryhnkfwgantb2</a><br>
><br>
> And an initial agenda (feel free to edit):<br>
> <a href="http://pad.ubuntu.com/doc-team" rel="noreferrer" target="_blank">http://pad.ubuntu.com/doc-team</a><br>
><br>
> Cheers,<br>
> David.<br>
><br>
> On Fri, Mar 4, 2016 at 12:03 AM, Elizabeth K. Joseph <<a href="mailto:lyz@ubuntu.com">lyz@ubuntu.com</a>> wrote:<br>
><br>
> > Hello community team,<br>
> ><br>
> > We are approaching you on behalf of the Ubuntu Documentation team to<br>
> > ask for assistance with the issues the team is undergoing.<br>
> ><br>
> > The Ubuntu Documentation team maintains the following documentation:<br>
> > – The desktop documentation at <a href="https://help.ubuntu.com/" rel="noreferrer" target="_blank">https://help.ubuntu.com/</a><br>
> > – The serverguide at <a href="https://help.ubuntu.com/" rel="noreferrer" target="_blank">https://help.ubuntu.com/</a><br>
> > – The community help wiki at <a href="https://help.ubuntu.com/community/" rel="noreferrer" target="_blank">https://help.ubuntu.com/community/</a><br>
> ><br>
> > We maintain documentation for how this documentation is maintained at<br>
> > <a href="https://wiki.ubuntu.com/DocumentationTeam" rel="noreferrer" target="_blank">https://wiki.ubuntu.com/DocumentationTeam</a><br>
> ><br>
> > The team is loosely organized in three subteams, each team taking care<br>
> > of one of the components mentioned above. In each team we have only a<br>
> > few people that can be considered active; some of those only barely.<br>
> > The state of all of the components can be described to be more or less<br>
> > stalled and in desperate the need of more contributors. With the<br>
> > string freeze for Documentation just a couple weeks away (March 17),<br>
> > at this point we risk not having updated documentation for 16.04,<br>
> > particularly for the Desktop.<br>
> ><br>
> > In the case of the community help wiki, the situation is even worse;<br>
> > not only has it encountered spam attacks lately (which only mean more<br>
> > work for the admins, who have been manually applying documentation<br>
> > "patches" that contributors send to the ubuntu-doc mailing list), it<br>
> > also has a lot of content that is completely outdated, useless and<br>
> > unstructured. Due to the spam attacks, most community members can't<br>
> > currently take any action to improve the situation.<br>
> ><br>
> > Following a meeting with the Community Council[0], we have begun to<br>
> > identify what we feel the team needs, both in the short and long term.<br>
> ><br>
> > We believe one of the major underlying issues to this situation is the<br>
> > teams inability to make decisions. The active and not so active team<br>
> > members all have their own opinion on which tasks are sensible to take<br>
> > on a certain component. This is especially problematic as sometimes we<br>
> > have had volunteers signed up to do the work, but the team has wanted<br>
> > to consider the issue further, ultimately stalling the process. When<br>
> > most efforts to improve the situation seem to be in vain, it is no<br>
> > wonder the team is not attracting new contributors either.<br>
> ><br>
> > As the Documentation team does not have a leader to steer the overall<br>
> > direction, there is no way to easily resolve the problem.<br>
> > Additionally, for various reasons, nobody from the current<br>
> > contributors is willing to step up and take the leadership position.<br>
> ><br>
> > Our request and recommendation for the community team at Canonical is<br>
> > to bring some leadership to the team from outside of the team.<br>
> > Ideally, the person would be a Canonical employee who would have part<br>
> > of their paid work assigned to working with the Documentation team. We<br>
> > think the request is fair considering the documentation is important<br>
> > and useful to many Ubuntu users and thus valuable to Canonical.<br>
> ><br>
> > We believe that a stable, fresh and adequately objective leadership<br>
> > could help the team resolve the underlying issues and ultimately,<br>
> > start growing the contributor base again. As part of and in addition<br>
> > to leading and guiding the team, the leader could take on the<br>
> > following tasks:<br>
> > – Work as a mediator with the members to resolve disagreements, be<br>
> > able to reach a consensus and get along with the work<br>
> > – Work with other Canonical employees, encouraging them to take part<br>
> > more in writing documentation, especially with the components they are<br>
> > working with themself<br>
> > – Work with the Canonical IS team to resolve technical difficulties<br>
> > the community help wiki is experiencing<br>
> ><br>
> > We feel their role as a leader on this team would not be because they<br>
> > work for Canonical, but because they are able to do the organizational<br>
> > work that is needed. Anyone able and willing to do this would be<br>
> > welcomed by us and the rest of the Documentation team. It's simply<br>
> > come to a point on the team today where we are not able to fill this<br>
> > role with a volunteer contributor.<br>
> ><br>
> > We do not think that the recommended arrangement has to be permanent<br>
> > unconditionally. Building up a team and getting it working by itself<br>
> > sometimes takes only time. We hope that with the leadership, the team<br>
> > can build up the contributor base and ultimately, find a new leader<br>
> > from within. If a leader is nominated, we will happily schedule a<br>
> > checkup meeting to see how things are going, if there are other<br>
> > actions that should be taken to grow and build up the team and if the<br>
> > outside leadership is required any more.<br>
> ><br>
> > Finally, we'd be happy to chat with anyone wishing to take on this<br>
> > role about the history of the team to give them some context for how<br>
> > we got to where we are. The Documentation team has always been quite<br>
> > small and has struggled to get contributors, but it was with this LTS<br>
> > release that we have finally hit a breaking point.<br>
> ><br>
> > Sincerely,<br>
> ><br>
> > Elizabeth K. Joseph (pleia2) and Pasi Lallinaho (knome)<br>
> ><br>
> > [0] <a href="http://irclogs.ubuntu.com/2016/03/03/%23ubuntu-meeting.html#t17:00" rel="noreferrer" target="_blank">http://irclogs.ubuntu.com/2016/03/03/%23ubuntu-meeting.html#t17:00</a><br>
> ><br>
> > --<br>
> > Ubuntu-community-team mailing list<br>
> > <a href="mailto:Ubuntu-community-team@lists.ubuntu.com">Ubuntu-community-team@lists.ubuntu.com</a><br>
> > Modify settings or unsubscribe at:<br>
> > <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-community-team" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-community-team</a><br>
> ><br>
</div></div>I think time zones are not an issue for me but more the unpredicatabilty of my schedule caused for needing to care for my father but the varience of when I will be freely available means I will probably not be able to attend but I wish I could. Belive me not knowing my own schedule is tough.<br>
<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>Thanks Brendan, and sorry to hear that :(. We'll make sure we share the summary for those who couldn't make it</div><div><br></div><div>Cheers,</div><div>David. </div></div><br></div></div>