[RFC] Add partner application process to ECOSYSTEM.md #37689
Conversation
## Overview This PR updates the ECOSYSTEM.md with more information for how to apply to be a partner, and includes an update to the joining process including a 3 month incubation period. It also emphasizes that being a partner is a commitment of resources to improve React Native, and not a status symbol.
facebook-github-bot
added
CLA Signed
|
rickhanlonii
changed the title
Base commit: 0201e51 |
| * Contributing to the release process. Examples include being a [community releaser](https://reactnative.dev/contributing/release-roles-responsibilities#release-role-2-community-releaser), testing new releases, technical support for release issues. | ||
| * Engage on the core contributor Discord | ||
| ### Application process | ||
| To become a React Native partner, an existing partner needs to refer and champion your application. Partners will undergo a 3 month incubating period, after which Partners will vote to convert to full membership. |
There was a problem hiding this comment.
an existing partner needs to refer and champion your application
I don't think this aspect was discussed/mentioned during the meeting?
There was a problem hiding this comment.
I do recall us talking about partners referring others, what are your concerns around this? Feel free to message the group about this too
| Maintaining partner status requires consistently meeting the baseline responsibilities, including: | ||
| * Attending monthly meeting. | ||
| * Contributing to the release process. | ||
| * Engaging in the core contributor Discord. |
There was a problem hiding this comment.
| Maintaining partner status requires consistently meeting the baseline responsibilities, including: | |
| * Attending monthly meeting. | |
| * Contributing to the release process. | |
| * Engaging in the core contributor Discord. | |
| Maintaining partner status requires consistently meeting the baseline responsibilities, including: | |
| * Attending monthly meeting. | |
| * Contributing to the release process. | |
| * Engaging in the core contributor Discord. | |
| * Meaningfully contribute to the ecosystem and the broader community |
since most existing partners do very important things (ex IR and Callstack and Expo+SWM doing the confs, Wix maintaining their libs) for the broader community it might be worth to mention? Like more partners do support the broader community than the ones contributing to the release process, so might be worth to have some sort of mention there for perspective partners to consider themselves "reaching the bar" for applying
There was a problem hiding this comment.
I agree with @kelset. Maybe not all partners should contribute to the release process but have meaningful contributions to the ecosystem. I think a good idea is to add examples of meaningful contributions (doesn't need to be concrete) as the definition is very vague. We mentioned in the meeting that it could be code contributions to core and popular libraries but also conferences and podcasts.
There was a problem hiding this comment.
Great points. I didn't change any of these here though, just changed the formatting, so let's followup to up if we want to change the baseline responsibilities.
| ### Incubating partners: | ||
| * There are no current incubating partners. | ||
|
|
||
| When you are contributing to React Native, you'll most likely meet somebody who works at one of the partner companies and who is a core contributor. |
There was a problem hiding this comment.
nit: I'm not sure I understand why this phrase is here/what purpose it serves; is it to help perspective partners understand how they can find someone to champion them? 🤔
There was a problem hiding this comment.
This was there before; it feeds to the next section about core contributors and delineates the difference between Partner (company) and Contributor (individual).
| * Contributing to the release process. | ||
| * Engaging in the core contributor Discord. | ||
|
|
||
| Examples of contributing to the release include being a [community releaser](https://reactnative.dev/contributing/release-roles-responsibilities#release-role-2-community-releaser), testing new releases, and technical support for release issues. |
There was a problem hiding this comment.
Not totally related to this doc but I think is a good idea to clarify in the release role doc that becoming part of the release crew is a multi month commitment until the baton is passed to the next crew. Additionally, the release crew is responsible for all active releases in the support window, not just the upcoming one.
There was a problem hiding this comment.
| Maintaining partner status requires consistently meeting the baseline responsibilities, including: | ||
| * Attending monthly meeting. | ||
| * Contributing to the release process. | ||
| * Engaging in the core contributor Discord. |
There was a problem hiding this comment.
I agree with @kelset. Maybe not all partners should contribute to the release process but have meaningful contributions to the ecosystem. I think a good idea is to add examples of meaningful contributions (doesn't need to be concrete) as the definition is very vague. We mentioned in the meeting that it could be code contributions to core and popular libraries but also conferences and podcasts.
|
@rickhanlonii has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
@rickhanlonii has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
This pull request was successfully merged by @rickhanlonii in 9e1c3d2. When will my fix make it into a release? | Upcoming Releases |
Overview
This PR updates the ECOSYSTEM.md with more information for how to apply to be a partner, and includes an update to the joining process including a 3 month incubation period.
It also emphasizes that being a partner is a commitment of resources to improve React Native, and not a status symbol.
Changelog: internal