Re: How to get some replacement for a commit list
On Fri, Jan 12, 2018 at 04:32:22PM +0100, Sébastien Villemot wrote:
> > $ emails_on_push.sh r-pkg-team email@example.com
> > Project r-pkg-team not found among your owned projects on https://salsa.debian.org/api/v4 service
> > $ emails_on_push.sh science-team firstname.lastname@example.org
> > Project science-team not found among your owned projects on https://salsa.debian.org/api/v4 service
> Notifications have to be set up on a per-project basis, not on a group-basis.
Ahhh, I should have read more closely.
> I am currently writing a script to list all the projects of a group,
That's *very* interesting. I also need it for the Blends metadata
gatherer. This needs d/changelog, d/control, d/upstream/metadata of all
projects of a packaging team. If you dive into this I'd be really happy
to get hints. On Alioth this was easy by running a cron job on the
machine iterating through all dirs of a team and fetching the debian/
dir. The Alioth -> Salsa move is breaking this (and other things for
the Blends tools).
> Also, I'm not sure it's a good model to have each of us add his personal
> address to the configuration of projects on which he/she has admin rights… The
> tracker.d.o address is really the prefered way.
Definitely. Having personal addresses per project seems to be a really
safe way to get lots of e-mail addresses and projects forgetten in one
or the other way.