Sprint Schedule and Organization

[Gregory Szorc]

> On Mar 8, 2017, at 12:30, Ryan McElroy <rm at fb.com> wrote:
> 
> At the last sprint, we did some basic organization and I think it helped make the sprint run more smoothly overall. I think we should plan on doing this again, unless there are objections.
> 
> Simon Farnsworth and I are volunteering to do the organizational work to make this happen.
> 
> Last time, things that worked well (in my opnion -- please chime in with your thoughts as well!)
> 
> * Presentations in the morning
> * Organized "tracks" of discussions through the day
> * People taking notes on each topic so others could see what happened
> 
> However, I think some things could have worked better. Ideas for improving these parts would be welcome:
> 
> * Structuring the discussion tracks
> * Making sure people can attend topics they are interested in
> * Unstructured "hack" time in the afternoon
> 
> I like the idea of unstructured time, but I felt it could be better used. Any ideas for that?

I'd like to propose establishing mini-projects/goals for the weekend and have time available for small groups to focus on those. Some ideas include:

* templatize all of the things
* Python 3 porting
* Friendly HG
* hg display
* Rewriting API / in-memory rewriting

If we have 2-4 people paired with a reviewer doing focused development, we could probably crank out a number of useful improvements during the weekend.

> 
> If there are no objections in the next day or so, Simon and I will send out a proposed schedule that we can try on for size.
> 
> Thanks in advance for sharing any thoughts you have on this!
> 
> ~Ryan and Simon
> 
> 
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel