Draft Notes for the OSS Core Meeting #52
Conversation
| @@ -0,0 +1,33 @@ | |||
| # Open Source Maintenance: November 2018 Core Meeting | |||
There was a problem hiding this comment.
I dont think we should call this "core". Can we call this "contributors" meeting ? We don't want to make this exclusive
There was a problem hiding this comment.
We always called them Core meeting (check the other notes) - and they are exclusive, since participation is limited to the developers in the Slack 🤷♂️
There was a problem hiding this comment.
And the paragraph right below this title clearly explains the nature of the core, so I don't see any issue with this wording.
There was a problem hiding this comment.
That said, what could be done is:
- come up with a clearer set of rules that defines what is a "core" contributor (good reference: https://www.youtube.com/watch?v=376dz1oIr3g)
- reword across the whole repo this concept, reflecting what decided in point 1
There was a problem hiding this comment.
I've also created a dedicated discussion for this -> #59
|
I think we are good to publish these notes. |
core-meetings/2019-11-oss-meeting.md
Outdated
| 3. The [Releases.md](https://github.com/facebook/react-native/blob/master/Releases.md) file will be updated to reflect the current set of steps necessary for a release | ||
| 4. For cherry pick requests, in case of complexities emerging during the release process, the author of the request will be asked to create a PR towards the branch | ||
| 5. The FB team will attempt to be more empathetic when landing commits like React syncs to prevent issues | ||
| 6. Another maintenance meeting will happen before end of the year, and among other things we'll discuss about merging the two GitHub organizations React Community and React Native Community and we'll create a shared guideline for how to maintain repos in them |
There was a problem hiding this comment.
Can we get some clarification on this point? I mean it's been probably all said - it's just that I didn't take part in the meeting.
1/ What is the motivation to merge them?
2/ Is the React Community going to stay, but be renamed to e.g. Expo Community where Expo-related modules are going to stay?
CC: @brentvatne, you might be the person to answer this more in details! Thank you :)
There was a problem hiding this comment.
This has not been discussed, that line is basically a "homework for next time" thing - I'll word it better. But overall the sentiment is that it would allow better understanding and management and stability of the components maintained in there.
There was a problem hiding this comment.
I've changed the wording to make this more clear and less like, we are taking decisions on this now.
Please review and LMK 😊