-
Notifications
You must be signed in to change notification settings - Fork 57
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
Create a repository and templates for write access requests #188
Comments
Had a quick look at how others handle these sort of requests, for instance Joining Quarkiverse via extension_proposal.yml We can do something similar; I'm expecting a mix of documentation on https://docs.openrewrite.org, and potentially some duplicate documentation in a README for the new requests repository. I'm leaning towards a slightly different name for the repository: I want the name to be a call to action, and convey that we both invite contributors, as well as adopt existing repositories such as we did with rewrite-jenkins. With that said I'm leaning towards for instance:
And then within the repository have two issue forms, one to get access to existing repositories, and one for adopting new libraries and frameworks. We could even have the form to get access just in https://github.com/openrewrite/.github/tree/main/.github/ISSUE_TEMPLATE ; that way the form is available on every repository, and not hidden away in a different access repository. Should also help scale up such requests and immediately have the applicable people involved in that project. |
It sounds good to me 👍 |
So two forms added:
We'll likely also want to document the community and governance over on docs.openrewrite.org, and call out those two forms in a similar manner to what we've seen for Quarkiverse. |
@timtebeek No rush - just curious about the status of this. Does more work need to be done on this end? Is this blocked on anything in particular? |
The tasks laid out at the start of this issue are covered, but we do not yet refer to these forms from a "community" landing page in the OpenRewrite docs. We're also adding a community page to the moderne.io website, which might also feature links to these forms, but it's not exactly clear where to draw the line. Maybe best to close this issue and ask internally on thoughts of similarly adding a community page to the OpenRewrite docs, and linking to the collaboration proposal form from there. |
Gonna close this issue as I think this isn't being worked on anymore. Feel free to reopen if you feel like it is. |
Background
Third-party communities might want to transfer their recipe repositories. In this case, they should also have write permissions to the repositories. However, now the repository will be allocated in the openrewrite org.
Acceptance Criteria
access-requests
The text was updated successfully, but these errors were encountered: