On Friday, 22 March 2019 22:37:06 CET Fabio Valentini wrote: > > Hi Robert-André, > > It looks like you put a lot of work into this - I don't think I've > seen as comprehensive a documentation as this Draft is for any other > aspect of packaging (but well, Go packaging is notoriously difficult > to get right, so I think comprehensive documentation is in order, and > was sorely lacking). > > I hope we can finally make the Go packaging guidelines official (and I > hope to be able to help with this as an FPC member). > > Some initial suggestions: I think the page is rather lengthy, so > splitting off the "Advanced Use cases" and "Additionnal annotated > templates" sections (maybe even the "Examples" section) into separate > sub-pages, similar to how the Python packaging guidelines are > organized, would probably be good. Adding a `:toc:` to the top of the > page would also help. > > If I have some spare time tomorrow, I can send you a PR / PRs with my > suggestions. > > Thank you, > Fabio > Thank you. I agree that the templates should be split off, they are a bit long and redundant with the page (they explain some less useful macros I believe). I think the examples should stay on the page, they are often the first thing I check out when I look at guidelines (for ex Rust ones). I could probably cut some non-interesting console output from "Advanced Use cases" to reduce the size. Best regards, Robert-André _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
