-
Notifications
You must be signed in to change notification settings - Fork 232
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
Add the donation checklist to the repo guidelines #102
Comments
So... This actually is spelled out (as we discovered Thursday), and it's not that list :) |
I think it's worth leaving this open to make it more discoverable, but it exists. |
I think the guidelines are insufficient, and hence why that checklist grew organically out of previous requests. E.g. there's nothing in the documented guidelines about Steering having a voice about a fit to project scope. The documented steps are a very tactical "do this than that" kind of thing, without the strategic/project elements included, which are more visible in the checklist. I'd like to see us combine elements of the checklist into what we've documented, and ideally give that checklist in markdown that people can include in their request. Perhaps an Issue template? |
Also, we shouldn't leave issues open to fix discoverability problems. |
I meant leave it open to track FIXING the discoverability issues 😉 |
I think we are close to having this closed by #151 |
/close |
There's a nice donation checklist that a few people have used in their Issues to donate code to the Knative project. However, this template and the actions required by it are not spelled out anywhere in the repo guidelines.
We should clean that up into a documented process, instead of a shared knowledge thing.
The text was updated successfully, but these errors were encountered: