Skip to content

Commit da67179

Browse files
committed
formatting to readme
1 parent 65f34b6 commit da67179

File tree

1 file changed

+14
-9
lines changed

1 file changed

+14
-9
lines changed

β€ŽREADME.md

+14-9
Original file line numberDiff line numberDiff line change
@@ -17,13 +17,16 @@ But some changes have a wider effect and require design and discussion to make s
1717

1818
A proposal is any change suggestion or feature idea for Qwik
1919

20-
**Who can create it?**
20+
πŸ§‘ **Who can create it?**
21+
2122
Anyone from the Qwik community can create a new proposal.
2223

23-
**How to create one?**
24+
✨ **How to create one?**
25+
2426
Create a [proposal discussion using the suggested template](https://github.com/QwikDev/qwik-evolution/discussions/new?category=proposals)
2527

26-
**Checklist for becoming a "RFC Issue"**
28+
πŸ“ƒ **Checklist for becoming a "RFC Issue":**
29+
2730
- [x] Detailed and well articulated Proposal
2831
- [x] Accepted via a Core leadership team vote
2932
- [x] Has at least one champion from the core team
@@ -36,10 +39,11 @@ A RFC issue is a Github issue that's based on the original proposal discussion.
3639
This means the implementation exploration can be started and all related PRs should be linked in that issue.
3740
An RFC is led by champions from the Core team but the original proposal submitter could join as a community champion to provide help / insight / feedback during the exploration process.
3841

39-
**Who can create it?**
42+
πŸ§‘ **Who can create it?**
43+
4044
Core team member
4145

42-
**Checklist for advancing to the review stage**
46+
πŸ“ƒ **Checklist for advancing to the review stage:**
4347
- [x] Full implementation of the proposal
4448
- [X] All the changes are covered by tests
4549
- [x] No unresolved critical discussions left on the issue
@@ -50,10 +54,11 @@ Core team member
5054

5155
The RFC related Pull requests should be reviewed and fully tested before
5256

53-
**Who can create it?**
57+
πŸ§‘ **Who can create it?**
58+
5459
Any contributor can help with the implementation of the RFC, with coordination with the core team
5560

56-
**Checklist for approving the implementation**
61+
πŸ“ƒ **Checklist for approving the implementation:**
5762
- [x] At least 2 reviewers from the core team
5863
- [x] The necessary documentation for the feature / change is added
5964

@@ -64,14 +69,14 @@ Any contributor can help with the implementation of the RFC, with coordination w
6469

6570
The PR is merged and is released under either a feature flag or a special alpha version.
6671

67-
**Checklist for releasing it as stable**
72+
πŸ“ƒ **Checklist for releasing it as stable**
6873
- [x] A period of at least 30 days of testing with community partners to gather feedback and fix bugs
6974

7075
.
7176

7277
### STAGE 5 - Stable feature
7378

74-
RFC Issue is closed and moved to "Released as Stable (STAGE 5)".
79+
RFC Issue is closed and moved to `Released as Stable (STAGE 5)`.
7580

7681
Oh happy days! πŸ˜ŠπŸŽ‰
7782

0 commit comments

Comments
Β (0)