Contribute

Contributing Code

• Keep the changes behind existing interfaces (ie.. try not to break any contracts)
• Be sure all tests in Abot2.Test.Unit and Abot2.Test.Ingtegration are passing without being commented out or hacked
• Be sure to write unit tests for any new code or changes
• Submit pull requests to the master branch

We Currently Need

• Help implementing new features and bug fixes on Github Issues page. Grab one, comment to let everyone know your progress, then submit a pull request when its polished and ready.
• Automated performance tests. This would allow us to determine which configurations of Abot work best/worst in several different scenarios.
• Dedicated or virtual dedicated hardware for the build server, deployment hub, distributed crawl testing, etc..
• Testing/reporting on Abot's performance/stability on different platforms

We Always Need

• Donations (See section below)
• Star us on the homepage
• Spread the word on blogs/websites and tell others why Abot is great
• Report bugs or suggest features on the Github Issues page
• Let us know when you create a cool project that uses Abot
• Let us know what we are doing right/wrong. Don't just grab and go.

Consider Making A Donation

A donation of any amount would be greatly appreciated.

Please reach out if you have other contribution ideas by emailing abotcrawler@gmail.com.