In reply to @philipp:xndr.de
I all! I finally have time and energy for nixos stuff again. The thing I'm most interested in advancing RFC145 and providing documentation to previously undocumented functions outside of lib that are very relevant to many maintainers and that I personally also use outside of nixpkgs. I'm currently reading up all the discussions. It's a lot so if anybody can point me in a general direction of open tasks that aren't rejected in another thread or more generally what I could do to be helpful, I'd be very happy.

Programming stuff where i could need help:

• https://github.com/NixOS/nixpkgs/pull/262987
• Extend the current python rendering: https://github.com/NixOS/nixpkgs/pull/281212
• https://github.com/nix-community/nixdoc/pull/91

Documentation stuff:

• Write: Just visit noogle.dev and pick a random function that is not documented. Place a doc-comment (see rfc145) at the position that noogle gives you. (Sometimes position tracking doesn't work yet, especially for functors.)
• Extend the scope: danielsidhion: https://github.com/nix-community/noogle/pull/68. Once the CI finishes: https://noogle.dev/f/pkgs/appimageTools/wrapAppImage should display your wrapAppImage content. Unfortunately there is nothing documented ;)

Thanks. I am always looking to extend the scope of Noogle.

If we use the current toolset that i have as a benchmark. Given the 1.5k noogle discovered functions the answer currently is somewhat ~95%. Maybe we can get better, but we have to understand some more edge cases. A correct position tracking is Key to finding the doc-comments.

In the future this may become part of native nix, but thats a long way to go. And I currently focus on building incrementally better tools, until all questions are resolved and either I or somebody else volunteers to integrate that into nix natively.

Hey, every piece of help is very valuable ;)

Programming stuff where i could need help:

• https://github.com/NixOS/nixpkgs/pull/262987
• Extend the current python rendering: https://github.com/NixOS/nixpkgs/pull/281212
• https://github.com/nix-community/nixdoc/pull/91

Documentation stuff:

• Write: Just visit noogle.dev and pick a random function that is not documented. Place a doc-comment (see rfc145) at the position that noogle gives you. (Sometimes position tracking doesn't work yet, especially for functors.)
• Extend the scope: danielsidhion: https://github.com/nix-community/noogle/pull/68. Once the CI finishes: https://noogle.dev/f/pkgs/appimageTools/wrapAppImage should display your wrapAppImage content. Unfortunately there is nothing documented ;)

Thanks. I am always looking to extend the scope of Noogle.

If we use the current toolset that i have as a benchmark. Given the 1.5k noogle discovered functions the answer currently is somewhat ~95%. Maybe we can get better, but we have to understand some more edge cases. A correct position tracking is Key to finding the doc-comments.

In the future this may become part of native nix, but thats a long way to go. And I currently focus on building incrementally better tools, until all questions are resolved and either I or somebody else volunteers to integrate that into nix natively.

Hey, every piece of help is very valuable ;)

Programming stuff where i could need help:

• https://github.com/NixOS/nixpkgs/pull/262987
• Extend the current python rendering: https://github.com/NixOS/nixpkgs/pull/281212
• https://github.com/nix-community/nixdoc/pull/91

Documentation stuff:

• Write: Just visit noogle.dev and pick a random function that is not documented. Place a doc-comment (see rfc145) at the position that noogle gives you. (Sometimes position tracking doesn't work yet, especially for functors.)
• Extend the scope: danielsidhion: https://github.com/nix-community/noogle/pull/68. Once the CI finishes: https://noogle.dev/f/pkgs/appimageTools/wrapAppImage should display your wrapAppImage content. Unfortunately there is nothing documented ;)

Thanks. I am always looking to extend the scope of Noogle.

If we use the current toolset that i have as a benchmark. Given the 1.6k noogle discovered functions the answer currently is somewhat ~95%. Maybe we can get better, but we have to understand some more edge cases. A correct position tracking is Key to finding the doc-comments.

In the future this may become part of native nix, but thats a long way to go. And I currently focus on building incrementally better tools, until all questions are resolved and either I or somebody else volunteers to integrate that into nix natively.