About the RFCs category
|
|
1
|
459
|
June 1, 2023
|
Pre-RFC: pipe operator `|>`
|
|
15
|
1290
|
September 4, 2023
|
Pre-RFC: Visually differentiate the `?` symbol in Nixpkgs
|
|
16
|
435
|
July 3, 2023
|
RFC 136: Looking for feedback on the scope
|
|
5
|
567
|
June 22, 2023
|
RFC 137: Nix language versioning – call for shepherds
|
|
0
|
213
|
June 8, 2023
|
Improving our RFC process
|
|
25
|
962
|
June 2, 2023
|
Potential RFC Idea: `Exec(Start|Stop)(Pre|Post)` as lists
|
|
3
|
267
|
April 18, 2023
|
Potential RFC Idea: Stability
|
|
5
|
470
|
April 7, 2023
|
2023-04-03 RFC 138 Developing RFCs in Repositories Meeting #2
|
|
0
|
214
|
April 3, 2023
|
Shepherds needed for RFC 140
|
|
0
|
360
|
March 20, 2023
|
[RFC 0144] Versioned Flake References
|
|
0
|
205
|
March 19, 2023
|
2023-03-06 RFC 138 Developing RFCs in Repositories Meeting #1
|
|
1
|
259
|
March 6, 2023
|
Migrate all Rust packages to `importCargoLock`
|
|
0
|
302
|
February 19, 2023
|
Draft RFC: Private Derivations - Derivations Without Read Access
|
|
0
|
205
|
February 3, 2023
|
Stalled RFCs - Proposing closing RFCs with no interest
|
|
0
|
291
|
September 24, 2022
|
Brainstorming for RFC: pname and version
|
|
102
|
3003
|
February 23, 2022
|
Locked RFCs: why and for how long?
|
|
1
|
577
|
November 4, 2021
|
Announcement: Community Team RFC
|
|
4
|
1035
|
October 23, 2021
|
Looking for RFC98 shepherds
|
|
2
|
733
|
August 14, 2021
|
RFCs looking for shepherds
|
|
1
|
661
|
July 22, 2021
|
RFC Process Inspiration from BORS
|
|
1
|
612
|
May 26, 2021
|