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

Migrating a repo into the React Native Community #34

Closed
kelset opened this issue Jun 14, 2019 · 3 comments
Closed

Migrating a repo into the React Native Community #34

kelset opened this issue Jun 14, 2019 · 3 comments
Labels
discussion Let's talk about stuff

Comments

@kelset
Copy link
Contributor

kelset commented Jun 14, 2019

We should really define "once and for all" what the flow for this should be, so that we can write it somewhere & communicate to people who wants to go for this.

At the moment, over time it sort of became standard to open an issue in the D&P repo, similar to what happened in this situation:

react-native-community/discussions-and-proposals#135

I wonder if this should happen instead on this repo, so that it's not "noising" the other discussions.

Note: I don't want here & now define "what it takes" to have a repo join the Comm, just "the happy path". This other topic is probably literally a case-by-case scenario.

@kelset kelset added the discussion Let's talk about stuff label Jun 14, 2019
@kelset
Copy link
Contributor Author

kelset commented Jul 10, 2019

Btw, short list of things that should happen when moving a repo into the RNComm:

  • main maintainer set to admin for the repo
  • main maintainer added to the org as member + the maintainers team
  • repo should be adding the codeowners file + the protect master branch settings

@lucasbento
Copy link

Also make sure that the main maintainer is in the React Native Community discord server.

@kelset
Copy link
Contributor Author

kelset commented Sep 4, 2020

Hey folks, I'm going to close this issue. I should have probably closed it off once I stopped being an owner of the org and while some conversation around this happened I feel that given the "0 executive power" of these conversations it's better to just close them off - so not to give the misleading signal that something is currently being done on my side (or by anyone tbh) around it.

If and when this topic will get picked up again it's much healthier for whoever will actually handle it to just open a new issue. I'm not against the new issue picking up this same conversation, even copy/pasting stuff from here - but I want to close the ones opened up by me off.

@kelset kelset closed this as completed Sep 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Let's talk about stuff
Projects
None yet
Development

No branches or pull requests

2 participants