Contribution standards and process

[sembrat]

I think it may be valuable to understand the code review, commit, and contribution process for DCC repo work.

For example:

1. Do DCC members have a representative with write access for each organization?
2. Who should review PRs?
3. Who should merge and close PRs?

Selfishly, I'd love an example of how best to contribute to DCC repositories and projects and reach out to DCC folks for feedback, review, and next steps.

[kayaelle]

Hi @sembrat - great questions! All of the DCC software is open source and we may get PRs from anyone but most typically they are from DCC members.

For the most part, the dev team at DCC reviews PRs, closes, & merges. However if there is a repo that your org is leading development on that is in the DCC github, then it probably makes more sense for your org to manage or co-manage PRs.

It would be a good idea to talk this through some at one of the TWG office hours.

[alexfigtree]

We will be adding a general contribution section to our upcoming developer WIKI: #35

I will reference this issue there and close this ticket.