Difference between revisions of "BugBountyProgram"
From Apache OpenOffice Wiki
(→OpenOffice.org Bug Bounty Programme: ideas for 2009 Edition) |
|||
| Line 25: | Line 25: | ||
== Planning == | == Planning == | ||
* Wait till the university exam period is done | * Wait till the university exam period is done | ||
| + | |||
= Join the OpenOffice.org Bounty Hunters! = | = Join the OpenOffice.org Bounty Hunters! = | ||
| Line 38: | Line 39: | ||
* to encourage code contributions (e.g. bug fixes) :-) | * to encourage code contributions (e.g. bug fixes) :-) | ||
| − | * to attract | + | * to attract new developers, make it easier to join. Participate! |
== How to apply == | == How to apply == | ||
Revision as of 13:07, 23 March 2009
Contents
OpenOffice.org Bug Bounty Programme
Preparing edition 2009
Starting with the preparation of a new programm in 2009, the following ideas/issues were mentioned: - better promotion - better support
Marketing
- promoting it on the main page (www.openoffice.org)
- add an item on contributung page (contributing.openoffice.org)
- start a twitter account and get 1000+ followers. post a link.
- post to digg
- tell a few high profile bloggers about it.
- encourage people to blog about it
- a lot of promoting and press releases
- inform writers/editors on tech news sites, like wired.com
- send notices to computer science departments at universities
Support
- promote clearly how people can get support, if they need it, to make the start
- have a prominent link to the predone VirtualBox ubuntu images of cl, so the issue of getting the thing compiled would be already solved
- have some really easy bugs available for fixing to get some results
Planning
- Wait till the university exam period is done
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:
- propose a bug fix on BugBountyProgram/Issues 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 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!
