let's try figure out best slot for it. https://framadate.org/DrEWMnFlw1e8Pd8J please fill in this survey so we can get best possible time for the most.
Looking forward to meet with you to discuss the issues and future plans.
Hey guys and gals,
Can we start to discuss this SIG goals? What each of you are expecting?
A few ideas:
- Making https://fedoraproject.org/wiki/More_Go_packaging official and
working on bringing them to EPEL7
- Assigning current Go packages to the SIG so each member of the SIG can work
on them, similar to https://src.fedoraproject.org/group/rust-sig
Many Google packages are inter-dependent, this would ease synchronising them.
- Working toward packaging more: I'm thinking about unbundling kubernetes and
- Developing tools to maintain up-to-date our current set of Go packages,
some of which are left outdated since their creation.
Any other ideas? I'd like to move forward as soon as possible.
----- Original Message -----
> From: "Ricardo Martinelli Oliveira" <ricardo.martinelli.oliveira(a)gmail.com>
> To: "Development discussions related to Fedora" <devel(a)lists.fedoraproject.org>
> Sent: Monday, August 6, 2018 3:47:44 PM
> Subject: Re: Golang SIG for Fedora
> I think we already have tools for that. What I expect with the SIG is
> something that could improve the Go Packaging best practices listed in
Yeah, I believe that is one of the most important tasks, but I envision that SIG will be place to kind of pool and share our resources/time/experiences and some issue/work(in addition to the BugZilla and other Fedora standart tools) tacking system could be really helpful. Place where we could put our ideas and nice to have things that we don't have time to work on currently, but not only those. It would also make more apparent to the outside progress of some bigger scope projects like the packaging guidelines.
> On Mon, Aug 6, 2018 at 9:10 AM, Vitor Ramos <lobocode(a)gmail.com> wrote:
> > I think that we can mature in the first moment the SIG, and in other
> > moment, channels, groups, and subjects in another moment. An approach
> > about the taiga is about the development of Tools that contemplate the
> > Golang in Fedora Project?
> > _______________________________________________
> > devel mailing list -- devel(a)lists.fedoraproject.org
> > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://firstname.lastname@example.org...
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
it seems that lately there has been more people maintaining Go package in the Fedora. I would like to propose to join up and form Go SIG so we could better co-ordinate and collaborate on the packaging issues and general developer experience.
There are few big outstanding issues that needs to be solved that need more than individual work, most notably the Go packaging guidelines and tooling. I think that should be one of the first tasks for the SIG.
To introduce myself. I'm for some while golang (co-)maintainer and recently started co-maintaining origin package. I'm mostly interested in the compiler and developer experience.
Please reply if you would like to participate.
PS: Also I will be at Flock this year and would like to meet up with anyone interested there.