Re: 4.4 Sprint Planning

[Ryan McElroy]

In what may be the last email before I fly off to Dublin,

I wanted to get some people to sign up for short "Vision Statements" on 
Friday. I have prepared an example one (that I actually plan to 
present), and I'm sharing the slides here to give an idea to people of 
what might work:


https://docs.google.com/presentation/d/1JO0RH45s0CnCsA2C2BRc5TfWGmZoWGigt6Pn7K4TXgA/edit?usp=sharing

Please respond back to me and Kostia if you're interested in presenting 
a Vision Statement before lunch on Friday. I think these statements will 
be a good way to spur discussion about possible future directions for 
the mercurial project.


Separately and less urgently, on Sunday we'll have a bit of a Tech Talk 
/ Prototype forum that it would be good to get some people signed up for 
as well (but we can do this during the sprint as well).


I'm looking forward to seeing all you sprinters in just less than a day now.

~Ryan



On 9/28/17 11:54 AM, Ryan McElroy wrote:


There's now a google spreadsheet with the Sprint Agenda previously 
discussed (in tabs "Friday" - "Sunday")


https://docs.google.com/spreadsheets/d/1U71bnBdIr915-IX8AsWIJBoZp_7wU3TjLpoeY78JGcA/edit?usp=sharing

---

On the front page "Topic Interest" is a spreadsheet I'd like to get 
everyone who is attending to fill out ASAP.


Topics and attendees copied from 
https://www.mercurial-scm.org/wiki/4.4sprint


For each topic, place a number from 3 (highly interested) to 1 
(slightly interested) based on the importance of that topic to you, or 
leave blank/0 if you are not interested in the topic


We will then be able to hopefully get people into the all the topics 
they are most interested in throughout the sprint


I have filled out my fields as an example. Kostia and I will try to 
arrange things to suit everyone as well as possible.


---

We also need people to sign up for vision statements (Friday) and tech 
talks (Sunday). I'll send out more info on those later today.


~Ryan


On 9/18/17 4:42 PM, Ryan McElroy wrote:

On 9/15/17 4:58 PM, Augie Fackler wrote:

On Sep 14, 2017, at 01:16, Gregory Szorc  wrote:

...

...


Thank you Greg and Augie for the feedback!

...


___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.mercurial-2Dscm.org_mailman_listinfo_mercurial-2Ddevel=DwIGaQ=5VD0RTtNlTh3ycd41b3MUw=Jw8rundaE7TbmqBYd1txIQ=SnzLcan4JmGU4wT2U4M5gYWKpxF4KvLz7BYwiBCDNxE=r6hn5CVKiYiS0JUIJCau6MlEKrHFcGeLfO_MmmBRE4c=


___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Re: 4.4 Sprint Planning

[Ryan McElroy]

There's now a google spreadsheet with the Sprint Agenda previously 
discussed (in tabs "Friday" - "Sunday")


https://docs.google.com/spreadsheets/d/1U71bnBdIr915-IX8AsWIJBoZp_7wU3TjLpoeY78JGcA/edit?usp=sharing

---

On the front page "Topic Interest" is a spreadsheet I'd like to get 
everyone who is attending to fill out ASAP.


Topics and attendees copied from 
https://www.mercurial-scm.org/wiki/4.4sprint


For each topic, place a number from 3 (highly interested) to 1 (slightly 
interested) based on the importance of that topic to you, or leave 
blank/0 if you are not interested in the topic


We will then be able to hopefully get people into the all the topics 
they are most interested in throughout the sprint


I have filled out my fields as an example. Kostia and I will try to 
arrange things to suit everyone as well as possible.


---

We also need people to sign up for vision statements (Friday) and tech 
talks (Sunday). I'll send out more info on those later today.


~Ryan


On 9/18/17 4:42 PM, Ryan McElroy wrote:

On 9/15/17 4:58 PM, Augie Fackler wrote:

On Sep 14, 2017, at 01:16, Gregory Szorc  wrote:

...

...


Thank you Greg and Augie for the feedback!

...
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Re: 4.4 Sprint Planning

[Ryan McElroy]

On 9/15/17 4:58 PM, Augie Fackler wrote:

On Sep 14, 2017, at 01:16, Gregory Szorc  wrote:

...

...


Thank you Greg and Augie for the feedback!

Kostia and I read over your ideas and we liked them, especially the 
"book end" part for having a summary of accomplishments at the end and 
moving the vision statements to when people have more energy to engage. 
Also, we're going to tighten up some sessions as suggested. Figuring out 
topics beforehand is something I like in principle but I think is hard 
to do in practice, though I'm happy to try some voting on topics 
beforehand (based probably on the list currently on the wiki).


Based on the feedback, we have modified the proposed schedule as a 
result (see below).


If there are no strong objections, Kostia and I will start reaching out 
to people to present various things in that "state of project" part, 
etc., and start organizing the first day topics.


## Friday

09:00-10:15: arrive, get breakfast at FB cafe, mingle
10:15-10:30: Welcome [< 5 min] and Introduction of everyone present [~ 
10 min]

