Attendees: @fricklerhandwerk @lucperkins @infinisil @domenkozar
Notes: @fricklerhandwerk
-
tried to discuss how to achieve a cleaner separation between nix-book and nix.dev ) (15 min)
decision: introduce a clear distinction between Tutorials and Guides on nix.dev; see if we can merge efforts in one location
-
final discussion on fixing terminology (10 min)
decision: will merge soon
-
discussed new Nix language tutorial (15 min)
decision: wait for reviews
-
discussed proposal for contribution guide (10 min)
decision: will merge soon
Other topics
-
@infinisil we should have a single scratchpad, then all meeting parameters will be constant and can be linked in a calendar event
- @fricklerhandwerk good, starting next time
-
@infinisil would be good to have a GitHub team for Nix documentation
- will create one
Next time
-
@fricklerhandwerk would like to talk about visual outline
- make it smaller and focused on nix.dev, link to existing tutorials
-
@domenkozar also make honeypot links, where clicking would prompt people to create an issue from a template
-
@fricklerhandwerk can we program this like
mailto:URLs (where it’s possible to pre-fill the email)?- is that possible
- @domenkozar actually yes
- is that possible
- no, it would be enough to pre-create the issues, as there will be not too many anyway
- also creating too many issues will be confusing
- @infinisil instruct people to vote on them to figure out priorities
-
@fricklerhandwerk can we program this like
-
@fricklerhandwerk we don’t have a way to measure priorities
-
@infinisil there are just too many things to work on
- @fricklerhandwerk exactly, this is why we need some handle on what’s important
- what about the following: create an issue/pull request query sorted by thumbs up
- instruct users to look through that list and vote with thumbs up
- instruct maintainers to look into that query and actually work it off in order
- @infinisil @domenkozar sounds good
- will update
-
@infinisil there are just too many things to work on