Re: New Golang Packaging Guidelines: Feedback needed and appreciated

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

 






----- Original Message -----
> From: "Robert-André Mauchin" <zebob.m@xxxxxxxxx>
> To: devel@xxxxxxxxxxxxxxxxxxxxxxx
> Cc: "nicolas mailhot" <nicolas.mailhot@xxxxxxxxxxx>, golang@xxxxxxxxxxxxxxxxxxxxxxx, jcajka@xxxxxxxxxx, "Discussion
> of RPM packaging standards and practices for Fedora" <packaging@xxxxxxxxxxxxxxxxxxxxxxx>
> Sent: Friday, March 22, 2019 7:46:23 PM
> Subject: New Golang Packaging Guidelines: Feedback needed and appreciated
> 
> 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é
> 

Thanks, great work.

I unfortunately I have managed to just go trough roughly half of them, but they look great so far. There some parts that needs minor fix up, some a bit of expanding and IMO there are some that can be omitted with just pointer to the general guidelines.

I hope that I will be able to send some PRs and open some issue/enhancement requests by the next week. Also I will try to ask someone from the Fedora docs team to take a look at the non-technical side of the things.

Thanks again for writing the new guidelines draft,

JC

> 
> _______________________________________________
> golang mailing list -- golang@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to golang-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/golang@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