Talk:OWASP Coderbounty Project

• Main
• FAQs
• Acknowledgements
• Road Map and Getting Involved
• Minimum Viable Product
• Project About

OWASP Coderbounty The OWASP Coderbounty project aims to accelerate development of projects through gamification within OWASP by placing bounties on Github issues, cheat sheets writing code and related tasks while keeping security in mind. OWASP Coderbounty is not a "Bug Bounty" platform that encourages users to find bugs. It is more of a project management software that allows users to hire developers to complete coding tasks. A proposed functionality of Coderbounty in conjunction with OWASP is that Projects can accumulate points for each bounty offer and in this way their money spent into running a bounties can increase. 30% of the 10% earned commission will go to the Flagship/LAB projects budget for running bounties. Another possibility is that 10% of the full bounty goes to OWASP. Description Coderbounty accelerates software development in the open source community. We connect developers who want to make money with software creators. Coderbounty makes it easy to get your issues fixed for a low cost. Developers compete for the cash prize, i.e. bounty, to get the issue done fast. Open source software used to require developers to donate their time to help out a project. Now, with Coderbounty, they can earn money. When project managers need to add a feature to an open source program, they can add the issue and post a bounty that will attract coders to complete it. Coderbounty is the best way to get open source code issues solved and supports innovation in the open source and software industry. Licensing This program is free software: you can redistribute it and/or modify it under the terms of the link GNU Affero General Public License 3.0 as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright © by {the Project Leader(s) or OWASP} {Year(s)}.

Project Resources Coderbounty.com FAQ Slack Feedback Drive Source What's New Commits Issues Labels Milestones Wiki Twitter Facebook Project Leader Project leader (s) name: Sean Auriti Email: [email protected] Related Projects OWASP_Snakes_and_Ladders Classifications

News and Events [26 Feb 2016] Applied to become an OWASP project [07 Jan 2016] Became a NYS corporation. [10 Dec 2015] Implemented the AGPL license. [14 Oct 2015] Became open source on Github. [29 Nov 2013] Completed new western theme design from design contest. [04 May 2013] Created new mockup for full website design. [01 May 2013] Moved from Webfaction to Heroku. [27 Oct 2012] Moved source code from SVN to Bitbucket. [24 Sep 2012] Featured in DailyTekk's 100 Terrific Tools for Coders & Developers article. [18 Apr 2012] Received our first $100 bounty for the OpenFrameworks project. [08 Feb 2012] Hired first developer and project manager to help move the project along faster. Added more gamification, coins and animations. [28 Dec 2011] Has first transaction of a coder helping Clusterify, an open source project, and getting paid the bounty. [20 Dec 2011] Launched first version of the website. Over 100 users signed up.

How can I participate in your project?

All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

If I am not a programmer can I participate in your project?

Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator. See the Road Map and Getting Involved tab for more details.

How do I use this Coderbounty

First find an issue on any of the services we support, paste a link to it, and add a bounty. Additionally you can add to existing bounties or if you are a coder you can complete the tasks and get the bounty!

How long will the bounty remain on the issue

As long as you want. You can request a refund within 60 days for a 3% fee, after that the bounty stays on the issue until it is closed.

What does open mean

Open means that the issue has not been fixed, coders can commit their code and fix the issue.

What does in review mean

In review means that the coder has committed a fix, and the issue reporter and bounty placers are reviewing the code. Bounties can still be placed and when the issue remains closed for 3 days, the bounty is paid out to the coder who committed the code to close the issue.

What does paid mean

Paid means that the issue has been fixed, was in review for 3 days and has been verified as closed. Also, the bounty was paid to the coder who closed the issue.

Can you integrate my bug tracker for my company

Yes! Let us know in the feedback area or send an email to coderbounty at gmail.com

I code, will I be guaranteed the bounty

Yes! Payment is collected up front and held in escrow. When your code is approved you will receive a payment to your selected payment service.

What does take mean

Take gives you exclusive rights to close the issue. This issue will be blocked from anyone else taking it and you will have 24 hours to resolve the issue.

Contributors

The OWASP Coderbounty Project is developed by a worldwide team of people. A live update of project contributors is found here.

The first contributors to the project were:

• Sean Auriti who created the OWASP Coderbounty project
• Long Yang who helped add more gamification features to the first version
• Andrey Gromov Helped with the first version's funcionality

Roadmap

1 - fix any issues the site may have, integrate payment services

2 - Endemic Advertising with tags on GitHub

3 - Collaboration with FOSS Communities & Orgs to develop a mutually beneficial model

4 - Develop the site to become the go-to tool for open source software development

As of February, 2016, the highest priorities for the next 6 months are:

• Get other people to review OWASP Coderbounty and provide feedback
• Incorporate feedback into changes
• Finalize and have it reviewed to be promoted from an Incubator Project to a Lab Project

Subsequent Releases will add

• Internationalization Support
• Additional Unit Tests
• Automated Regression tests

Getting Involved

Involvement in the development and promotion of OWASP Coderbounty is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows:

Coding

We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests

Localization

Are you fluent in another language? Can you help translate the text strings in the Tool Project Template into that language?

Testing

Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.

Feedback

Please use the Uservoice for feedback about:

• What do like?
• What don't you like?
• What features would you like to see prioritized on the roadmap?

Our MVP is to have a fully automatic bounty purchase and payout as well as integrate special functions, methods and processes for OWASP projects.