2.3 Sprint

Planning the 2.3 sprint

1. Date and location

The sprint will run from Friday morning, May 11 to Sunday evening, May 13. Our host will be Unity Technologies in Copenhagen, Denmark. Unity's office is located at:

Livjægergade 17

Yardhouse, 1st Floor

2100, København Ø

2. Attendees

Subscribe to this page to get email updates!

Attendance is open to all Mercurial contributors. We will try to reimburse travel costs for core contributors.

3. Hotel

We'll be staying at the Adina near Unity. Current confirmed bookings are as follows:

Note that the booking above are for nights in the hotel, ie most people need to check out Monday morning. Talk to mpm if you need updates.

4. Directions

4.1. General

Both the Adina hotel and the Unity office are within short walking distance of Østerport station.

Here is a map containing the hotel, Unity Technologies and the closest train station to the hotel, the Østerport station. Transportation options from the Copenhagen airport are either taking the train to Østerport (as described below) and walking, or a taxi from the airport. Taxi fare should be about 300 Kroner = $53 USD.

4.2. Trains

Regional trains go from the station beneath airport Terminal 3. You can purchase a train ticket at the automated machines to the side of the DSB ticket booth in Terminal 3. Tickets, valid for 3 fare zones, cost 36 DKK. A 10-ride discount card is available at 190 DKK; it must be stamped in the yellow machine on the platform prior to boarding the train or Metro. Tickets and discount cards are valid for one hour. You need to use a card with a PIN, so most US credit cards won't work. A debit card worked fine for durin42 last year. Also note that most things not only require a pin, but they generally require a 4-digit PIN and aren't set up for PINs that aren't 4 digits.

The most direct train is the Øresunds Train, which will go directly to Østerport Station where you need to get off. This train does not leave that frequently though. Another option is to take the Metro, also from Terminal 3, to Nørreport Station and change there for the S-Train. Catch any northern bound S-train, and get off at the next stop: Østerport Station.

4.3. Taxi

Taxis are usually available waiting in a line outside of the airport, but you can also call for one:

Amager Øbro Taxi

www.amagerobrotaxi.dk

Telephone no. +45 32 51 51 51

4.4. Other Information

A good site for traveling by train and buses in CPH is www.dsb.dk

Beware that Denmark does not use the Euro and Euros are not likely to be accepted outside of the airport.

Some taxis (and restaurants/shops, for that matter) do not accept cards other than the Danish national credit card (Dankort), so it's a good idea to ask beforehand if you are expecting to pay with a credit card (durin42's experience last year was that nobody outside the airport accepted cards without a PIN, and a 4-digit PIN is generally needed -- machines are typically designed to assume 4 digits). There are of course several ATMs in the airport.

If you find yourself stuck, lost, or otherwise in need of help, you can call or SMS natosha (+45 2829 9411) or Tak (+45 2829 8762), who both live in Copenhagen and work at Unity.

5. Local info

Pre-paid data SIM info for Denmark.

If you have an unlocked GSM phone, I hear you can get a local number via a prepaid SIM card for around 100 DKK (~$20 USD) in the Copenhagen airport. Two providers I've heard of that have this are Telia and TDK

6. Schedule

Breakfast, lunch, and dinner will be served in the office on Friday, Saturday, and Sunday. Meal times are:

• Breakfast: 8:00 - 9:00
• Lunch: 12:00 - 13:00
• Dinner: 18:00 - 19:00

We will start the day working at 9 AM every morning and continue on until we feel like stopping.

7. Sponsors

Judging from previous sprints, we'll need about $5000USD in sponsorship for hotel and airfare.

Possible sponsors:

• Mozilla
• Facebook

8. Possible Topics

Suggested topics for discussion include:

• Making Mercurial perform well at scale
• Areas where we are missing tools/functionality in the every day, real-world, user's workflow and how to fix them. Ideas include:
  • Useful, 'human-readable' view for large merges
  • Integrated stash-oriented workflow (that doesn't rely on buggy or unmaintained 3rd-party extensions -- see Attic or Shelve extensions for possible inclusion?)

• ConsensusMerge

• what to do about unloved code (fetch, hgk, etc.)
• tackling code debt
• short release cycles
• improve extension development and testing

• ImprovingCollaboration

• Obsolete markers implementation for Core

8.1. Document Performance Characteristics

What is the complexity (in terms of number of changesets/named branches/heads/tags) of commands such as:

• hg commit: O(1)?

• hg log -r 100: O(1)?

• hg log -b foo: O(number-of-changesets)?

• hg log -r "branch(foo)": O(number-of-changesets)?

• hg branches: O(number-of-branches)?

• hg tags: O(number-of-tags)?

8.2. Extensions in Core

Could we turn some extensions on by default — extensions that most people will want to use anyway?

Put an extension here and let us know if you find it useful. This doesn't mean that we should turn it on by default, but it can help us identify candidates for being included in core:

Third-party extensions that provide important functionality:

• HisteditExtension

• AtticExtension or ShelveExtension

9. Notes

http://titanpad.com/mercurial23

10. Proceedings

• Mercurial 2.3 day 0 - Logilab.org Blog

• Mercurial 2.3 sprint by Henrik Stuart

• Photos from the sprint by Martin Geisler

CategoryMeetings