3.8 Sprint

Subscribe to this page so you don't miss updates!

1. Date and location

The sprint will take place Friday March 18, 2016 to Sunday March 20 at Mozilla's San Francisco office.

2 Harrison St. San Francisco, CA 94105

The entrance is under a big Mozilla sign along Embarcadero Blvd facing the water and the bay bridge.

Please arrive no earlier than 0900 PDT on Friday. Official start time is no later than 1000.

Arriving via public transit or walking is highly preferred. There is a N and T light rail stop in front of the office. MUNI costs $2.25/ride (exact change).

If you drive, there is an underground garage in the adjacent building (entrance on Folsom St.). Paid street parking with meters is available, but you are limited to a few hours. The parking meters are disabled on Sundays and parking should not be a problem in the neighborhood.

2. Meals

2.1. Lunch

• Friday: Mozilla will provide pizza and wings on Friday as part of their regular lunch program. There will be gluten free and vegetarian options.
• Saturday: Atlassian will provide pizza (since it's easy to have vegetarian and vegan options).
• Sunday: Not planned yet.

2.2. Dinner

• Friday: Open to ideas.
• Saturday: Osha Thai (vegetarian and vegan options).
• Sunday: Probably a free-for-all since most people are leaving.

3. Attendance

Everyone is welcome from core to aspiring contributor. Attending a Mercurial sprint is usually a good way to kickstart your contributions are you'll get a large amount of help available for 3 days.

4. Sponsors

We will probably need to find some funds to get flights and hotel for a few independent contributors.

Last sprint sponsoring budget was $10,000 contributed equally from Google and Facebook.

5. Possible Topics

Important things we want to discuss: (add your own)

5.1. User Interface and Experience

• feature branch workflow (FeatureBranchesStruggle and TopicPlan)

• UI related discussion,
  • Interactive UI
  • pager into core/by default
  • color into core/by default

5.2. New Features and Improvements

• ExtensibleDiscoveryPlan

• Continue discussion for commit custody

5.3. Data Format and Performance

• PackedRepoPlan and alternate client storage

• Worker processes on Windows

• State of PyPy support (CFFI) ( requires VC with Fijal, South Africa)

• Bos's SQLite revset PoC
• lz4 and other compression formats

5.4. Mercurial Project

• Patch Flow

• mpm/transition

• packaging work: hardcode chg install path?
• bitbucket updates

• MercurialBookPlan ( requires VC with Mathias De Maré, Belgium) *hgbook2 status

• SummerOfCode/2016

• PerformanceTrackingSuitePlan ( requires VC with Logilab people, France)

• ExperimentalExtensionsPlan

  • Defining criteria,
  • Steps for getting sparse/narrow/holey clones into core,

5.5. Persistent Bugs

• hg revert file/directory behavior
• bookmarks lack of transactionality

5.6. Discussion with remote people

Please update these sections with constraint and time proposal.

The sprint is happening California time, currently UTC-7. from Friday to Sunday 10h → 18h for sure. I don't expect Friday morning to be much schedulable.

5.6.1. Discussion around hgbook

There have been a lot of good progress and interrest around this.

Remote attendee: - Mathias de Maré, Belgium, Belgium (UTC+1)

5.6.2. Discussion around PyPy and CFFI

Facebook is contracting people to get an idea of what it would take to run Mercurial on Pypy. The most fuzzy part if the handling of C code using CFFI

Remote attendee: - Maciej Fijalkowski, South Africa (UTC+2)

5.6.3. Discussion around Mercurial Performance tracking

Facebook is also contracting people to get a proper performance tracking suite for Mercurial so that we can start tracking performance change overtime. I expect people to have opinions and idea around this.

Remote attendee: - David Douard, France (UTC+1) - Philippe Pepiot, France (UTC+1)

6. Bulk Bikeshedding

Name and details we want to fight over:

7. Sprint Notes

The format of this sprint was a bit different than the previous one as we broke up into small chatting session much more.

The table below is an attempt to gather written summary of all of them

---

CategoryMeetings