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
docs: expand community membership with CNCF and governance processes (#95)
- Add CNCF request and communication protocols
- Define governance and project goal change procedures
- Outline election process requirements for candidates
- Include announcement protocol for community awareness
Signed-off-by: mingcheng <mingcheng@apache.org>
@@ -131,6 +141,64 @@ After the departure date, the Member(or Maintainer/Approver) and their GitHub ID
131
141
132
142
Those processes ensure proper handover and recognition while providing sufficient notice to the community.
133
143
144
+
## CNCF Requests and Communications
145
+
146
+
As a CNCF project, Dragonfly maintains an active relationship with the Foundation.
147
+
148
+
### CNCF-Related Decisions
149
+
150
+
CNCF-related requests that impact the project require community involvement, including:
151
+
152
+
- Project status changes (incubation, graduation)
153
+
- Resource requests and TOC interactions
154
+
- CNCF program participation
155
+
- Official statements and responses
156
+
157
+
### Process for CNCF Requests
158
+
159
+
#### Initiating CNCF Communications
160
+
161
+
1.**Proposal**: Any Maintainer creates an issue with label `cncf-request` including description, rationale, and timeline
162
+
2.**Discussion**: 7-day minimum community discussion period
163
+
3.**Review**: Maintainers discuss in bi-weekly meeting
164
+
4.**Other Considerations**: Any other relevant factors or context
165
+
166
+
#### Decision Making and Approval
167
+
168
+
We make the decision based on our [defined roles in the document](#how-we-make-decisions).
169
+
170
+
## Governance and Project Goal Changes
171
+
172
+
Significant changes to governance structure or project direction require special consideration to ensure community alignment.
173
+
174
+
### Types of Governance Changes
175
+
176
+
This process applies to:
177
+
178
+
-**Governance Document Updates**: Major revisions to governance, membership, or ladder documents
179
+
-**Decision-Making Changes**: Modifications to voting thresholds or consensus mechanisms
180
+
-**Role Structure Changes**: Adding/modifying community roles or responsibilities
181
+
-**Project Goal Changes**: Updates to mission, vision, or strategic direction
182
+
-**Repository Structure Changes**: Significant reorganization of project repositories
183
+
-**Other Major Changes**: Any other changes with substantial community impact
184
+
185
+
### Governance Change Process
186
+
187
+
#### Proposal and Discussion Phase
188
+
189
+
1.**Proposal**: Any Maintainer creates an issue with label `governance-change` including:
190
+
- Description of proposed changes
191
+
- Rationale and expected benefits
192
+
- Impact analysis and migration plan
193
+
2.**Discussion**: Make community discussion in the issue to gather feedback
194
+
3.**Voting**: Voting by our [defined roles in the document](#how-we-make-decisions)
195
+
4.**Documentation**: Create a Pull Request to update governance documents to reflect changes, and mention the related issue
196
+
5.**Announcement**: Publicly announce changes and notify in our bi-weekly community meeting
197
+
198
+
#### Decision and Implementation
199
+
200
+
We make the decision based on our [defined roles in the document](#how-we-make-decisions).
201
+
134
202
## Election Process
135
203
136
204
The candidates in the election must explain their past contributions to the project and community, as well as their future plans, while also presenting their campaign reasons and clear intentions.
Copy file name to clipboardExpand all lines: REPOSITORIES.md
+31-31Lines changed: 31 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,59 +4,59 @@ This document lists all repositories, sorted by their scope, within [Dragonfly](
4
4
5
5
You can read more about the scope and lifecycle of repositories in [REPOSITORY-GUIDELINES.md](https://github.com/dragonflyoss/community/blob/main/REPOSITORY-GUIDELINES.md).
6
6
7
-
## `Core`Scope Repositories
7
+
## `Core` Repositories
8
8
9
9
Learn more about the `Core` scope repositories in [REPOSITORY-GUIDELINES.md](./REPOSITORY-GUIDELINES.md#core).
|[dragonfly](https://github.com/dragonflyoss/dragonfly)| The core repository of Dragonfly. |
15
-
|[nydus](https://github.com/dragonflyoss/nydus)| Nydus is a Dragonfly sub-project, providing fast, secure and easy access to container images. |
16
-
|[helm-charts](https://github.com/dragonflyoss/helm-charts)| The Helm charts for deploying Dragonfly. |
17
-
|[client](https://github.com/dragonflyoss/client)| The Dragonfly client, providing a command-line interface for Dragonfly. |
18
-
|[api](https://github.com/dragonflyoss/api)| Canonical location of the Dragonfly API definition files. |
19
-
|[d7y.io](https://github.com/dragonflyoss/d7y.io)| The official site for Dragonfly, built with Docusaurus. |
|[.github](https://github.com/dragonflyoss/.github)| The default community organization-level files for Dragonfly. |
15
+
|[api](https://github.com/dragonflyoss/api)| Canonical location of the Dragonfly API definition files. |
16
+
|[client](https://github.com/dragonflyoss/client)| The Dragonfly client, providing a command-line interface for Dragonfly. |
17
+
|[community](https://github.com/dragonflyoss/community)| The Dragonfly community repository, providing resources and information for contributors. |
|[community](https://github.com/dragonflyoss/community)| The Dragonfly community repository, providing resources and information for contributors. |
30
-
|[.github](https://github.com/dragonflyoss/.github)| The default community organization-level files for Dragonfly. |
|[perf-tests](https://github.com/dragonflyoss/perf-tests)| Performance tests and benchmarks |
34
-
|[vortex-protocol](https://github.com/dragonflyoss/vortex-protocol)| A P2P file transfer protocol |
35
-
|[dragonfly-injector](https://github.com/dragonflyoss/dragonfly-injector)| A Dragonfly mutating webhook server that implements toolkits injection |
36
-
|[machinery](https://github.com/dragonflyoss/machinery)| Machinery is an asynchronous task queue/job queue based on distributed message passing. |
|[monitoring](https://github.com/dragonflyoss/monitoring)| Monitoring support for dragonfly |
39
-
|[dragonfly-repository-agent](https://github.com/dragonflyoss/dragonfly-repository-agent)| The Triton repository agent that downloads model via dragonfly. |
40
-
|[image-service-website](https://github.com/dragonflyoss/image-service-website)| The website of Nydus project. |
41
-
|[killercoda-scenarios](https://github.com/dragonflyoss/killercoda-scenarios)| Killercoda Scenarios for Dragonfly |
42
-
|[dragonfly-endpoint](https://github.com/dragonflyoss/dragonfly-endpoint)| The TorchServe endpoint that downloads model via dragonfly. |
|[dragonfly-endpoint](https://github.com/dragonflyoss/dragonfly-endpoint)| The TorchServe endpoint that downloads model via dragonfly. |
37
+
|[dragonfly-injector](https://github.com/dragonflyoss/dragonfly-injector)| A Dragonfly mutating webhook server that implements toolkits injection |
38
+
|[dragonfly-repository-agent](https://github.com/dragonflyoss/dragonfly-repository-agent)| The Triton repository agent that downloads model via dragonfly. |
|[image-service-website](https://github.com/dragonflyoss/image-service-website)| The website of Nydus project. |
41
+
|[killercoda-scenarios](https://github.com/dragonflyoss/killercoda-scenarios)| Killercoda Scenarios for Dragonfly |
42
+
|[machinery](https://github.com/dragonflyoss/machinery)| Machinery is an asynchronous task queue/job queue based on distributed message passing. |
43
+
|[monitoring](https://github.com/dragonflyoss/monitoring)| Monitoring support for dragonfly |
44
44
45
45
<!-- markdownlint-restore -->
46
46
47
-
## `Historical`Scope Repositories
47
+
## `Historical` Repositories
48
48
49
49
Learn more about the `Historical` scope repositories in [REPOSITORY-GUIDELINES.md](./REPOSITORY-GUIDELINES.md#historical).
|[dragonfly-archived](https://github.com/dragonflyoss/dragonfly-archived)| Legacy repository, which has been archived and is read-only. |
55
-
|[website](https://github.com/dragonflyoss/website)| All website material of Dragonfly |
56
55
|[dragonfly-examples](https://github.com/dragonflyoss/dragonfly-examples)| The examples of using Dragonfly |
56
+
|[dragonfly-scripts](https://github.com/dragonflyoss/dragonfly-scripts)| dragonfly scripts for CI |
57
+
|[helm-chart](https://github.com/dragonflyoss/helm-chart)| The legacy Helm chart for deploying Dragonfly. |
57
58
|[katacoda-scenarios](https://github.com/dragonflyoss/katacoda-scenarios)| Katacoda Scenarios for Dragonfly |
58
59
|[linter](https://github.com/dragonflyoss/linter)| linter is a very useful container image used for linter in all open source golang repositories |
59
-
|[helm-chart](https://github.com/dragonflyoss/helm-chart)| The legacy Helm chart for deploying Dragonfly. |
60
-
|[dragonfly-scripts](https://github.com/dragonflyoss/dragonfly-scripts)| dragonfly scripts for CI |
60
+
|[website](https://github.com/dragonflyoss/website)| All website material of Dragonfly |
0 commit comments