4.2 Sprint

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

1. Date and location

The sprint will be held at the Google office in Mountain View, California, March 10-12. The address is:

Location point of contract: Martin von Zweigbergk (martinvonz), martinvonz@google.com

If you need a formal invitation for visa purpose, contact the person above.

2. Arrival Logistics

We are going to be at 501 Ellis Street, Mountain View, CA. We are going to be in the north west corner of the building. The entrance is on the west side of the building. The doors will probably be locked, but we'll check frequently in the morning if anyone is waiting. Otherwise just ping us (there's an open GoogleGuest wifi). Worst case, knock on the windows

There is plenty of parking on the south side of the building.

The best light rail stop is Middlefield, which is a 7-minute walk from the office.

3. Attendance

Everyone is welcome from core developer 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 need funds to pay flights and hotel for a few independent contributors.

Recent sprints sponsoring budgets were around $10,000.

Sponsoring Company:

• Google
• Facebook

• Please offer your sponsoring

Sponsor point of contact: Please offer your service

5. Meals

Having Food delivered for Lunch is usually preferred as it help keeping the timing under control. Dinner is usually taken outside to help people cool off after a day of work.

(Don't forget vegetarian and vegan option)

Meal point of contact: Please offer your service

6. Possible Topics

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

6.1. Steering Committee and Donations

We really need a clear (and fast) picture here. It's been frustrating that we (Bitbucket) have money to donate but nobody seems to know what to do.

6.2. Obsmarker Exchange

• Making it faster
• Making it more user friendly (in particular pruning)

6.3. friendlyhg

• We really need to do this, soon.

• Add options to core, make friendlyhg primarily an hgrc file instead of extension?

• One of the most important (KyleLippincott's opinion): a way for users to sanely enable --check on update by default.

• Homepage update (JunWu's opinion): Features better than git like revsets, templates, phases should be visible directly from homepage.

6.4. Phase/head based repoview

• A new "archived" phase?
• More efficient "computehidden" etc.
• More flexible repoview
• When they're source controlled, allows viewing the old state, useful for debugging weird DAG operations like rebase / histedit etc.

• See this mail for a general idea.

6.5. Topic 1

• (Please copy this section)

• sub topic 1.a

• sub topic 1.b

7. Sprint Notes

General overview (drop the anti spam part): https://public.etherpad-mozilla.org/p/sprint-hg4.2-NOSPAMREMOVETHATLASTPAST

The table below is an attempt to gather written summary of discussion

CategoryMeetings