-
Notifications
You must be signed in to change notification settings - Fork 128
Contribution Guide
agorajek edited this page Mar 28, 2011
·
32 revisions
- You should have some idea about the project and its purpose. If you don't, start here: http://madlib.net
- You should be familiar with the project contents. If you are not, look at below links:
- Existing methods: http://devdoc.madlib.net
- Development Status
- Future methods: Contrib Status
- You should have some knowledge on relational databases, SQL, Python, C/C++, and analytical methods that you want to implement.
- Create an account on GitHub.com.
- Get a git client from git-scm.com.
- If you are not familiar with this version control software follow Bootcamp guides on help.github.com to gain some confidence.
- Create an account on MADlib JIRA and review the Open issues.
- Found one that you like?
- Write a Comment and ask for assignment.
- Know what you want to work and we don't have it on JIRA.
- Open a JIRA ticket (bug, task, or new feature) and let us know (in a Comment) you are working on it.
- Don't know what to work on or have any other question?
- Post a message to MADlib Dev Forum
- Go to GitHub MADlib repo and fork the project using the FORK button (top right).
- This step will create a "connected" copy of madlib/madlib repo under yourGitHubAccount/madlib.
- Need some help with forking? Check here
by using your own copy/fork of the MADlib repository. And remember about:
- Good coding practices: Coding Patterns & Best Practices Guide (COMING SOON)
- Proper API: SQL API Guide
- Full documentation: Documentation Guide (NEEDS REVIEW)
- Installer compliance: MADlib Installer Guide (NEEDS REVIEW)
- Comprehensive unit tests: Unit Testing Guide (NEEDS REVIEW)
- Done with coding?
- Make a pull-request from your forked repository. Get some help on pull-requests here.
- This will generate an email to project committers.
- Someone will review your changes and merge them into MADlib master repository.