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

Commit 6b84c510 authored by Martin Haeuer's avatar Martin Haeuer
Browse files

fix typo

parent d40cab4b
...@@ -7,7 +7,7 @@ Contributing to IEEE SA OSCom open-source peer-review ad-hoc sub-committee proje ...@@ -7,7 +7,7 @@ Contributing to IEEE SA OSCom open-source peer-review ad-hoc sub-committee proje
this file is based on [Nektar++'s CONTRIBUTING.md](https://gitlab.nektar.info/nektar/nektar/-/blob/master/CONTRIBUTING.md) file under an MIT License. this file is based on [Nektar++'s CONTRIBUTING.md](https://gitlab.nektar.info/nektar/nektar/-/blob/master/CONTRIBUTING.md) file under an MIT License.
## Contents ## Contents
This guide should provide you sufficient information to help if you're interested in contributing to IEEE-SA OSCom Open-Source Peer-Review ad-hoc committee, either in reporting bugs or, hopefully, providign ideas to fix them. The peer-review "admin" project repository will not produce any software or hardware design; instead, it will ead to the creation of recommendations for consideration by teh IEEE SA Open Source Committee on the topic of peer-review of open source designs. This guide should provide you sufficient information to help if you're interested in contributing to IEEE-SA OSCom Open-Source Peer-Review ad-hoc committee, either in reporting bugs or, hopefully, providign ideas to fix them. The peer-review "admin" project repository will not produce any software or hardware design; instead, it will ead to the creation of recommendations for consideration by the IEEE SA Open Source Committee on the topic of peer-review of open source designs.
Contributing is described from the following three points of view: Contributing is described from the following three points of view:
- [Issues and bug reports](#issues-and-bug-reports) - [Issues and bug reports](#issues-and-bug-reports)
- [How to contribute](#how-to-contribute) - [How to contribute](#how-to-contribute)
...@@ -32,7 +32,7 @@ If you would like to contribute improvements or add new topic/feature, please co ...@@ -32,7 +32,7 @@ If you would like to contribute improvements or add new topic/feature, please co
- `fix/mygreatfix`: fixes an issue that isn't tracked in the issue tracker. - `fix/mygreatfix`: fixes an issue that isn't tracked in the issue tracker.
- `issue###/123-myfantasticpatch`: fixes an issue that is tracked in the issue tracker (please replace `###` with the issue number) - `issue###/123-myfantasticpatch`: fixes an issue that is tracked in the issue tracker (please replace `###` with the issue number)
- `tidy/mybrillianttidying`: cosmetic fixes to bring existing files up to the [formatting guidelines](#formatting-guidelines) defined below. - `tidy/mybrillianttidying`: cosmetic fixes to bring existing files up to the [formatting guidelines](#formatting-guidelines) defined below.
3. Submit a merge request to merge back into the [`opensource.ieee.org/community`](https://opensource.ieee.org/community/) project space. ___Note:___ If you are merging back just to see the difference between your change and the project space code, use the `[WIP]` text at teh begining of the title of your merge request: this convention will signal to us to disregard the merged request but to keep it for your viewing. 3. Submit a merge request to merge back into the [`opensource.ieee.org/community`](https://opensource.ieee.org/community/) project space. ___Note:___ If you are merging back just to see the difference between your change and the project space code, use the `[WIP]` text at the begining of the title of your merge request: this convention will signal to us to disregard the merged request but to keep it for your viewing.
4. When you are ready to merge your contribution, put a comment in the Merge Request saying that it's ready to be merged. 4. When you are ready to merge your contribution, put a comment in the Merge Request saying that it's ready to be merged.
5. When applicable, please respond to any comments or questions during the merge request processing. 5. When applicable, please respond to any comments or questions during the merge request processing.
...@@ -90,7 +90,7 @@ Management of features, issues and improvements will be done through the [issue ...@@ -90,7 +90,7 @@ Management of features, issues and improvements will be done through the [issue
* 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. * 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. * 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.
For this project, the BDFL model was adopted. @alfredo.herrera will be teh only one making commits, but contributions to specific topics will be assigned to indivbidual members of the committee who will provide a target date for completion of the task and self-direct the work. For this project, the BDFL model was adopted. @alfredo.herrera will be the only one making commits, but contributions to specific topics will be assigned to indivbidual members of the committee who will provide a target date for completion of the task and self-direct the work.
### Auditing ### Auditing
Auditing will be done on regular conference calls. Auditing will be done on regular conference calls.
......
Supports Markdown
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