You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+14-9
Original file line number
Diff line number
Diff line change
@@ -17,13 +17,16 @@ But some changes have a wider effect and require design and discussion to make s
17
17
18
18
A proposal is any change suggestion or feature idea for Qwik
19
19
20
-
**Who can create it?**
20
+
π§ **Who can create it?**
21
+
21
22
Anyone from the Qwik community can create a new proposal.
22
23
23
-
**How to create one?**
24
+
β¨ **How to create one?**
25
+
24
26
Create a [proposal discussion using the suggested template](https://github.com/QwikDev/qwik-evolution/discussions/new?category=proposals)
25
27
26
-
**Checklist for becoming a "RFC Issue"**
28
+
π **Checklist for becoming a "RFC Issue":**
29
+
27
30
-[x] Detailed and well articulated Proposal
28
31
-[x] Accepted via a Core leadership team vote
29
32
-[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.
36
39
This means the implementation exploration can be started and all related PRs should be linked in that issue.
37
40
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.
38
41
39
-
**Who can create it?**
42
+
π§ **Who can create it?**
43
+
40
44
Core team member
41
45
42
-
**Checklist for advancing to the review stage**
46
+
π **Checklist for advancing to the review stage:**
43
47
-[x] Full implementation of the proposal
44
48
-[X] All the changes are covered by tests
45
49
-[x] No unresolved critical discussions left on the issue
@@ -50,10 +54,11 @@ Core team member
50
54
51
55
The RFC related Pull requests should be reviewed and fully tested before
52
56
53
-
**Who can create it?**
57
+
π§ **Who can create it?**
58
+
54
59
Any contributor can help with the implementation of the RFC, with coordination with the core team
55
60
56
-
**Checklist for approving the implementation**
61
+
π **Checklist for approving the implementation:**
57
62
-[x] At least 2 reviewers from the core team
58
63
-[x] The necessary documentation for the feature / change is added
59
64
@@ -64,14 +69,14 @@ Any contributor can help with the implementation of the RFC, with coordination w
64
69
65
70
The PR is merged and is released under either a feature flag or a special alpha version.
66
71
67
-
**Checklist for releasing it as stable**
72
+
π **Checklist for releasing it as stable**
68
73
-[x] A period of at least 30 days of testing with community partners to gather feedback and fix bugs
69
74
70
75
.
71
76
72
77
### STAGE 5 - Stable feature
73
78
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)`.
0 commit comments