10:30-10:45: State of the project
* state of the community (updates from the steering committee) [~5 min]
* state of the tooling (updates about the build bots and systems on 
mercurial-scm.org 
) 
[~5 min]
* state of the code (updates on statistics about code contributions and 
code review) [~5 min]

10:45-11:00: Status of hg deployments in the wild
* state of hg at company X (BitBucket, Mozilla, Unity, Google, FB, etc) 
[< 5 min each]
11:00-12:00: "Vision" Statements & Discussions -- directions we’d like 
to see mercurial go in the future [number and length TBD based on interest]

12:00-13:00: lunch at FB cafeteria
### Afternoon breakout sessions (topics voted on before sprint) [with 
notetakers in etherpad]

13:00-14:00: breakout session 1
14:00-14:15: break
14:15-15:15: breakout session 2
15:15-15:30: break
15:30-16:30: breakout session 3
16:30-16:45: break
16:45-17:45: breakout session 4
17:45-18:00:order Saturday breakfast [will have someone in charge]
18:00-evening: dinner at FB office, enjoy a pint in Dublin, etc

## Saturday
09:00-10:00: arrive, eat breakfast, mingle
10:00-10:15: order lunch [will have someone in charge]
10:15-11:00: Organize day 2 breakout sessions (if there is interest, 
coding groups will run simultaneous to sessions)

11:00-12:00: breakout session 1
12:00-13:00: lunch
13:00-14:00: breakout session 2
14:00-14:15: break
14:15-15:15: breakout session 3
15:15-15:30: break
15:30-16:30: breakout session 4
16:30-16:45: break
16:45-17:45: breakout session 5
17:45-18:00: order Sunday breakfast [will have someone in charge]
18:00-evening: dinner out in Dublin, enjoy the brisk Irish air, etc

## Sunday
09:00-10:00: arrive, eat breakfast, mingle
10:00-10:15: order lunch [will have someone in charge]
10:15-12:00: hackathon morning session -- low-hanging bugs, vision 
statement proofs-of-concept, etc

12:00-13:00: eat lunch
13:00-15:00: hackathon afternoon session
15:00-15:30: break, organize demos & tech talks
15:30-17:00: demos and tech talks to end on a high note
17:00-17:30: closing remarks, goodbyes
17:30-evening: freedom!


Thanks again for the feedback. We're looking forward to seeing everyone 
in 11 days!


~Ryan
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Re: 4.4 Sprint Planning

[Augie Fackler]

> On Sep 14, 2017, at 01:16, Gregory Szorc  wrote:
> 
> Thank you and Kostia for volunteering to organize things on the ground! The 
> sprints can be chaotic and I'm sure you'll make great masters-of-ceremony.

+1

> 
> While the draft schedule seems very reasonable (I'd be happy if it were the 
> final schedule), I'd like to throw out a few ideas and observations.
> 
> Experience from previous Sprints tells me that people are pretty drained by 
> the 3rd day. I like the idea of a "vision statements" session to hash out 
> project direction. But I'm a bit worried about doing that on Sunday. If we 
> have the session, I'd prefer see it done on Friday or Saturday when everyone 
> is still pretty fresh. I /think/ it would make a natural follow-up to the 
> "state of" sessions. Maybe we could do it after lunch on Friday? Although I 
> do worry about information overload if we stack all the heavy talking on 
> Friday. It might also be useful for people to have time to digest all the 
> "state of" information and to connect with others before we start thinking 
> about vision statements.

Maybe we could do state-of things quickly Friday morning after introductions, 
capped at an hour *total*, and then talk vision statement etc Saturday morning 
when we're all fresh.

> Personally, I love when things get done at the Sprint. The best Sprints for 
> me are when I walk away feeling energized about what was accomplished. 
> Something I feel has been lacking from previous Sprints is a natural "book 
> end" to the event. Sundays can kind of tail off and fizzle. What do others 
> think about some kind of "closing" event where we announce accomplishments 
> and leave on a high note?

Sounds like something we should try.

> Another area I'd like to explore is establishing more formal goals or even 
> "tracks" for the Sprint - before the Sprint starts. It would be cool if by 
> the time I get on a plane I have a pretty good sense of what we're going to 
> try to do at the Sprint. For example, perhaps a few people sign up for Python 
> 3 porting, others on storage futures, another group on UX papercuts, and 
> another group on bug triage and fixing. Being a reviewer and patch author, if 
> I have time to "page in" areas that I know will be a focus at the Sprint, it 
> should enable me - and others - to have a more productive Sprint.
> 
> Finally, I'd really like to make sure we address as many of the "only at the 
> Sprint" activities as we can. We tend to save many of our larger backwards 
> compatibility breaking decisions for Sprints. Going back to knowing what will 
> happen before the Sprint, if we could get a list of major proposals on the 
> wiki before the Sprint so everyone has time to digest them and isn't 
> surprised by the crazy ones, I think that would go a long way.
> 
> Thanks again for starting this thread, Ryan!
> ___
> Mercurial-devel mailing list
> Mercurial-devel@mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Re: 4.4 Sprint Planning

