Differences between revisions 14 and 15
Revision 14 as of 2017-07-22 01:24:10
Size: 2971
Editor: SeanWhitton
Comment: location & date
Revision 15 as of 2017-07-22 01:25:49
Size: 2897
Editor: SeanWhitton
Comment: move date back to Monday
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * when: DebCamp 2017, Wednesday 2nd August  * when: DebCamp 2017, Monday 1st August
Line 8: Line 8:
   * '''feel free to approach Policy team members before this day!'''

Debian Policy Sprint at DebCamp 2017

Location, Date

  • when: DebCamp 2017, Monday 1st August

    • ask questions about Policy process; start discussions
    • continue working on patches for remainder of DebCamp

  • where: Jardin intérieur, and #debian-policy

Participants

(please go ahead and add yourself to the list if you plan to join us for the sprint and subscribe to this wiki page to receive notifications if the details of the sprint change)

Name

username/nick

Remote via IRC?

Want to work on (optional)

Sean Whitton (policy editor)

spwhitton

N

Russ Allbery (policy editor)

rra

Y

Helmut Grohne

helmut

Y

multi-arch

Taowa Munene-Tardif

taowa

N

Goal 1

Agenda

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.

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

Reports

Acknowledgements

The sprint has been possible thanks to:


CategorySprint