<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 28, 2018 at 10:12 PM, MartÃn Ferrari <span dir="ltr"><<a href="mailto:tincho@debian.org" target="_blank">tincho@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Michael,<br>
<br>
Thanks for moving this forward!<br>
<span class="gmail-"><br>
On 27/02/18 21:10, Michael Stapelberg wrote:<br>
<br>
> dh-make-golang’s create-salsa-project subcommand now calls this logic<br>
> via an HTTP request, so that we can update the logic independent of the<br>
> version of dh-make-golang that users are running (we’ve seen people run<br>
> very old versions). See<br>
<br>
</span>I was going to say that my version of the tool does not have it, but<br>
then I realised it is there, but the help or the man say nothing about<br>
it.. Is there a reference somewhere?<br></blockquote><div><br></div><div>No, dh-make-golang subcommands are fairly new and undocumented. I filed <a href="https://github.com/Debian/dh-make-golang/issues/91">https://github.com/Debian/dh-make-golang/issues/91</a> to track the cleanup I had planned.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class="gmail-"><br>
> Tincho, aviau, can you confirm that we’re good to go?<br>
> aviau, are you still up for coordinating and doing the next steps<br>
> (sending the announcement, migrating the repositories)?<br>
<br>
</span>I have some things in mind that I think have not been resolved yet:<br>
<br>
* Have we decided on a naming scheme, including group name? What about<br>
the go compiler stuff? (I think it will make sense to join everytihng<br>
under one group)<br></blockquote><div><br></div><div>I agree with mwhudson’s reply — go-team as group name is what we settled on (see my thread on the subject, which had a long feedback time window). I’m okay with the compiler team being a subgroup.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
* What about mailing list and maintainer address? I know the perl people<br>
solved this somehow, but I don't understand how :)<br>
<br>
These two are important, because we should define them before changing<br>
all repos and mass-committing hundreds of changes.<br></blockquote><div><br></div><div>Can you explain why the maintainer address needs to be changed in the same step as the repository move?</div><div><br></div><div>As far as I’m concerned, we can leave it as-is for the time being. The mailing list will be migrated, and there will be a separate turn-down cycle for that in a few years.</div></div><div><br></div>-- <br><div class="gmail_signature">Best regards,<br>Michael</div>
</div></div>