On 1 March 2018 at 10:12, Martín Ferrari <[email protected]> wrote: > Hi Michael, > > Thanks for moving this forward! > > On 27/02/18 21:10, Michael Stapelberg wrote: > > > dh-make-golang’s create-salsa-project subcommand now calls this logic > > via an HTTP request, so that we can update the logic independent of the > > version of dh-make-golang that users are running (we’ve seen people run > > very old versions). See > > I was going to say that my version of the tool does not have it, but > then I realised it is there, but the help or the man say nothing about > it.. Is there a reference somewhere? > > > Tincho, aviau, can you confirm that we’re good to go? > > aviau, are you still up for coordinating and doing the next steps > > (sending the announcement, migrating the repositories)? > > I have some things in mind that I think have not been resolved yet: > > * Have we decided on a naming scheme, including group name? What about > the go compiler stuff? (I think it will make sense to join everytihng > under one group) >
The salsa group is now called "go-team" and I thought that's the one we were going to stick with? The go compiler stuff should be a subgroup of the go-team group, although I don't think anything about that should block the package migration. > * What about mailing list and maintainer address? I know the perl people > solved this somehow, but I don't understand how :) > I don't know the answer to this bit. Cheers, mwh > These two are important, because we should define them before changing > all repos and mass-committing hundreds of changes. > > -- > Martín Ferrari (Tincho) > > _______________________________________________ > Pkg-go-maintainers mailing list > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers >
_______________________________________________ Pkg-go-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
