Skip to content

Commit e24da5a

Browse files
swcurranswcurran
committed
Updates to the README and other Admin files in the repository
Signed-off-by: Stephen Curran <[email protected]>
1 parent e235901 commit e24da5a

File tree

4 files changed

+337
-46
lines changed

4 files changed

+337
-46
lines changed

‎CODE_OF_CONDUCT.md

+166
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,166 @@
1+
# [Hyperledger Code of Conduct](https://wiki.hyperledger.org/community/hyperledger-project-code-of-conduct)
2+
3+
Hyperledger is a collaborative project at The Linux Foundation. It is an open-source and open
4+
community project where participants choose to work together, and in that process experience
5+
differences in language, location, nationality, and experience. In such a diverse environment,
6+
misunderstandings and disagreements happen, which in most cases can be resolved informally. In rare
7+
cases, however, behavior can intimidate, harass, or otherwise disrupt one or more people in the
8+
community, which Hyperledger will not tolerate.
9+
10+
A **Code of Conduct** is useful to define accepted and acceptable behaviors and to promote high
11+
standards of professional practice. It also provides a benchmark for self evaluation and acts as a
12+
vehicle for better identity of the organization.
13+
14+
This code (**CoC**) applies to any member of the Hyperledger community – developers, participants in
15+
meetings, teleconferences, mailing lists, conferences or functions, etc. Note that this code
16+
complements rather than replaces legal rights and obligations pertaining to any particular
17+
situation.
18+
19+
## Statement of Intent
20+
21+
Hyperledger is committed to maintain a **positive** [work environment](#work-environment). This
22+
commitment calls for a workplace where [participants](#participant) at all levels behave according
23+
to the rules of the following code. A foundational concept of this code is that we all share
24+
responsibility for our work environment.
25+
26+
## Code
27+
28+
1. Treat each other with [respect](#respect), professionalism, fairness, and sensitivity to our many
29+
differences and strengths, including in situations of high pressure and urgency.
30+
31+
2. Never [harass](#harassment) or [bully](#workplace-bullying) anyone verbally, physically or
32+
[sexually](#sexual-harassment).
33+
34+
3. Never [discriminate](#discrimination) on the basis of personal characteristics or group
35+
membership.
36+
37+
4. Communicate constructively and avoid [demeaning](#demeaning-behavior) or
38+
[insulting](#insulting-behavior) behavior or language.
39+
40+
5. Seek, accept, and offer objective work criticism, and [acknowledge](#acknowledgement) properly
41+
the contributions of others.
42+
43+
6. Be honest about your own qualifications, and about any circumstances that might lead to conflicts
44+
of interest.
45+
46+
7. Respect the privacy of others and the confidentiality of data you access.
47+
48+
8. With respect to cultural differences, be conservative in what you do and liberal in what you
49+
accept from others, but not to the point of accepting disrespectful, unprofessional or unfair or
50+
[unwelcome behavior](#unwelcome-behavior) or [advances](#unwelcome-sexual-advance).
51+
52+
9. Promote the rules of this Code and take action (especially if you are in a
53+
[leadership position](#leadership-position)) to bring the discussion back to a more civil level
54+
whenever inappropriate behaviors are observed.
55+
56+
10. Stay on topic: Make sure that you are posting to the correct channel and avoid off-topic
57+
discussions. Remember when you update an issue or respond to an email you are potentially
58+
sending to a large number of people.
59+
60+
11. Step down considerately: Members of every project come and go, and the Hyperledger is no
61+
different. When you leave or disengage from the project, in whole or in part, we ask that you do
62+
so in a way that minimizes disruption to the project. This means you should tell people you are
63+
leaving and take the proper steps to ensure that others can pick up where you left off.
64+
65+
## Glossary
66+
67+
### Demeaning Behavior
68+
69+
is acting in a way that reduces another person's dignity, sense of self-worth or respect within the
70+
community.
71+
72+
### Discrimination
73+
74+
is the prejudicial treatment of an individual based on criteria such as: physical appearance, race,
75+
ethnic origin, genetic differences, national or social origin, name, religion, gender, sexual
76+
orientation, family or health situation, pregnancy, disability, age, education, wealth, domicile,
77+
political view, morals, employment, or union activity.
78+
79+
### Insulting Behavior
80+
81+
is treating another person with scorn or disrespect.
82+
83+
### Acknowledgement
84+
85+
is a record of the origin(s) and author(s) of a contribution.
86+
87+
### Harassment
88+
89+
is any conduct, verbal or physical, that has the intent or effect of interfering with an individual,
90+
or that creates an intimidating, hostile, or offensive environment.
91+
92+
### Leadership Position
93+
94+
includes group Chairs, project maintainers, staff members, and Board members.
95+
96+
### Participant
97+
98+
includes the following persons:
99+
100+
- Developers
101+
- Member representatives
102+
- Staff members
103+
- Anyone from the Public partaking in the Hyperledger work environment (e.g. contribute code,
104+
comment on our code or specs, email us, attend our conferences, functions, etc)
105+
106+
### Respect
107+
108+
is the genuine consideration you have for someone (if only because of their status as participant in
109+
Hyperledger, like yourself), and that you show by treating them in a polite and kind way.
110+
111+
### Sexual Harassment
112+
113+
includes visual displays of degrading sexual images, sexually suggestive conduct, offensive remarks
114+
of a sexual nature, requests for sexual favors, unwelcome physical contact, and sexual assault.
115+
116+
### Unwelcome Behavior
117+
118+
Hard to define? Some questions to ask yourself are:
119+
120+
- how would I feel if I were in the position of the recipient?
121+
- would my spouse, parent, child, sibling or friend like to be treated this way?
122+
- would I like an account of my behavior published in the organization's newsletter?
123+
- could my behavior offend or hurt other members of the work group?
124+
- could someone misinterpret my behavior as intentionally harmful or harassing?
125+
- would I treat my boss or a person I admire at work like that ?
126+
- Summary: if you are unsure whether something might be welcome or unwelcome, don't do it.
127+
128+
### Unwelcome Sexual Advance
129+
130+
includes requests for sexual favors, and other verbal or physical conduct of a sexual nature, where:
131+
132+
- submission to such conduct is made either explicitly or implicitly a term or condition of an
133+
individual's employment,
134+
- submission to or rejection of such conduct by an individual is used as a basis for employment
135+
decisions affecting the individual,
136+
- such conduct has the purpose or effect of unreasonably interfering with an individual's work
137+
performance or creating an intimidating hostile or offensive working environment.
138+
139+
### Workplace Bullying
140+
141+
is a tendency of individuals or groups to use persistent aggressive or unreasonable behavior (e.g.
142+
verbal or written abuse, offensive conduct or any interference which undermines or impedes work)
143+
against a co-worker or any professional relations.
144+
145+
### Work Environment
146+
147+
is the set of all available means of collaboration, including, but not limited to messages to
148+
mailing lists, private correspondence, Web pages, chat channels, phone and video teleconferences,
149+
and any kind of face-to-face meetings or discussions.
150+
151+
## Incident Procedure
152+
153+
To report incidents or to appeal reports of incidents, send email to Mike Dolan
154+
([email protected]) or Angela Brown ([email protected]). Please include any
155+
available relevant information, including links to any publicly accessible material relating to the
156+
matter. Every effort will be taken to ensure a safe and collegial environment in which to
157+
collaborate on matters relating to the Project. In order to protect the community, the Project
158+
reserves the right to take appropriate action, potentially including the removal of an individual
159+
from any and all participation in the project. The Project will work towards an equitable resolution
160+
in the event of a misunderstanding.
161+
162+
## Credits
163+
164+
This code is based on the
165+
[W3C’s Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc) with some
166+
additions from the [Cloud Foundry](https://www.cloudfoundry.org/)‘s Code of Conduct.

‎MAINTAINERS.md

+88-41
Original file line numberDiff line numberDiff line change
@@ -1,70 +1,117 @@
11
# Maintainers
22

3+
## Maintainer Scopes, GitHub Roles and GitHub Teams
4+
5+
Maintainers are assigned the following scopes in this repository:
6+
7+
| Scope | Definition | GitHub Role | GitHub Team |
8+
| ---------- | ------------------------ | ----------- | ----------------------------------- |
9+
| Admin | | Admin | [aries-admins] |
10+
| Maintainer | The GitHub Maintain role | Maintain | [aries-askar committers] |
11+
| Maintainer | The GitHub Maintain role | Maintain | [aries committers] |
12+
| Read | The GitHub Read role | Read | [Aries Contributors] |
13+
| Read | The GitHub Read role | Read | [TOC] |
14+
15+
[aries-admins]: https://github.com/orgs/hyperledger/teams/aries-admins
16+
[aries-cloudagent-python committers]: https://github.com/orgs/hyperledger/teams/aries-cloudagent-python-committers
17+
[aries-askar committers]: https://github.com/orgs/hyperledger/teams/aries-askar-committers
18+
[Aries Contributors]: https://github.com/orgs/hyperledger/teams/aries-contributors
19+
[TOC]: https://github.com/orgs/hyperledger/teams/toc
20+
321
## Active Maintainers
422

523
<!-- Please keep this sorted alphabetically by github -->
624

7-
| Name | Github | LFID |
8-
| ---------------- | ---------------- | ---------------- |
9-
| Andrew Whitehead | andrewwhitehead | |
10-
| Berend Sliedrecht | blu3beri | |
11-
| Ian Costanzo | ianco | |
12-
| Wade Barnes | WadeBarnes | |
25+
| GitHub ID | Name | Scope | LFID | Discord ID | Email | Company Affiliation |
26+
| --------------- | ----------------- | ---------- | ---- | ---------- | ------------------------ | ------------------- |
27+
| andrewwhitehead | Andrew Whitehead | Admin | | | [email protected] | BC Gov |
28+
| dbluhm | Daniel Bluhm | Admin | | | [email protected] | Indicio PBC |
29+
| blu3beri | Berend Sliedrecht | Maintainer | | | [email protected] | Animo Solutions |
30+
| dh1128 | Daniel Hardman | Admin | | | [email protected] | Provident |
31+
| ianco | Ian Costanzo | Maintainer | | | [email protected] | Anon Solutions |
32+
| nage | Nathan George | Maintainer | | | [email protected] | Kiva |
33+
| swcurran | Stephen Curran | Admin | | | [email protected] | BC Gov |
34+
| WadeBarnes | Wade Barnes | Admin | | | [email protected] | BC Gov |
1335

1436
## Emeritus Maintainers
1537

16-
| Name | Github | LFID |
17-
|--------------|---------|---------|
18-
| | | |
38+
| Name | GitHub ID | Scope | LFID | Discord ID | Email | Company Affiliation |
39+
|----- | --------- | ----- | ---- | ---------- | ----- | ------------------- |
40+
| | | | | | | |
41+
42+
## The Duties of a Maintainer
43+
44+
Maintainers are expected to perform the following duties for this repository. The duties are listed in more or less priority order:
45+
46+
- Review, respond, and act on any security vulnerabilities reported against the repository.
47+
- Review, provide feedback on, and merge or reject GitHub Pull Requests from
48+
Contributors.
49+
- Review, triage, comment on, and close GitHub Issues
50+
submitted by Contributors.
51+
- When appropriate, lead/facilitate architectural discussions in the community.
52+
- When appropriate, lead/facilitate the creation of a product roadmap.
53+
- Create, clarify, and label issues to be worked on by Contributors.
54+
- Ensure that there is a well defined (and ideally automated) product test and
55+
release pipeline, including the publication of release artifacts.
56+
- When appropriate, execute the product release process.
57+
- Maintain the repository CONTRIBUTING.md file and getting started documents to
58+
give guidance and encouragement to those wanting to contribute to the product, and those wanting to become maintainers.
59+
- Contribute to the product via GitHub Pull Requests.
60+
- Monitor requests from the Hyperledger Technical Oversight Committee about the
61+
contents and management of Hyperledger repositories, such as branch handling,
62+
required files in repositories and so on.
63+
- Contribute to the Hyperledger Project's Quarterly Report.
1964

2065
## Becoming a Maintainer
2166

22-
The Aries Askar community welcomes contributions. Contributors may progress to become a
23-
maintainer. To become a maintainer the following steps occur, roughly in order.
24-
25-
- 5 significant changes have been authored by the proposed maintainer and
26-
accepted.
27-
- The proposed maintainer has the sponsorship of at least one other maintainer.
28-
- This sponsoring maintainer will create a PR modifying the list of
29-
maintainers.
30-
- The proposed maintainer accepts the nomination and expresses a willingness
31-
to be a long-term (more than 6 month) committer.
32-
- This would be a comment in the above PR.
33-
- This PR will be communicated in all appropriate communication channels. It
34-
should be mentioned in any maintainer/community call. It should also be
35-
posted to the appropriate mailing list or chat channels if they exist.
36-
- Approval by at least 3 current maintainers within two weeks of the proposal or
37-
an absolute majority of current maintainers.
38-
- These votes will be recorded in the PR modifying the list of maintainers.
39-
- No veto by another maintainer within two weeks of proposal are recorded.
40-
- All vetoes must be accompanied by a public explanation as a comment in the
41-
PR for adding this maintainer
42-
- The explanation of the veto must be reasonable.
43-
- A veto can be retracted, in that case the approval/veto timeframe is reset.
44-
- It is bad form to veto, retract, and veto again.
45-
- The proposed maintainer becomes a maintainer
46-
- Either two weeks have passed since the third approval,
47-
- Or an absolute majority of maintainers approve.
48-
- In either case, no maintainer presents a veto.
67+
This community welcomes contributions. Interested contributors are encouraged to
68+
progress to become maintainers. To become a maintainer the following steps
69+
occur, roughly in order.
70+
71+
- The proposed maintainer establishes their reputation in the community,
72+
including authoring five (5) significant merged pull requests, and expresses
73+
an interest in becoming a maintainer for the repository.
74+
- A PR is created to update this file to add the proposed maintainer to the list of active maintainers.
75+
- The PR is authored by an existing maintainer or has a comment on the PR from an existing maintainer supporting the proposal.
76+
- The PR is authored by the proposed maintainer or has a comment on the PR from the proposed maintainer confirming their interest in being a maintainer.
77+
- The PR or comment from the proposed maintainer must include their
78+
willingness to be a long-term (more than 6 month) maintainer.
79+
- Once the PR and necessary comments have been received, an approval timeframe begins.
80+
- The PR **MUST** be communicated on all appropriate communication channels, including relevant community calls, chat channels and mailing lists. Comments of support from the community are welcome.
81+
- The PR is merged and the proposed maintainer becomes a maintainer if either:
82+
- Two weeks have passed since at least three (3) Maintainer PR approvals have been recorded, OR
83+
- An absolute majority of maintainers have approved the PR.
84+
- If the PR does not get the requisite PR approvals, it may be closed.
85+
- Once the add maintainer PR has been merged, any necessary updates to the GitHub Teams are made.
4986

5087
## Removing Maintainers
5188

52-
Being a maintainer is not a status symbol or a title to be maintained
89+
Being a maintainer is not a status symbol or a title to be carried
5390
indefinitely. It will occasionally be necessary and appropriate to move a
5491
maintainer to emeritus status. This can occur in the following situations:
5592

5693
- Resignation of a maintainer.
5794
- Violation of the Code of Conduct warranting removal.
5895
- Inactivity.
5996
- A general measure of inactivity will be no commits or code review comments
60-
for one reporting quarter, although this will not be strictly enforced if
97+
for one reporting quarter. This will not be strictly enforced if
6198
the maintainer expresses a reasonable intent to continue contributing.
6299
- Reasonable exceptions to inactivity will be granted for known long term
63100
leave such as parental leave and medical leave.
64-
- Other unspecified circumstances.
101+
- Other circumstances at the discretion of the other Maintainers.
102+
103+
The process to move a maintainer from active to emeritus status is comparable to the process for adding a maintainer, outlined above. In the case of voluntary
104+
resignation, the Pull Request can be merged following a maintainer PR approval. If the removal is for any other reason, the following steps **SHOULD** be followed:
65105

66-
Like adding a maintainer the record and governance process for moving a
67-
maintainer to emeritus status is recorded in the github PR making that change.
106+
- A PR is created to update this file to move the maintainer to the list of emeritus maintainers.
107+
- The PR is authored by, or has a comment supporting the proposal from, an existing maintainer or Hyperledger GitHub organization administrator.
108+
- Once the PR and necessary comments have been received, the approval timeframe begins.
109+
- The PR **MAY** be communicated on appropriate communication channels, including relevant community calls, chat channels and mailing lists.
110+
- The PR is merged and the maintainer transitions to maintainer emeritus if:
111+
- The PR is approved by the maintainer to be transitioned, OR
112+
- Two weeks have passed since at least three (3) Maintainer PR approvals have been recorded, OR
113+
- An absolute majority of maintainers have approved the PR.
114+
- If the PR does not get the requisite PR approvals, it may be closed.
68115

69116
Returning to active status from emeritus status uses the same steps as adding a
70117
new maintainer. Note that the emeritus maintainer already has the 5 required

0 commit comments

Comments
 (0)