-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
946d2fa
commit 5e8fdeb
Showing
1 changed file
with
49 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,49 @@ | ||
| # Code of Conduct | ||
|
|
||
| The standard _Code of Conduct_ that all Eclipse projects must adhere to is defined in the following documents: | ||
|
|
||
| - [Eclipse Code of Conduct](https://raw.githubusercontent.com/eclipse/.github/master/CODE_OF_CONDUCT.md) | ||
| - [Eclipse Foundation Handbook](https://www.eclipse.org/projects/handbook/) | ||
| - [Eclipse Committer Due Diligence Guidelines](https://www.eclipse.org/legal/committerguidelines.php) | ||
|
|
||
| We (the committers) aim to run this project in an open and fair manner where contributions are encouraged from all companies and individuals. We aim for high quality, well documented and tested software that can be used in production environments. | ||
|
|
||
| This document shall outline additional roles and responsibilities for committers and project leads to ensure the project is well maintained and supported to be useable in production environments. | ||
|
|
||
| ## Committers | ||
|
|
||
| [Eclipse-uProtocol Committers](https://www.eclipse.org/projects/handbook/#roles-cm) play a vital role to ensure contributions from others (and themselves) follow the vision and mission of the project as well. In this section we will outline how committers are nominated, retired, and their duties while in service. | ||
|
|
||
| ### Duties | ||
|
|
||
| * Contribute to specifications by providing feedback, code contributions in up-spec, up-core-api repos | ||
| * Ensure all contributors (including themselves) adhere to this code of conduct, the Eclipse Foundation Handbook, and the vision & mission of the project | ||
| * Make _significant_ code contributions to one or more repositories in the Eclipse-uProtocol project | ||
| * Review and provide feedback to pull requests from other contributors | ||
| * _Actively_ participate in weekly/bi-weekly project meetings | ||
|
|
||
| ### Nomination | ||
|
|
||
| Contributors are nominated by a uProtocol Committer when they meet the [Eclipse Committer Nomination Process](https://www.eclipse.org/projects/handbook/#elections-committer) requirements and are actively performing the duties of a committer mentioned above. | ||
|
|
||
| ### Retirement | ||
|
|
||
| Per [Eclipse Foundation Handbook](https://www.eclipse.org/projects/handbook/#elections-retire-cm), Committers may retire for one of the following reasons: | ||
|
|
||
| * Their own volition | ||
| * By the project lead (with supporting justification) | ||
|
|
||
| Non-exhaustive examples for early retirement might be: | ||
| * Inactivity over extended period of time | ||
| * Repeated violations of this code of conduct (ex. obstructing progress during discussions/PRs without | ||
| * valid justification, intentional damage of various repos/projects, etc...) | ||
|
|
||
| All communication regarding committer nominations and retirement, *SHALL* be sent to the [email protected] mailing list. | ||
|
|
||
|
|
||
| ## Project Lead | ||
|
|
||
| In addition to the duties mentioned in [Eclipse Contributor Handbook](https://www.eclipse.org/projects/handbook/#roles-pl), project leads *MUST* also fulfill the Committer [Duties defined above](#duties). | ||
|
|
||
|
|
||
| NOTE: Violation to this code of conduct should be reported to the [Eclipse Foundation Management Office (EMO)](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues) |