You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+33
Original file line number
Diff line number
Diff line change
@@ -84,6 +84,39 @@ About two tasks are one time for the life time. You can continue to use the same
84
84
- When the PR has 'Approved' flag from corresponding maintainer.
85
85
- If you feel there is delay, feel free to add a comment, discuss the same in Slack channel, or send email.
86
86
87
+
## Becoming member of gluster.org team in github
88
+
89
+
This section details the process of becoming part of gluster.org team.
90
+
The member list is reviewed by the current maintainers along with infra team time to time.
91
+
92
+
### How to create a presence/identity in the Gluster.org projects
93
+
94
+
Words 'MUST', 'SHOULD' etc to be referred from [RFC2119](https://tools.ietf.org/html/rfc2119)
95
+
96
+
* MUST have enabled [two-factor authentication](https://help.github.com/articles/about-two-factor-authentication) on their GitHub account
97
+
* MUST have read the [contributor guide](#)
98
+
* SHOULD have made multiple contributions to the project or community. Contribution may include, but is not limited to:
99
+
- Authoring or reviewing PRs on GitHub
100
+
- Filing or commenting on issues on GitHub
101
+
- Contributing to subproject, or community discussions (e.g. meetings, Slack, email discussion forums, Stack Overflow)
102
+
* SHOULD be subscribed to [gluster-users](https://lists.gluster.org/mailman/listinfo/gluster-users), [gluster-devel](https://lists.gluster.org/mailman/listinfo/gluster-devel) mailing lists.
103
+
* SHOULD be actively contributing to 1 or more subprojects for 30 days.
104
+
* Sponsored by 2 gluster-maintainers. Note the following requirements for sponsors:
105
+
- Sponsors must have close interactions with the prospective member - e.g. code/design/proposal review, coordinating on issues, etc.
106
+
- Sponsors must be the maintainer of an active repo in the Gluster org
107
+
- An approver/reviewer in the Gluster org may sponsor someone for the Gluster org; as long as it's a project they're involved with.
108
+
109
+
110
+
### Request Process
111
+
112
+
* Open an issue against the [project-infrastructure](https://github.com/gluster/project-infrastructure) repo
113
+
- With your github handle
114
+
- Ensure your sponsors are @mentioned on the issue or may be as approvers
115
+
- Have your sponsoring reviewers reply confirmation of sponsorship: +1
116
+
* Once your sponsors have responded, your request will be reviewed by the admin. Any missing information will be requested.
117
+
118
+
119
+
87
120
## By contributing to this project, the contributor would need to agree to below.
0 commit comments