Propose creation of project community resources #42
Conversation
|
For what its worth, we received the following feedback about the project from an internal customer:
And re. WG meetings:
|
zmackie
changed the title
|
I wonder if this RFC should also include the creation of a "project contributors" team for people who want to do this sort of work. |
Signed-off-by: Zander Mackie <zmackie@pivotal.io>
text/0000-landing-page.md
Outdated
| - Purpose of the project and high level overview including some canonical talk from youtube, etc | ||
| - Technical overview, including guides to the various components of the projects and links to their respective repos | ||
| - Project and community overview, including key personel, governance structures, link to slack, calendar links, and links to a contribution guide (this document is likely sufficiently detailed as to necessitate a seperate document beloew) | ||
| - `contributing.md` which details the RFC process and various other pieces of information about how to get started contributing to the project |
There was a problem hiding this comment.
It might be useful to include an section on "When should I open an RFC?", with examples or heuristics as well as the default disposition (ie start with an issue or a PR and that can be upgraded to an RFC if deemed necessary or vice-versa). I realize that the RFC RFC sort of touches on this but it seems a little vaguely specficied at the moment
Something like:
**RFC**
- Add new field to `buildpack.toml`
- Create new repo in the project
**No RFC**
- Bug in pack
- Modify language in logging headers
text/0000-landing-page.md
Outdated
| [unresolved-questions]: #unresolved-questions | ||
|
|
||
| - Should this include some sort of roadmap? This would ideally give people a sense of where they can start to chip in | ||
| - Should we host our WG meetings out of the CNCF calendar so they're more publicall discoverable? Who moderates the zoom? |
There was a problem hiding this comment.
Yes, and someone nominated by Core team. It should be the responsibility of a single person (for consistency and commitment) with occasional substitution as needs arrive. It should also not be forever, but something that can be passed on after some period of time.
Signed-off-by: Zander Mackie <zmackie@pivotal.io>
| [outcomes]: #outcomes | ||
|
|
||
| - New contributors feel welcomed. | ||
| - A new contributor can easily find information they want about the project, can join the slack and WG meetings, and can quickly contribute pull-requests, RFCs, and issues. |
There was a problem hiding this comment.
It's been pointed out before that publicly publishing the zoom WG meeting details could be problematic as we currently have no way of moderating anybody with the link participating.
An open question for me is if this rolls up under the "Learning" subteam or if there's enough that it's own thing. I do believe there is a general overlap between the two. For instance, as a user you're interested in:
It'd be great to see in this RFC how to distinguish what goes on the website vs in this proposed repo. |
|
We should definitely link out to a Code of Conduct in here. |
|
The code of conduct should automatically be shown for all the repos in the |
…ds the mailing list to comms Signed-off-by: Zander Mackie <amackie@pivotal.io>
|
🚢 !! |
Readable