Differences between revisions 6 and 7
Revision 6 as of 2017-06-25 05:33:34
Size: 2361
Editor: SeanWhitton
Comment: note about remote participants
Revision 7 as of 2017-07-04 06:42:57
Size: 2426
Editor: SeanWhitton
Comment: add link to announcement
Deletions are marked like this. Additions are marked like this.
Line 41: Line 41:
 * announcement: TBC  * announcement: https://lists.debian.org/debian-devel-announce/2017/07/msg00001.html

Debian Policy Sprint at DebCamp 2017

Location, Date

  • when: DebCamp 2017, day TBC

  • where: TBC, and #debian-policy


(please go ahead and add yourself to the list if you plan to join us for the sprint; use 'via IRC' to indicate if you will participate remotely)

  • Sean Whitton <spwhitton> (policy editor)

  • Russ Allbery <rra> via IRC (policy editor)


We've two goals. Sprint participants can work on either.

(1) Clear backlog of uncontroversial changes to Policy

We want to clear the backlog of uncontroversial changes to Policy, which makes up the greater part of bugs filed against debian-policy. They are each at different stages of the PolicyChangesProcess, but it would not take much to get them moved along and committed to the debian-policy git repo.

Bringing this key part of our documentation up-to-date would save lots of volunteer time across Debian. There will be a policy editor physically present at the sprint, with commit access to the debian-policy git repo, and at the end of DebConf we plan a "special edition" release of Policy, closing as many of these uncontroversial bugs as we can. How many can we close? :)

(2) Draft text for "big ticket" Policy updates

Debian Policy does not document the following important parts of Debian. We want to bring together both those who already understand these mechanisms, and those who are new to them, to produce concise and useful explanations of our preexisting best practices.

  • the current state of init systems (835520)

    • systemd
  • multiarch (687900, 749826)

  • dpkg triggers (582109)

    • replace various obsolete recommendations to use postinst maintscripts
  • reproducible builds (844431)

  • FHS 3.0 (787816)

It probably makes sense to use gobby for working on the draft text.



The sprint has been possible thanks to: