4.8 Sprint

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

1. Date and location

The sprint will be held October 12-14, 2018 at Google Stockholm in Sweden.

The address is Kungsbron 2, 111 22 Stockholm, Sweden (Google Maps).

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

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

1.1. Arrival Logistics

Google reception is open from 8:00am to 5:00pm on Friday (Street view, picture). This is where you can meet a Google employee who will accompany you inside. Access details for Saturday/Sunday will be announced on Friday.

1.2. Food etc.

Breakfast on Friday will be provided at the Google cafeteria between 8:00am and 9:30am. You will need to be accompanied by a Google employee.

• Saturday/Sunday breakfast will not be provided.

• Friday/Saturday/Sunday lunch will be provided.

• Dinner will not be provided on any day.

Wifi is available inside the Google office.

2. 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.

3. Sponsors

We need funds to pay flights and hotel for a few independent contributors.

Sponsoring Company:

• Facebook ($5,000)
• Google ($5,000)

• Please offer your sponsoring

Sponsor point of contact: Martin von Zweigbergk (martinvonz), martinvonz@google.com Please offer your service

4. Meals

Having Food delivered for Lunch is usually preferred as it helps keep 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

5. Possible Topics

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

5.1. Topic 1

• sub topic 1.a

• sub topic 1.b

5.2. hg undo / hg rewind

5.3. Stable API/ Maintaining extensions like hg-git

After every major release, hg-git gets broken and there are user complains about that. We are loosing users because of that fact which is not good. Either we should establish a stable API or we should think about what we can do to make sure hg-git works until we come up with better solution like hgit. Some ideas:

• We have couple of weeks code freeze, we make sure that all out of tree extensions work with new version of mercurial
• Add a buildbot to test out of tree extensions with default/stable branch

(added by Pulkit)

5.4. hg/git

(I think Augie?) brought up the idea that "hg could become the best git client out there", which would mean a significant adoption growth for the project. Should this be a priority?

5.5. Getting a Code of Conduct in place

Seeing recent news about Linux development, I checked whether we have a code of conduct or not and I was unable to find one. CoC is very important and having one in place can increase the confidence of new or potential contributors in the community.

(added by Pulkit)

5.6. Improving UI, UX of partial clones and selective checkout

We should discuss about the UI of partial clones, interaction between narrow+shallow(remotefilelog) and also improving the UI of selective checkout i.e. sparse. Maybe we can come up with a single command which handles the tracked files in the repository.

(added by Pulkit)

5.7. absorb tweaks

Absorb is in hgext now. Have people used it? Augie has some proposed UI changes: make the default behavior be to print the -pn output and then ask the user if that looks okay.

5.8. performance tracking

We continued our work on performance tracking. It is now simpler to use by individual developers to test their development. Doing a small demo of how it works and an "install party" seems like a good idea.

5.9. State of Mercurial at Bitbucket

I (Erik) would like to give an update on Mercurial usage at Bitbucket, including common workflows and pain points among the general public. Since I unfortunately won't be able to be attend in person, I offer to dial in from SF on Saturday morning (my morning, your afternoon). I imagine 30 minutes or so would be sufficient.

5.10. Experimentation around test runner

I've been experimenting around the test runner and would like to show a demo of my experimentation.

(added by Boris)

6. Sprint Notes

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

A copy of the etherpad is available at 4.8sprint/Notes.

I'm sharing 360-degree photos in "Mercurial 4.8 Sprint in Stockholm" (by foozy)

---

CategoryMeetings