Difference between revisions of "BugBountyProgram"

From Apache OpenOffice Wiki
Jump to: navigation, search
(New page: = Draft for a OpenOffice.org Bug Bounty Program = * program is running from September 15th to December 15th 2008, 10000 € are available in this time. * for every bug fix 33 € (about ...)
 
Line 1: Line 1:
= Draft for a OpenOffice.org Bug Bounty Program =
+
= Draft for a OpenOffice.org Bug Bounty Programme =
  
* program is running from September 15th to December 15th 2008, 10000 € are available in this time.
+
= Join the OpenOffice.org Bounty Hunters! =
  
* for every bug fix 33 € (about 50$) will be payed
+
* The Bounty Programme will start on September 15th and will finish either on December 15th 2008, or when the total bounty money (10000 €) has been spent, whichever comes first.
  
== Scope ==
+
* The Programme will pay a minimum of 33 € (about 50$) for every bug fixed.
  
* encourage code contributions (e.g. bug fixes)
+
== Why are we doing this? ==
  
* attract new developers (students and pupils), software professionals are not eligible for the program
+
* to clear up outstanding bugs
  
* reduce bug count
+
* to encourage code contributions (e.g. bug fixes) :-)
  
== how to apply ==
+
* to attract '''new''' developers (students and pupils). Sorry, professional software developers or existing contributors are not eligible for the Programme
  
* a minimum effort has to be in the fix to avoid to have "no brainers" included in this program, for this reason:
+
== How to apply ==
  
* propose a bug fix on <to-be-specified> wiki page, any [[DomainDeveloper]] is been able to confirm that this is a nontrivial fix
+
Trivial, "no brainers" are excluded from the Programme. To make sure your work will qualify:
  
* a domain developer can propose to raise the payment to 100, 200 or 500 € according to the difficulty of the bug fix.
+
* propose a bug fix on <to-be-specified> wiki page
 +
 
 +
* wait for any [[DomainDeveloper]] to confirm that this is a non-trivial fix
 +
 
 +
* a domain developer can also propose a higher payment of 100, 200 or 500 € according to the difficulty of the bug fix.
  
 
== conditions ==
 
== conditions ==
  
* bug fix has to be integrated into the development code line, either via cws or via patch gateway of an established contributor
+
* Your bug fix has to be integrated into the development code line, either via cws or via patch gateway of an established contributor
 +
 
 +
* You must have a PayPal account to receive any payment
 +
 
 +
* By entering, you are certifying you are eligible to take part and that it is legal for you to do so
 +
 
 +
* By entering, you accept that the decision of the Programme team is final
  
* paypal account
+
* Code received after the Bounty is exhausted will not be liable for a payment, so get your entries in early!

Revision as of 19:16, 29 August 2008

Draft for a OpenOffice.org Bug Bounty Programme

Join the OpenOffice.org Bounty Hunters!

  • The Bounty Programme will start on September 15th and will finish either on December 15th 2008, or when the total bounty money (10000 €) has been spent, whichever comes first.
  • The Programme will pay a minimum of 33 € (about 50$) for every bug fixed.

Why are we doing this?

  • to clear up outstanding bugs
  • to encourage code contributions (e.g. bug fixes) :-)
  • to attract new developers (students and pupils). Sorry, professional software developers or existing contributors are not eligible for the Programme

How to apply

Trivial, "no brainers" are excluded from the Programme. To make sure your work will qualify:

  • propose a bug fix on <to-be-specified> wiki page
  • a domain developer can also propose a higher payment of 100, 200 or 500 € according to the difficulty of the bug fix.

conditions

  • Your bug fix has to be integrated into the development code line, either via cws or via patch gateway of an established contributor
  • You must have a PayPal account to receive any payment
  • By entering, you are certifying you are eligible to take part and that it is legal for you to do so
  • By entering, you accept that the decision of the Programme team is final
  • Code received after the Bounty is exhausted will not be liable for a payment, so get your entries in early!
Personal tools