Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What: update project proposals doc #816

Merged
merged 5 commits into from
Jun 13, 2022

Conversation

TheFoxAtWork
Copy link
Contributor

Why:

  • capture new Annual Review for sandbox
  • small updates as discussed to refresh the doc.

This change addresses the need by:

Why:

* capture new Annual Review for sandbox
* small updates as discussed to refresh the doc.

This change addresses the need by:

*  capture contents from cncf#815
* call out no lobbying for sponsors.
@amye
Copy link
Contributor

amye commented Mar 24, 2022

You may want to reconcile this with what's in the README doc, I can help collate these changes next week. (March 29th - onwards.)

@TheFoxAtWork
Copy link
Contributor Author

@amye wilco.

@dzolotusky
Copy link
Contributor

Beyond "Lobbying for a sponsor is not permitted.", should we add something suggesting that the project should reach out to either the entire TOC or to Amye if they are concerned about the timeline, feel they have waited too long, or just have any other reason to want to reach out to various TOC members directly?

Basically, saying "don't single out TOC members, if you have an ask, send it to the entire TOC or to nobody"

@dims
Copy link
Member

dims commented Mar 30, 2022

@dzolotusky feels like they should be able to raise a concern on toc public or private mailing list no? (they can talk to Amye as well as needed!)

@dzolotusky
Copy link
Contributor

@dzolotusky feels like they should be able to raise a concern on toc public or private mailing list no? (they can talk to Amye as well as needed!)

Sure, that sounds fine to me. I guess I didn't specify the mechanism for "if you have an ask, send it to the entire TOC or to nobody", but suggesting the two mailing lists and/or Amye sounds fine to me.

@amye
Copy link
Contributor

amye commented Mar 30, 2022

Let's say 'CNCF staff' instead? Make this repeatable and helpful. 😂

@dims
Copy link
Member

dims commented Mar 30, 2022

LOL yes indeed :)

@TheFoxAtWork
Copy link
Contributor Author

Done.

* TOC Incubation Sponsor is responsible for driving the process, and co-ordinating with TAGs for review and input as they see fit.
* TOC Incubation Sponsor is a point of contact for the project throughout the process.
* TOC members may not sponsor a project for which they have a clear conflict of interest (for example, originating primarily from their organization). This doesn't mean that they can't have any involvement at all - for example, contributing pull requests, or being an end user of that project, can signal a healthy interest in and knowledge of a worthwhile project.
. *Due Diligence* _2-3 months_
* TOC Incubation Sponsor drives due diligence (see the [https://github.com/cncf/toc/blob/main/process/dd-review-template.md](template) and [https://github.com/cncf/toc/blob/main/process/due-diligence-guidelines.md](guidelines)).
* TOC Incubation Sponsor drives due diligence (see the [temaplte](https://github.com/cncf/toc/blob/main/process/dd-review-template.md) and [guidelines](https://github.com/cncf/toc/blob/main/process/due-diligence-guidelines.md).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tiny typo!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants