[WIP] RFCs

[turnrye]

This is an early draft of a proposed RFC repo and process. It's very very similar to what exists today on React. I'm still researching other RFC processes and trying to incorporate additional improvements. If there's any early feedback on this, feel free to share or even directly make a change if you're so compelled.

[kelset]

maybe change rfcs/0000-my-feature.md to rfcs/XXXX-my-feature.md?

[turnrye]

The RFC number isn't known until the PR is made; they wont know it yet.

[kelset]

Yes it was simply to "make more clear" that is was still an undefined number. No strong opinions anyway

[kelset]

Friday team meeting?

[turnrye]

Oops! Leak :)

[kelset]

Left a couple comments here, but overall 100% solid and I like it.

Side things:

1. should we then move the CHANGELOG into a /changelog/ folder with a file per each major version? I feel it would help keeping clear the "separation" of the various elements of this repo

2. should we move all the For Discussions labelled issues on the main repo to this format? Would be a good way to get a pool of RFCs here right away (also to make it easier to understand which kind of subjects should be discussed via RFC)

3. Should the RFC folder also have a .md file with an overview of all the RFC open and maybe a quick "recap" of the proposal, or something like that?

[turnrye]

I agree with moving the changelog to a separate directory, however I do believe that it stay unified in one file. This is consistent with most other projects. I do think there's more progress to be made on streamlining the changelog though.

I like the idea of converting For Discussion to RFCs; I fear however that if we move them over for users, they may not feel ownership of them. I'd suggest instead incentivising users to move them.

The filtered PR link should show all of the open ones. I'm open to tracking statuses in another way, especially if it can include more context for the change (like the summary).

[kelset]

I'm comfortable with moving the changelog to a separate directory, however I do believe that it stay unified in one file. This is consistent with most other projects. I do think there's more progress to be made on streamlining the changelog though.

Gotcha. That's fine then.

I like the idea of converting For Discussion to RFCs; I fear however that if we move them over for users, they may not feel ownership of them. I'd suggest instead incentivising users to move them.

I'll double check if there is a way of "migrating" an issue from a repo to another, but yeah I see what you mean.

The filtered PR link should show all of the open ones. I'm open to tracking statuses in another way, especially if it can include more context for the change (like the summary).

My idea behind having a "recap" was more like, to allow people to have a quick overview since it's probably the closest thing to a roadmap we could have on the OSS side.

[turnrye]

Got input outside of Github that we should consider this less of a strict RFC approach and instead as broader planning and proposals. Going to do some revs tonight with that in mind.

[turnrye]

I didn't get through changes to the proposal template, but I did update a draft of the README this evening.

[kelset]

let's close this in favour of https://github.com/react-native-community/discussions-and-proposals ?