@@ -255,22 +255,34 @@ Committees follow to handle a prospective donation.
255
255
256
256
1 . Per the above, the donating organization creates a GitHub issue using
257
257
the "Donation Proposal" form in the ` community ` repository.
258
- 2 . The Technical Committee (TC) will do diligence, write a report, and attach
259
- that report to the GitHub issue. Writing the report may require meeting and
260
- discussing alternative technologies with different vendors in the community
261
- and can be a lengthy process. The TC member driving the report will post
262
- updates and time estimates to the issue.
263
- 3 . The Governance Committee (GC) will consider the report and make a final
264
- decision about the donation. The GC must ensure that the donation is aligned
265
- with the overall OpenTelemetry project vision and roadmap and has a balanced
266
- set of interested contributors and maintainers. The GC is also responsible
267
- for driving awareness in the community about the contribution and making
268
- sure all interested parties have a chance to object and/or contribute.
269
- 4 . If accepted, the contributing organization – particularly if it's a
258
+ 2 . The Governance Committee (GC) will evaluate the proposal to ensure that
259
+ the donation is aligned with the overall OpenTelemetry project vision
260
+ and roadmap and has a balanced set of interested contributors and maintainers.
261
+ The GC is also responsible for driving awareness in the community about
262
+ the contribution and making sure all interested parties have a chance to
263
+ object and/or contribute. The GC should work with any appropriate Special Interest
264
+ Groups or Working Groups to evaluate the donation proposal, consider alternatives,
265
+ and ensure OTel has the resources required to support the donation. When
266
+ considering alternatives, the GC should consider at least the CNCF ecosystem,
267
+ and may also consider other well-known open source projects or alternatives proposed
268
+ by the community.
269
+ 3 . If a donation proposal passes the initial GC screening, the Technical Committee (TC)
270
+ will conduct due diligence to determine if the proposed donation can be effectively
271
+ integrated into the OpenTelemetry project in a way that meets the quality, security,
272
+ and privacy standards of the project without violating stable specification or OTEPs.
273
+ The TC will summarize their findings, and make a recommendation to either,
274
+ conditionally or unconditionally, accept or reject the proposal, in a report which will
275
+ be attached to the donation proposal issue. Writing the report may require meeting
276
+ and discussing alternative technologies with different vendors in the community and
277
+ can be a lengthy process. The TC member driving the report will post updates and time
278
+ estimates to the issue.
279
+ 4 . The GC will consider the report and make a final decision about the donation,
280
+ and document that decision on the donation proposal issue.
281
+ 5 . If accepted, the contributing organization – particularly if it's a
270
282
commercial entity – must formally acknowledge via the GitHub issue that its
271
283
respective sales and marketing departments have received, understood, and
272
284
accepted the terms of the [ OpenTelemetry marketing guidelines] ( https://github.com/open-telemetry/community/blob/main/marketing-guidelines.md ) .
273
- 5 . Given all of the above, the GitHub issue is closed and the donation moves
285
+ 6 . Given all of the above, the GitHub issue is closed and the donation moves
274
286
forward as agreed to by the TC and GC.
275
287
276
288
## Communication
0 commit comments