[gis] branch master updated (2245028 -> ca6e7bd)

[Bas Couwenberg]

On 2018-03-01 12:57, Andreas Tille wrote:
> CCing pkg-grass-devel list - my fault to post in private initially]
> On Thu, Mar 01, 2018 at 12:05:31PM +0100, Bas Couwenberg wrote:
>> 
>> The hook on Alioth only sent it to 
>> blends-commit at lists.alioth.debian.org
>> initially, since I don't want to force Debian GIS contributors to 
>> subscribe
>> to that list too, I added pkg-grass-devel where the commits for the 
>> regular
>> repositories go too.
> 
> In general I think it would be better to have separate lists *-devel 
> and
> *-commit - at least that's usual for other teams.

pkg-grass-devel has always been used for Maintainer related emails and 
commits.

I don't see value in splitting off the commits to a separate list, 
especially not now with the Alioth deprecation.

Creating new lists likely won't be possible on alioth-lists.d.n, as 
people are expected to subscribe to the vcs keyword in tracker.d.o.

>> We can drop blends-commit@ and only keep pkg-grass-devel@ if that's 
>> what you
>> prefer.
> 
> I do not mind much.  I'm reading blends-commit@ very frequently and
> pkg-grass-devel@ rarely and I might overlook some relevant blends
> commits in the "noise" of package commits.  But it is not only about
> me and we could even keep two lists in case this was not injected by
> incident.

I'm not subscribed to blends-commits@ either, as most of the commits are 
not related the GIS blend.

All packaging related emails which includes Maintainer related mails, 
VCS changes, etc should stay on pkg-grass-devel@ until tracker.d.o is a 
suitable replacement for Maintainer related mails.

Once we're at that point we can stop using pkg-grass-devel and 
reconfigure Salsa to send notifications to tracker.d.o. as well.

Kind Regards,

Bas