|
Size: 4110
Comment:
|
← Revision 72 as of 2020-03-16 10:36:48 ⇥
Size: 5161
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 15: | Line 15: |
| The print will be held in Paris on March 27th - 29th. Two company offered hosting in Paris. Logilab and Mozilla, the choice on the actual hoster is not done yet. (depends on Connor availability) || |
The sprint will be held in '''Paris''' on '''March 27th - 29th'''. /!\ Current plan are cancel. We will reschedule another sprint later. /!\ The sprint will host at: [[https://www.openstreetmap.org/search?query=%20117%20quai%20de%20Valmy%20Paris%2075010%20France%20#map=19/48.87551/2.36288|Mozilla Paris|]], 117/119 quai de Valmy, Paris 75010, France. Location point of contact: '''Chloé Rebattu''' ``contact AT octobus.net`` For the record, other location options were: || Location || Host || Point of Contact || Feb 21-23 || Feb 28-Mar 1 || Mar 6-8 || Mar 13-15 || Mar 20-22 || Mar 27-29 || Notes || || Espoo, Finland || Open-Xchange || Jeff Sipek || (./) || (./) || (./) || (./) || (./) || (./) || || || Antwerp, Belgium || Nokia || Mathias De Maré || {X} || (./) || {X} || (./) || (./) || (./) || || || Paris, France || Mozilla || Connor Sheehan || (./) || {X} || {X} || (./) || (./) || (./) || Availability tentative (depends on Connor availability) || |
| Line 19: | Line 37: |
| Location point of contact: (Location not picked yet) | |
| Line 21: | Line 38: |
| If you need a formal invitation for visa purposes, contact the person above. | If you need a formal invitation for visa purposes, contact contact@octobus.net . |
| Line 34: | Line 52: |
| || AugieFackler || Pittsburgh || {X} || || || (copied from availability dates|| || JSipek || Boston area || {X} || || || (copied from availability dates|| || Logilab || Paris || {X} || || || (copied from availability dates|| || Mathiasdm (Nokia) || Antwerp || {X} || || || (copied from availability dates|| || Manuel Jacob || Leipzig || maybe || || Martin von Zweigbergk || Bay Area || {X} || || || (copied from availability dates|| || KyleLippincott || SF Bay Area || {X} || || || (copied from availability dates|| || RodrigoDamazio || SF Bay Area || {X} || || || (copied from availability dates|| || [[Pierre-YvesDavid]] || Paris || {X} || || || (copied from availability dates|| || Raphaël Gomès || Lyon, FR || {X} || || || (copied from availability dates|| || Pulkit Goyal || || (./) || || || (copied from availability dates|| || Sushil Khanchi || India || (./) || || || (copied from availability dates|| || Gregory Szorc || SF Bay Area || {X} || || || (copied from availability dates|| || AntonShestakov || || (./) || || || (copied from availability dates|| || Yuya Nishihara || Tokyo || maybe || || || (copied from availability dates|| |
|| Logilab || Paris || {X} || || || || || [[Pierre-YvesDavid]] || Paris || {X} || || || || || AntonShestakov || || (./) || || || || |
| Line 83: | Line 89: |
| === Topic 1 === | === Tags === |
| Line 85: | Line 91: |
| * <!> sub topic 1.a * <!> sub topic 1.b |
Multiple large users have their own overwrite of Mercurial tag system. It is worth reviewing what and why they do it and maybe make plan to improve the situation accordingly. === Releases === Right now durin42 is doing all the releases, and has some help doing release notes. It'd be nice to have others start rolling releases. Is anyone interested? Can we automate this more? === Obsshelve === What needs to be done to get this to replace current shelve? === Replication-friendly repository format === durin42 is interested in (and has a handwave of a design for) a storage layer that would be replication-friendly. Basically, "how could we restructure repo storage so that it would be safe to put in {Dropbox,CIFS,etc}"? === More command "namespace" === Right now we have the normal namespace and the "debug" namespace. It would be useful to have a couple more explicit namespace with their own guarantee. For example one dedicated to maintenance command (debugupdatecache, debugrebuildstate, debugupgraderepo, etc…) and one for other tooling (eg: debugcompletion) === Google's --changeset-as-wdir feature === Multiple contributors from google are trying to have various existing commands being able to consider a revision in place of the working copy. This is an interesting and powerful idea that is worth discussing in greater length. See [[RevisionAsWDirPlan|plan page]]. |
When using this template, review all sections marked with
Note:
This page is primarily intended for developers of Mercurial.
5.4 Sprint
Contents
![/!\](/moin-static/modernized/img/alert.png "/!\"){kind=small}
Subscribe to this page so you don't miss updates!
1. Date and location
The sprint will be held in Paris on March 27th - 29th.
Current plan are cancel. We will reschedule another sprint later.
The sprint will host at:
Mozilla Paris, 117/119 quai de Valmy, Paris 75010, France.
Location point of contact: Chloé Rebattu contact AT octobus.net
For the record, other location options were:
Location |
Host |
Point of Contact |
Feb 21-23 |
Feb 28-Mar 1 |
Mar 6-8 |
Mar 13-15 |
Mar 20-22 |
Mar 27-29 |
Notes |
Espoo, Finland |
Open-Xchange |
Jeff Sipek |
|
|
|
|
|
|
|
Antwerp, Belgium |
Nokia |
Mathias De Maré |
|
|
|
|
|
|
|
Paris, France |
Mozilla |
Connor Sheehan |
|
|
|
|
|
|
Availability tentative (depends on Connor availability) |
Paris, France |
Logilab |
Katia Saurfelt |
|
|
|
|
|
|
|
If you need a formal invitation for visa purposes, contact contact@octobus.net .
1.1. People Availability
2. Attendance
fill me when a location and date have been picked
Everyone is welcome from core developers to aspiring contributors. Attending a Mercurial sprint is usually a good way to kickstart your contributions as you'll get a large amount of help available for 3 days.
Name |
Coming from |
Need funding |
Hotel |
In Town Dates |
Notes |
Logilab |
Paris |
|
|
|
|
Paris |
|
|
|
|
|
|
|
|
|
|
3. Sponsors
We need funds to pay for flights and hotels for a few independent contributors.
Recent sprints sponsoring budgets were around $10,000.
Sponsoring Company:
- Please offer your sponsoring
Sponsor point of contact: 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 options)
Meal point of contact: Please offer your service
Day |
Meal |
Details |
Organiser (when relevant) |
Friday |
Lunch |
|
|
Friday |
Dinner |
|
|
Saturday |
Lunch |
|
|
Saturday |
Dinner |
|
|
Sunday |
Lunch |
|
|
Sunday |
Dinner |
|
|
5. Possible Topics
Important things we want to discuss: (add your own)
5.1. Tags
Multiple large users have their own overwrite of Mercurial tag system. It is worth reviewing what and why they do it and maybe make plan to improve the situation accordingly.
5.2. Releases
Right now durin42 is doing all the releases, and has some help doing release notes. It'd be nice to have others start rolling releases. Is anyone interested? Can we automate this more?
5.3. Obsshelve
What needs to be done to get this to replace current shelve?
5.4. Replication-friendly repository format
durin42 is interested in (and has a handwave of a design for) a storage layer that would be replication-friendly. Basically, "how could we restructure repo storage so that it would be safe to put in {Dropbox,CIFS,etc}"?
5.5. More command "namespace"
Right now we have the normal namespace and the "debug" namespace. It would be useful to have a couple more explicit namespace with their own guarantee. For example one dedicated to maintenance command (debugupdatecache, debugrebuildstate, debugupgraderepo, etc…) and one for other tooling (eg: debugcompletion)
5.6. Google's --changeset-as-wdir feature
Multiple contributors from google are trying to have various existing commands being able to consider a revision in place of the working copy. This is an interesting and powerful idea that is worth discussing in greater length. See plan page.
6. Sprint Notes
General overview (drop the anti spam part): https://public.etherpad-mozilla.org/p/sprint-hgx.y-NOSPAMREMOVETHATLASTPAST ( update URL)
The table below is an attempt to gather written summary of discussion
Session theme |
notes/result |
People who know what happened |