[pkg-go] Asking upstream to tag repositories

[Alexandre Viau]

On 29/03/16 01:06 PM, Martín Ferrari wrote:
> Hey,
> 
> On 29/03/16 15:05, Alexandre Viau wrote:
> 
>> I was pleasantly surprised by upstream's reaction. Most of them
>> understand that it can be helpful and only **very few** have refused to tag.
> 
> This seems actually very surprising to me. Looks like most of these
> communities don't believe in releases and would easily refuse. Maybe you
> should share your template so we all can have the same success :)

Heh. Actually, it was very easy. My template is two sentences.

Successes:
 - https://github.com/kimor79/gollectd/issues/8
 - https://github.com/Unknwon/com/issues/8
 - https://github.com/pierrec/xxHash/issues/2
 - https://github.com/mattn/go-isatty/issues/7
 - https://github.com/kimor79/gollectd/issues/8
 - https://github.com/jtolds/gls/issues/4
 - https://github.com/gosimple/slug/issues/7
 - https://github.com/dylanmei/iso8601/issues/1
 - https://github.com/cenkalti/backoff/issues/23
 - https://github.com/klauspost/crc32/issues/15
 - https://github.com/klauspost/cpuid/issues/11
 - https://github.com/paulbellamy/ratecounter/issues/5
 - https://github.com/rakyll/statik/issues/15
 - https://github.com/naoina/toml/issues/20
 - https://github.com/naoina/go-stringutil/issues/2

Example of small resistance:
 - https://github.com/klauspost/compress/issues/47 (I explained uscan)

Some saying no/not answering:
 - https://github.com/tent/http-link-go/issues/1
 - https://github.com/hashicorp/raft/issues/99


I don't know what to say. I think its about making a simple request, and
explaining when they ask questions. Sometimes they say "no because of
[blablabla]" then I try to make a counter-argument. Other times they
just say yes right away.

A good amount of my bugs are still open and waiting for answer, but that
is normal. Out of the ones I got reaction, I have a high success rate.

>> Maybe it could also be a good idea to post a statement on a sub-page of
>> the pkg-go alioth website that we can link to upstream explaining why
>> tagging go packages makes sense for projects like Debian.
> 
> +1 too! I think there is somewhere some page explaining how to be a good
> upstream.
> 
> Ah, here it is: https://wiki.debian.org/UpstreamGuide#Releases_and_Versions

Ha! Thanks.

> BTW, it seems we never got around to implement the policy changes
> discussed a couple of months ago?

I have asked Michael (secure) on IRC a couple of weeks ago and he will
do it when he has time. Only him has access to the policy repository.

-- 
Alexandre Viau
aviau at debian.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20160329/e7a7af12/attachment.sig>