Goaltender

Priorities for managing daily Mercurial project tasks.

1. Rationale

In the interest of reducing mpm's workload and spreading responsibilities, we're going to experiment with occasional rotations of people filling his daily roles. Hopefully this will increase the project's capacity and let mpm do some coding.

2. Priorities

In descending priority order:

• make sure queued messages are accepted/rejected
  • whitelist legitimate posters
  • drop spam, reject recruiter mail

• bug triage

  • appropriately categorize unconfirmed bugs
  • with special attention to possible regressions
  • cc relevant/guilty parties
  • ask for missing data, set NEED_EXAMPLE as necessary
• look for interesting issues on the user mailing list

• check buildbot status

• patch review
  • sync from other repos
  • review patches, in priority order
  • test
  • push

3. Schedule

The rotation is currently suspended.

• Google calendar with the official schedule

4. Setup

When you become a Goatlender, consider:

• subscribe to both mercurial-devel@mercurial-scm.org and mercurial@mercurial-scm.org (the user mailing list),

• are tracking activity of the bugzilla user on the bugtracker to track all activity automatically,
• are subscribed to all wiki update.

5. Notes

Journal of notable fact to pass the next goaltender

5.1. 2015 Week 42 (oct 12)

• durin42 is working on a new changegroup format that can transfer treemanifests
• indygreg is working on formalizing the format of streaming clones so it's more generally useful

These two topics have in common a need to interact with (and possibly extend) repository store requirements during initial clone. This is currently unsupported.

• sid0 is working on some merge driver stuff, meandering towards more in-memory operations
• foozy had more work on transaction sanity. It looked like it was starting to wind down.

---

CategoryDeveloper CategoryProject