|
RFCSC Meeting 2024-06-24
|
|
0
|
598
|
June 24, 2024
|
|
RFCSC Meeting 2024-06-10
|
|
0
|
472
|
June 10, 2024
|
|
RFCSC Meeting 2024-05-28
|
|
1
|
549
|
June 3, 2024
|
|
Pre-RFC: CycloneDX BOM taxonomy
|
|
3
|
570
|
June 2, 2024
|
|
RFCSC Meeting 2024-05-14
|
|
11
|
1391
|
May 17, 2024
|
|
RFC 171: Default name of fetchFromX to include version information
|
|
1
|
505
|
April 22, 2024
|
|
RFCSC Meeting 2024-04-16
|
|
0
|
431
|
April 16, 2024
|
|
RFCSC Meeting 2024-04-02
|
|
0
|
495
|
April 2, 2024
|
|
Pre-RFC: module system for wrappers in Nixpkgs
|
|
2
|
663
|
March 28, 2024
|
|
FCP, Prototypes and Implementations for RFCs
|
|
16
|
880
|
March 20, 2024
|
|
RFCSC Meeting 2024-03-19
|
|
0
|
459
|
March 19, 2024
|
|
Pre-RFC: Verification of the ISO
|
|
7
|
774
|
March 11, 2024
|
|
RFCSC Meeting 2024-03-05
|
|
2
|
621
|
March 6, 2024
|
|
RFC Status Summaries?
|
|
4
|
578
|
March 5, 2024
|
|
Pre-RFC: Standardization of feature parameters
|
|
72
|
3606
|
January 21, 2024
|
|
Let's improve the RFC process!
|
|
1
|
681
|
January 8, 2024
|
|
Pre-RFC: Universal Reverse Proxy interface
|
|
3
|
803
|
December 30, 2023
|
|
Shepherds needed for the Nix formatting RFC
|
|
1
|
465
|
December 12, 2023
|
|
Pre-RFC: A single canonical domain name
|
|
35
|
3055
|
November 20, 2023
|
|
RFC 0164: Nim library lockfiles
|
|
1
|
411
|
October 13, 2023
|
|
[RFC 0163] Portable Service Layer
|
|
6
|
1673
|
October 8, 2023
|
|
Pre-RFC: Visually differentiate the `?` symbol in Nixpkgs
|
|
16
|
1043
|
July 3, 2023
|
|
RFC 136: Looking for feedback on the scope
|
|
5
|
1116
|
June 22, 2023
|
|
RFC 137: Nix language versioning – call for shepherds
|
|
0
|
508
|
June 8, 2023
|
|
Improving our RFC process
|
|
25
|
2219
|
June 2, 2023
|
|
About the RFCs category
|
|
1
|
944
|
June 1, 2023
|
|
Potential RFC Idea: `Exec(Start|Stop)(Pre|Post)` as lists
|
|
3
|
568
|
April 18, 2023
|
|
Potential RFC Idea: Stability
|
|
5
|
1035
|
April 7, 2023
|
|
2023-04-03 RFC 138 Developing RFCs in Repositories Meeting #2
|
|
0
|
575
|
April 3, 2023
|
|
Shepherds needed for RFC 140
|
|
0
|
910
|
March 20, 2023
|