-
Notifications
You must be signed in to change notification settings - Fork 22
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
Comments
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; If an organization permits contributions to open source projects, then the following shall exist: 3.5.1.1 - A documented open source contribution policy; |
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? |
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. |
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. |
There could be two ways of contributing from orgs standpoint -
Should this reflect in the Contribution section? |
Item for discussion in the editing cycle.
The text was updated successfully, but these errors were encountered: