aboutsummaryrefslogtreecommitdiff
path: root/maintainers/README.md
AgeCommit message (Collapse)Author
2023-03-16Prioritize testing in the maintainers process docsJohn Ericson
PRs that don't increase our ongoing obligations (i.e. by adding new features) but do increase test coverage of existing features are good things to merge for the health of the project, and thus good to prioritize.
2023-03-13Merge pull request #7534 from fricklerhandwerk/maintainers-goalsValentin Gagarin
add objectives and tasks for Nix team
2023-03-06Merge pull request #7580 from fricklerhandwerk/nix-team-add-johnEelco Dolstra
add @Ericson2314 to the Nix team
2023-02-24incorporate feedback from maintainersValentin Gagarin
2023-02-24add objectives and tasks for Nix teamValentin Gagarin
so far there were no even remotely measurable objectives, only a general purpose statement. this change is intended to focus the team's work on what I (and many others I talked to) perceive to be the main pain point in the development process. Co-authored-by: solene.rapenne@tweag.io
2023-01-12state priorities in triaging and discussion processValentin Gagarin
based on - Nix team decisions https://discourse.nixos.org/t/2022-11-11-nix-team-meeting-minutes-7/23451#planning-discussion-1 https://discourse.nixos.org/t/2022-12-02-nix-team-meeting-minutes-13/23731#discussion-3 - proposal to deal use labels more effectively https://discourse.nixos.org/t/improving-nix-developer-experience/21629 - documentation team decision to foster gauging interest using upvotes https://github.com/NixOS/nix/pull/7387
2023-01-11add @Ericson2314 to the Nix teamValentin Gagarin
John has been part of every meeting since the beginning. He took on a lot of work on behalf of the team, and provided useful suggestions in discussions, advocating for stability, reasonable design decisions, and maintainable code. He was in general highly productive within the team process, and repeatedly helped us to keep focus on our stated goals. Specifically, early on he suggested to gather more experience with the team reviews in order derive our values for the project encode a more structured approach to guiding contributions, which is slowly bearing fruit these days. John is already the contributor with the most code changes to date (only topped by principal author Eelco), and is well-known to be highly knowledgeable about both high-level design and low-level internals of the code base. He has continued to offer high quality work during the team's operation, which resulted in many pull requests getting merged that further the team's goals. It is due time for John to be come an official team member and be granted merge access that he will surely exercise with the great care he is known for.
2022-12-05maintainers/README.md: Use CETEelco Dolstra
2022-12-05Fix typoEelco Dolstra
2022-11-21rewordValentin Gagarin
2022-11-21add maintainers' handbookValentin Gagarin
write down the process we have been developing and following so far. Co-Authored-By: Théophane Hufschmitt <theophane.hufschmitt@tweag.io> Co-Authored-By: John Ericson <John.Ericson@Obsidian.Systems>