ubuntu-manual team mailing list archive

[Thomas Corwin <dog1489@xxxxxxxxxxx>]

Hello Patrick,

> I'll admit that I'm guilty of letting my section slide a bit this past
> cycle. Luckily enough, it's a section that doesn't change very much.
> I bit off more than I could chew, and time flew by faster than I
> expected. 

I think we all did that this time around. We have about 12 weeks before the 14.04.1 release, so we have 12 weeks to redeem ourselves of the slack we have all put in. I let mine go a bit too. 

> That being said, I'd like to make a suggestion for the upcoming cycles.

Suggestions are always a great thing!

> The suggestion is to have bi-weekly status updates starting at the
> beginning of the cycle. Mainly something along the lines of 
> "These sections are being actively worked on." 
> "These sections haven't been worked on in the past two weeks." 
> "These are the sections that are still available to be worked on." 
> And more importantly "Here's where we are in the schedule, and here's
> the amount of time until the next milestone."

These would be great things to have during this cycle, but we had no coordinators for the 14.04 cycle, so now I've put myself in the position as the Authors Coordinator (unless someone objects, then I will step down). These will definitely be used on Atleast a weekly basis, if not a daily basis of some sort. 

>  (I could have used the
> last one, because I kept thinking "Oh I've got plenty of time." and the
> next thing I knew, Hannie was emailing us about the end of the author
> phase.)
> 

Exactly what happened to me. I kept thinking that.

> You could also put a note in saying something along the lines of "If
> you've completed your section, and have a bit of free time, please take
> a look at one of the available sections."

This will also be mentioned for week one (which I will be considering next Monday, for this week I'm considering preparation), as well as on a bi-weekly basis.

> 
> Along these lines, we might want to get a bit more detailed in the
> milestones and/or emails. Something like by week 2 or 3, you should have
> the components installed and working, and have downloaded the
> branch(es). By weeks 4 or 5, you should have started looking at your
> sections, and made minor changes (fixing obvious errors, removing things
> that we know won't be there anymore, etc). And so on, and so on.

I'm still working on the weekly schedule, and will have it posted before the end of this week as a Google Document. 

These were great ideas Patrick. I will be incorporating all of them this mini-cycle. 

Thanks!
Thomas Corwin