Differences between revisions 3 and 4
Revision 3 as of 2010-07-26 10:17:53
Size: 2133
Comment:
Revision 4 as of 2010-07-26 10:20:30
Size: 2104
Comment:
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
== The Guidelines === == The Guidelines ==
Line 27: Line 27:
     <<BR>>
     That will enable people interested in the meeting topics to provide their

     this will enable people interested in the meeting topics to provide their
Line 32: Line 32:
   * minimize expenses <<BR>>    * minimize expenses
Line 35: Line 36:
   * consider giving periodic updates on how the meeting is going <<BR>>    * consider giving periodic updates on how the meeting is going
Line 37: Line 39:
   * think about remote participation <<BR>>    * think about remote participation
Line 42: Line 45:
     <<BR>> e.g. `d-d-a` for meetings of general development interest
e.g. `d-d-a` for meetings of general development interest
Line 47: Line 51:
 * [[http://upsilon.cc/~zack/blog/posts/2010/06/debian_meeting_guidelines_RFC/|preliminary thoughts / RFC]] on the matter, as a blog post  * [[http://upsilon.cc/~zack/blog/posts/2010/06/debian_meeting_guidelines_RFC/|preliminary thoughts / RFC]] on the matter (zack's blog post)

WORK IN PROGRESS

Debian Meeting Sponsoring Guidelines

How to have a Debian meeting without turning into a secret cabal

Sponsoring various kinds of Debian meetings (conferences, sprints, BSPs, etc.) is a good way to spend, actually invest, Debian money.

Nonetheless, Debian is a community of volunteers and we cannot rely on the fact that people will be able to attend meetings as they were "work" meetings. That is why organizers have to carefully balance the high efficiency that meetings offer (higher communication bandwidth than remote work, more focused people, more enthusiasm, more fun, etc.) with the risk of cutting out the rest of the community which cannot attend the meeting, for whatever reason.

Debian is very happy to sponsor developer meetings, but requests that the following sponsoring guidelines are respected, in order to minimize the risks outlined above.

The Guidelines

  • before the meeting

    • announce the meeting to the most relevant public list / forum
    • ideally, include a tentative agenda of the meeting in the announcement
      • this will enable people interested in the meeting topics to provide their inputs and more generally to know what is going on
  • during the meeting / meeting preparation

    • minimize expenses
      • it is a way to show respect for all people that generously donate to Debian
    • keep track of what's happening, in preparation of the overall meeting report
    • consider giving periodic updates on how the meeting is going
      • e.g. blog about what's happening day-by-day
    • think about remote participation
      • e.g. stay on a specific IRC channel and announce it
  • after the meeting

    • post meeting minutes / report to the most relevant public list / forum
      • e.g. d-d-a for meetings of general development interest

References


?CategoryDPL