Re: New Golang Packaging Guidelines: Feedback needed and appreciated

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Mar 22, 2019 at 7:47 PM Robert-André Mauchin <zebob.m@xxxxxxxxx> wrote:
>
> Hello Fedora people,
>
>     As you may or may not know, currently applied Golang packaging guidelines
> have always been simply a « draft ». Part of the new Go SIG mission is to
> update ours best practices and tooling. As such, Nicolas Mailhot designed  a
> new set of macros based on lua script to improve our current situation. As a
> result, we needed to draft new guidelines to reflect the future implementation
> of these macros.
>
>     I have written these new guidelines and I'd like to ask for your help in
> order to review them: both from current Go SIG packagers point of view and
> from novices in the matter, in order to make sure they are clear and
> understandable enough for everyone.
>
>     I have uploaded a mirror of the Guidelines on my FedoraPeople space:
> https://eclipseo.fedorapeople.org/guidelines/packaging-guidelines/Golang/
>
>     Please, if you have 10 mn to spare, read them and send me feedback. If you
> wish you can also directly send me a Merge Request on Pagure:
> https://pagure.io/fork/eclipseo/packaging-committee/  (branch
> implement_golang_guidelines).
>
> Best regards,
>
> Robert-André

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

> _______________________________________________
> 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
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux