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 ...)
 
m
 
(11 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Draft for a OpenOffice.org Bug Bounty Program =
+
= OpenOffice.org Bug Bounty Programme =
  
* program is running from September 15th to December 15th 2008, 10000 € are available in this time.
+
For the 2009 programm, go to [[OpenOffice.org_Internship]].
  
* for every bug fix 33 € (about 50$) will be payed
+
= Join the OpenOffice.org Bounty Hunters! =
  
== Scope ==
+
* 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.
  
* encourage code contributions (e.g. bug fixes)
+
* The Programme will pay a minimum of 33 € (about 50$) for every bug fixed.
  
* attract new developers (students and pupils), software professionals are not eligible for the program
+
== Why are we doing this? ==
  
* reduce bug count
+
* to clear up outstanding bugs
  
== how to apply ==
+
* to encourage code contributions (e.g. bug fixes) :-)
  
* a minimum effort has to be in the fix to avoid to have "no brainers" included in this program, for this reason:
+
* to attract new developers, make it easier to join. Participate!
  
* propose a bug fix on <to-be-specified> wiki page, any [[DomainDeveloper]] is been able to confirm that this is a nontrivial fix
+
== How to apply ==
  
* a domain developer can propose to raise the payment to 100, 200 or 500 € according to the difficulty of the bug fix.
+
Trivial, "no brainers" are excluded from the Programme. To make sure your work will qualify:
  
== conditions ==
+
* propose a bug fix on [[BugBountyProgram/Issues]] wiki page
  
* bug fix has to be integrated into the development code line, either via cws or via patch gateway of an established contributor
+
* wait for any [[DomainDeveloper]] to confirm that this is a non-trivial fix
  
* paypal account
+
* a domain developer can also propose a higher payment of 33, 100, 200 or 500 € according to the difficulty of the bug fix.
 +
 
 +
== Terms & 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
 +
 
 +
* Once your work for a BugFix has been completed, the bugbounty_review@openoffice.org has to be notified for further processing.
 +
 
 +
* 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!
 +
 
 +
[[Category:Community Council]]

Latest revision as of 15:25, 11 January 2010

OpenOffice.org Bug Bounty Programme

For the 2009 programm, go to OpenOffice.org_Internship.

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, make it easier to join. Participate!

How to apply

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

  • a domain developer can also propose a higher payment of 33, 100, 200 or 500 € according to the difficulty of the bug fix.

Terms & 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
  • Once your work for a BugFix has been completed, the bugbounty_review@openoffice.org has to be notified for further processing.
  • 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