Policy/process for accepting contributions?

[bensheldon]

The Contributions section includes how people can make contributions, but doesn't explain the process/timeline for how contributions are reviewed, evaluated for inclusion, and accepted (or under what circumstances they won't be accepted).

Providing greater transparency into this Open Source process would help contributors know what to expect and better prepare their contributions for inclusion.

An example is the Linux kernel patch review process.

[benbalter]

@bensheldon have you seen http://project-open-data.github.io/governance/? Perhaps a pull request adding it to contributing.md would be the best path forward to make it more visible? (it's linked from the main page).

[bensheldon]

@benbalter aha, I missed that previously. In regards to this section...

a repo manager will adjudicate the pull requests (accept, modify, or reject) in a public log according to a communicated release cycle (e.g., once a week, every other month). Information on the repo manager and release cycle for updates will be available in each repo’s documentation file. A program management office (PMO) in the General Services Administration (GSA) will delegate management of individual repos on behalf of the White House, as well as provide daily technical oversight and user support for the Project.

... who is the repo manager and what is the release cycle for this repository?

I'll take another look at the main page and readme and see if I can help make it clearer. Thanks!

[haleyvandyck]

Thanks for the questions @bensheldon. We just added additional clarification to the governance file in #112 as well--hope this helps clarify!