IEEE.org     |     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

From 1500 (3:00 PM) EST to 1600 (4:00 PM) EST we will be performing a major upgrade of the SA Open platform. This will affect all related services (opensource.ieee.org, opensource-connect.ieee.org, and *.ieee-saopen.org). During this period the listed URLs will be unavailable. For questions, email opensource@ieee.org.

Commit c2bac517 authored by Alfredo Herrera's avatar Alfredo Herrera
Browse files

Update CONTRIBUTING.md

parent a8cfd987
......@@ -51,11 +51,13 @@ Governance is the framework adopted by the project members to reflect how we wil
| Elements | Description | Date reviewed | Date adopted |
|--------------|-------------|---------------|--------------|
|[Policies](#policies) | What is acceptable and what is not acceptable | (planned) Jun 30, 2020 | TBD |
|[Inventory](#inventory) | List of availale resources and key decision | (planned) Jun 30, 2020 | TBD |
|[Inventory](#inventory) | Not included, out of scope for this project | (planned) Jun 30, 2020 | TBD |
|[Managing](#managing) | How we plan to follow and enforce governance policies | (planned) Jun 30, 2020 | TBD |
|[Auditing](#auditing) | How we plan to monitor the respect of governance policies | (planned) Jun 30, 2020 | TBD |
|[Reporting](#reporting) | How we plan to communicate progress/status on governance | (planned) Jun 30, 2020 | TBD |
Decision making will be based on [SciPy's governance](http://scipy.github.io/devdocs/dev/governance/governance.html).
### Policies
We adhere to [IEEE's code of conduct](https://www.ieee.org/content/dam/ieee-org/ieee/web/org/about/ieee_code_of_conduct.pdf), we count on you to follow it in all your interactions within the project:
1. Be respectful of others
......@@ -72,21 +74,9 @@ For question regarding _Publication_ guidelines and policies on all aspects of I
For question regarding _Standards_ guidelines and policies for contributions-to or use-of IEEE intellectual property rights in Standards check the [IEEE Standards IPR](https://standards.ieee.org/ipr/index.html) webpage.
### Inventory
This project will not create a hardware or software design, and for that reason and inventory of open source is not required. But proper attribution to copyrighted, free and open source and standards shall be followed for the purpose of:
* enforce our open source policies
* establish a baseline for ongoing auditing efforts
* plan for support
* manage risk
* prepare to distribute, divest, or publish findings
* comply with internal policies
* comply with regulations
* comply with open source licenses
* manage intellectual property issues
### Managing
Management of features, issues and improvements will be done through the [issue tracker](https://opensource.ieee.org/community/peer-review/admin/-/issues). There are three common decision making structures associated with self-governed open source projects according to [Dries Buytaert, InfoWorld](https://www.infoworld.com/article/3451796/3-models-for-open-source-governance.html):
* Benevolent Dictator For Life (Hierarchical): one person (project initiator or lead) has final say on all major project decisions; often, only this person commits code and appoints maintainers. The project's community contributes and reviews patches.
* Benevolent Dictator For Life (Hierarchical): one person (project initiator or lead) has final say on all major project decisions; often, only this person commits code and appoints maintainers. The project's community contributes and reviews contributions.
* Meritocracy (Majority rule from decision-makers): active project contributors (those who demonstrate “merit”) are given a formal decision making role and decisions are usually made based on pure voting consensus. Contributions can only be made by individuals representing themselves, not by a company. All Responsibility is shared by community.
* Liberal contribution (Concensus): those doing the most (current) work are recognised as most influential. Major project decisions are made based on a consensus rather than pure vote, and include as many community perspectives as possible.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment