Differences between revisions 11 and 12
Revision 11 as of 2010-10-08 14:04:15
Size: 3323
Comment:
Revision 12 as of 2012-01-22 20:34:43
Size: 5007
Comment: document hardware sponsoring guidelines
Deletions are marked like this. Additions are marked like this.
Line 56: Line 56:
Do you have '''comments''' ? Please mail them to <<MailTo(leader AT debian DOT org)>>. == Hardware Guidelines ==

Buying hardware that can help improving specific parts of Debian is another good way of spending Debian money.
We routinely buy servers and other parts of the Debian Project infrastructure administered by [[Teams/DSA|DSA]].

But buying project '''hardware to be used by individual developers''' can be done as well. If you're working
on a specific project area and you feel like your work is hindered by the fact you lack specific hardware or
other material, the project can buy it for you in an attempt to remove the obstacle.

As usual, the DPL will be in charge of deciding whether to grant the request or not.

The following general principles will drive the choice:

 1. the request should be motivated (and the motivation will be disclosed), i.e. not "can the project buy $foo for me?", but "I'm working on $bar, but it is a PITA because I lack $foo and I can't afford buying it myself"
 1. once again, '''transparency''' is the rule: you should take care of periodically informing fellow developers of what you're doing with the hardware the project both for you (the usual "here is my last hack" blog post / mail would do)

As people might feel shy asking, hardware sponsoring can also go [[http://www.corsac.net/?rub=blog&post=1541|the other way around]].
If you think fellow developers might benefit from some hardware or other material to improve specific parts of Debian,
you can '''advocate them for hardware sponsoring''': discuss with them or with the DPL first, whatever you think is best.
Line 60: Line 79:
While the above guidelines have been written with meeting funding in mind, they are way more general. While the above guidelines have been written with specific purposes in mind, they are way more general.
Line 64: Line 83:
 * E.g.: if you get sponsored hardware for yourself (e.g. for porting), be public about the fact you
   got the hardware and take care of sending reports from time to time about what you do with it.
 
* E.g.: if you go to attend a conference sponsored by Debian, ensure to inform the project that you
  
are going (that would be the good moment to ask from inputs from others too!) and send a report
  
once you're back.
 * E.g.: if you get sponsored hardware for yourself (e.g. for porting), be public about the fact you got the hardware and take care of sending reports from time to time about what you do with it.
 * E.g.: if you go to attend a conference sponsored by Debian, ensure to inform the project that you are going (that would be the good moment to ask from inputs from others too!) and send a report once you're back.
Line 70: Line 86:
Line 74: Line 91:
 * [[http://www.corsac.net/?rub=blog&post=1541|on advocating people for hardware sponsoring]] (corsac's blog post)


== Comments ==

Do you have '''comments''' ? Please mail them to <<MailTo(leader AT debian DOT org)>>.

Debian Sponsoring Guidelines

Meeting 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 are neither absolute, nor complete, they are ... just general guidelines ! In case you hit a corner case not addressed by them please discuss it with <leader AT debian DOT org>.

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

    • optimize expenses, don't waste money!
      • 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
        include mention of who took part in the meeting

Hardware Guidelines

Buying hardware that can help improving specific parts of Debian is another good way of spending Debian money. We routinely buy servers and other parts of the Debian Project infrastructure administered by DSA.

But buying project hardware to be used by individual developers can be done as well. If you're working on a specific project area and you feel like your work is hindered by the fact you lack specific hardware or other material, the project can buy it for you in an attempt to remove the obstacle.

As usual, the DPL will be in charge of deciding whether to grant the request or not.

The following general principles will drive the choice:

  1. the request should be motivated (and the motivation will be disclosed), i.e. not "can the project buy $foo for me?", but "I'm working on $bar, but it is a PITA because I lack $foo and I can't afford buying it myself"
  2. once again, transparency is the rule: you should take care of periodically informing fellow developers of what you're doing with the hardware the project both for you (the usual "here is my last hack" blog post / mail would do)

As people might feel shy asking, hardware sponsoring can also go the other way around. If you think fellow developers might benefit from some hardware or other material to improve specific parts of Debian, you can advocate them for hardware sponsoring: discuss with them or with the DPL first, whatever you think is best.

General Guidelines

While the above guidelines have been written with specific purposes in mind, they are way more general. The underlying principle is that if you use Debian money, you should be transparent in the way you use them. That principle is general, and applies to any kind of Debian money usage.

  • E.g.: if you get sponsored hardware for yourself (e.g. for porting), be public about the fact you got the hardware and take care of sending reports from time to time about what you do with it.
  • E.g.: if you go to attend a conference sponsored by Debian, ensure to inform the project that you are going (that would be the good moment to ask from inputs from others too!) and send a report once you're back.
  • etc ...

References

Comments

Do you have comments ? Please mail them to <leader AT debian DOT org>.


CategoryDpl