[Gregory Szorc]

On Wed, Sep 13, 2017 at 2:22 AM, Ryan McElroy  wrote:

> Greetings Mercurial Community!
>
> As hopefully everyone is aware, the 4.4 sprint (https://www.mercurial-scm.
> org/wiki/4.4sprint) is coming up in two and a half weeks. Please make
> sure you have copied your name from the "Availability" list to the
> "Attendance" list if you are planning on coming (currently our confirmed
> numbers are about half of those a year ago in Paris and I'll confirming
> numbers would also be awesome).
>
> As we have have learned from the past few sprints, a little bit of
> planning has helped us get the most out of these events. I wanted to
> propose a tentative schedule and solicit feedback now so we can hit the
> ground running when the sprint starts on Friday, September 29.
>
> Once we agree on a schedule that at least most of us are okay with, I’ll
> add it to the sprint wiki. Also, Kostia Balytskyi and I are volunteering to
> help organize the sprint on-the-ground (to help ensure we’re covering as
> much ground as possible during the three days of the sprint).
>
> # Proposed Schedule Draft
>
> ## Friday
> 9-10am arrive, get breakfast at FB office, mingle
> 10am-noon: Welcome and Status Updates
> * state of the community (updates from the steering committee)
> * state of the tooling (updates about the build bots and systems on
> mercurial-scm.org)
> * state of the code (updates on statistics about code contributions and
> code review)
> * state of hg at company X (BitBucket, Mozilla, Unity, Google, FB, etc)
> noon-1:00pm: lunch at FB cafeteria
> 1:00-3:00pm: breakout sessions on major topics, with notetakers in
> etherpad (will use wiki ideas to pre-seed)
> 3:00-3:30: break
> 3:30-5:30: breakout sessions continue
> 5:30: order Saturday breakfast
> 6:00-evening: dinner at FB office, enjoy Dublin, etc
>
> ## Saturday
> 9-10am: arrive, eat breakfast, mingle
> 10am: order lunch
> 10:30am-noon: Tech Talks – interesting project presentations (will have
> sign ups before and at sprint)
> noon-1:00pm: eat lunch
> 1:00-5:30 hackathon, fix some low-hanging bugs, implement some quick
> features, etc (needs reviewers!)
> 5:30: order Sunday breakfast
> 6:00-evening: dinner out in Dublin, enjoy the brisk Irish air, etc
>
> ## Sunday
> 9-10am: arrive, eat breakfast, mingle
> 10am: order lunch
> 10:30am-noon: Vision statements – directions we’d like to see mercurial go
> in the future (good idea?)
> noon-1:00pm: eat lunch
> 1:00-3:00pm: breakout sessions
> 3:00-3:30: break
> 3:30-5:30: breakout sessions
> 5:30-evening: freedom!
>
> Please help paint this bikeshed! All ideas will be considered.
>
> I’m looking forward to seeing many of you in a couple of weeks!
>

Thank you and Kostia for volunteering to organize things on the ground! The
sprints can be chaotic and I'm sure you'll make great masters-of-ceremony.

While the draft schedule seems very reasonable (I'd be happy if it were the
final schedule), I'd like to throw out a few ideas and observations.

Experience from previous Sprints tells me that people are pretty drained by
the 3rd day. I like the idea of a "vision statements" session to hash out
project direction. But I'm a bit worried about doing that on Sunday. If we
have the session, I'd prefer see it done on Friday or Saturday when
everyone is still pretty fresh. I /think/ it would make a natural follow-up
to the "state of" sessions. Maybe we could do it after lunch on Friday?
Although I do worry about information overload if we stack all the heavy
talking on Friday. It might also be useful for people to have time to
digest all the "state of" information and to connect with others before we
start thinking about vision statements.

Personally, I love when things get done at the Sprint. The best Sprints for
me are when I walk away feeling energized about what was accomplished.
Something I feel has been lacking from previous Sprints is a natural "book
end" to the event. Sundays can kind of tail off and fizzle. What do others
think about some kind of "closing" event where we announce accomplishments
and leave on a high note?

Another area I'd like to explore is establishing more formal goals or even
"tracks" for the Sprint - before the Sprint starts. It would be cool if by
the time I get on a plane I have a pretty good sense of what we're going to
try to do at the Sprint. For example, perhaps a few people sign up for
Python 3 porting, others on storage futures, another group on UX papercuts,
and another group on bug triage and fixing. Being a reviewer and patch
author, if I have time to "page in" areas that I know will be a focus at
the Sprint, it should enable me - and others - to have a more productive
Sprint.

Finally, I'd really like to make sure we address as many of the "only at
the Sprint" activities as we can. We tend to save many of our larger
backwards compatibility breaking decisions for Sprints. Going back to
knowing what will happen before the Sprint, if we could get a list of major
proposals on the