You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Easier

Anyone can contribute to COmanage by

  • Participating in community discussions on the Email Lists, in particular comanage-users.
  • Filing bug reports and requests for enhancement (RFEs) in the COmanage Issue Tracker.
    • Bug reports with patches, pull requests, or suggested fixes are especially welcome.
    • Any code submissions must be small (ie: only a few lines, and consist exclusively of bug fixes to existing code), otherwise see Harder, below.
  • Making minor corrections (fixing typos or clarifying existing language) in this wiki.
    • (warning) Please do not make major changes without consulting the project first.
  • Discussing or presenting on your COmanage deployments, to your colleagues, at conferences, in elevators, or at social events where you aren't concerned with coming across as too geeky.
  • Funding. Various mechanisms exist for funding project development and work. Drop a note to the dev list and we'll point you in the right direction.

Harder

Non-trivial contributions to COmanage require a few more steps. While this list is oriented towards code contributions, similar constraints apply to other sorts of contributions, including documentation.

  1. A signed Contributor License Agreement must be filed before any contributions can be merged into the release path.
    1. A list of organizations that may currently contribute code is available in Authorized COmanage Contributors.
  2. Read through the Developer Manual pages for the project's current best practices.
  3. Reach out to the dev team (drop a note to the dev list, find us at a conference, etc) to discuss your proposed work and to identify the correct branch to apply the work to.
    1. (info) We recommend consulting with us prior to starting any major work so we can make sure you're headed in the right direction.
  4. All technical work requires an associated issue in the COmanage Issue Tracker.
  5. Once your changes are ready, submit a pull request against the identified branch. Your changes will be reviewed and either modifications will be requested or the pull request merged.
  6. If you do this often enough, we might make you a committer. We don't have formal thresholds for that just yet, though.
  • No labels