Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Improvement] Should we revisit contribution - pointers to elsewhere or more than generic policy request? #62

Closed
shanecoughlan opened this issue Nov 21, 2022 · 5 comments

Comments

@shanecoughlan
Copy link
Contributor

Item for discussion in the editing cycle.

@shanecoughlan
Copy link
Contributor Author

Here is what we currently have:

3.5.1 - Contributions

If an organization considers contributions to open source projects, then

a written policy shall exist that governs contributions to open source projects;
the policy shall be internally communicated; and
a process shall exist that implements the policy
Verification material(s):

If an organization permits contributions to open source projects, then the following shall exist:

3.5.1.1 - A documented open source contribution policy;
3.5.1.2 - A documented procedure that governs open source contributions; and
3.5.1.3 - A documented procedure that makes all program participants aware of the existence of the open source contribution policy (e.g., via training, internal wiki, or other practical communication method).

@shanecoughlan
Copy link
Contributor Author

On the January 2023 North America / Europe call we discussed whether more details were needed. For example, should we say what the policy should contain?

It was agreed that with our official focus of "the what and why" (avoid the how and when), it is appropriate to remain high level.

Checking with January 2023 North America / Asia call participants: what do you think?

@shanecoughlan
Copy link
Contributor Author

Discussion on call had this outcome: the current text fits the "what" approach and we should avoid going to "how," so we will not change this text in the next iteration of the specification. Issue is being closed. Can reopen if people feel strongly.

@jacobdjwilson
Copy link

I agree with the discussion on the January 2023 call. If either directional or prescriptive guidance is provided this should be part of the education/training workstream as a resource but not the specification itself.

@bprashant644
Copy link

There could be two ways of contributing from orgs standpoint -

  1. Organization making their code open source and maintaining it. (Would require CCLA, ICLA, Contribution guidelines, code of conduct, and other documents in place)
  2. Organizations allowing their employees to contribute to any open source project

Should this reflect in the Contribution section?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants