Get involved and Contribute via forums, edit the documentation, work on the issue tracker, and submit pull requests on Github.

Once you're actively contributing, one of our Team members may invite you to be a committer (after a vote has been called). When that happens, if you accept, the following process begins.

Note that becoming a committer is not just about submitting some pull requests; it is also about helping with the development and user Discussion Forums, helping with documentation, and working on the issue tracker.

Steps to Becoming a Contributor to Documentation and Source Code

1. Fill out and submit the Codice Individual Contributor License Agreement. 
2. Submit a pull request with desired changes (for source code only).

Getting Started on Development

See the /wiki/spaces/DDF27x/pages/1179898 for developer tips and information about contributing your changes and source code formatting.

Getting Karma on JIRA and Confluence

After being an active participant, you can mail the dev list and request JIRA/Confluence karma. We can then grant the necessary karma, so you can start working on JIRA issues and editing the wiki.

Factors considered to become a Committer

Community - Active Participation helps build it

• Knowing when to leverage other committers, groups (nobody knows everything)
• The involvement in the number of pull requests: https://github.com/codice/ddf/pulls?utf8=%E2%9C%93&q=involves
  • https://help.github.com/articles/searching-issues-and-pull-requests/#search-by-a-user-thats-involved-in-an-issue-or-pull-request
• Reviewing pull requests and providing impactful feedback (even if it is not requested, it is open source).
  • Ability to effectively communicate technical opinion 
  • Ability to resolve disagreements on technical solutions
  • Willingness to -1 PRs or request changes, ideas with sound technical logic
• Actively posting to the Google Group Forums 

Overall Knowledge

• Providing guidance/feedback on architectural direction of the project
  • Create a new feature/component
• Proper usage of existing architectural constructs: Catalog Framework, Plugins, Transformers, Actions, Endpoints, Sources, Catalog Provider (Solr)
• Understanding concepts of re-usable code
• Federation concepts (querying, availability, Sources, Stores, Providers, Fanout, Registry)

Documentation

• Improving documentation for the benefit of all community members
• In the spirit of Github's open source survey - "Documentation is highly valued, frequently overlooked, and a means for establishing inclusive and accessible communities." 

Testing - Unit and Integration Tests (PaxExam)

• Adding new tests
• Fixing race conditions/Improving stability 
• Modifying/Improving existing tests

Security

• Authentication - user management

• Authorization - policy management
• SAML/SSO

User Interfaces

• Demonstrated ability to contribute (JavaScript) to Intrigue or the Admin Console