Re: [Reproducible-builds] adding a new PTS keyword (Re: Usefulness of periodic reproducible builds e-mails

2015-10-05 Thread Raphael Hertzog
On Sat, 03 Oct 2015, Mattia Rizzolo wrote:
> > What kind of mails are we referring to?
> 
> We are talking about very short mails, actually one-liners like
> 
> 2015-10-03 11:43 https://reproducible.debian.net/unstable/amd64/derby changed 
> from FTBFS -> unreproducible
> 
> (this one will be sent out this evening)

They should probably be expanded to be more explicit but I think
that being informed of such changes is interesting in the general case.

> > That said it depends on the mails... we really want only notifications
> > when something significant changes.
> 
> Well, we'd like a dedicate keywoard exactly because for a lot of people
> this is not significant.
> The current implementation of sending mails to $pkg@packages.d.o makes
> the mail use the "contact" keyword, and imho this is bad, usually people
> interested in contact only are not interested in this kind of info.

We can always override that decision at the PTS level, we get the mail via
$pkg@packages.d.o (and thus the default "contact" keyword) but it can be
reclassified afterwards.

But I don't agree that we need to add a new keyword. Almost nobody will
know of it and will make the effort to update their subscription, etc.

Either we make it good enough and with enough value so that it stands
as a mail of its own (and I think it's doable with little efforts) or
we should not forward it until we have a way to group multiple small
bits of information (and this where the "summary" keyword was supposed
to come into play).

> Yes, but I guess this require something "qa side", or is it enough to
> just start sending mails to package_reproduci...@packages.qa.debian.org
> (or package_reproduci...@tracker.debian.org, but that way old PTS user
> wouldn't get those mails) > ??

The answer is not the same for the old and the new but it doesn't matter
as the new PTS will be the one handling all the mails as soon as I finish
the work that I started a few weeks ago.

And there you definitely needs some coordination to make the keyword
exist.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] adding a new PTS keyword (Re: Usefulness of periodic reproducible builds e-mails

2015-10-03 Thread Raphael Hertzog
Hello,

> On Mittwoch, 30. September 2015, Mattia Rizzolo wrote:
> > > I think there is value in receiving these notifications, they provide
> > > timely feedback about the status of our packages.
> > > 
> > > Maybe we can setup a mailing list for this, something like
> > > pkg-java-bui...@lists.alioth.debian.org? (we already have
> > > pkg-java-commits, for example).
> > 
> > This wouldn't work with the current implementation, which is emailing
> > $p...@packages.debian.org.  Anyway, I received a suggestion of setting up
> > a new PTS keyword, so then people can go and subscribe there, maybe
> > using the team facility of the new tracker to subscribe to the whole lot
> > (i beliebe it works that way?).
> > 
> > Does anybody knows how to achive that?

What kind of mails are we referring to?

In general, it's OK to use the package tracker to relay important data
about the packages... but I don't think that a dedicated keyword helps
here. We have a "build" keyword already and I believe that reproducible
mails should be sent via that keyword as well.

That said it depends on the mails... we really want only notifications
when something significant changes.

About the implementation it can be done simply by mailing a specific
email address that encodes both the package and the keyword.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] adding a new PTS keyword (Re: Usefulness of periodic reproducible builds e-mails

2015-10-03 Thread Mattia Rizzolo
On Sat, Oct 03, 2015 at 09:13:19PM +0200, Raphael Hertzog wrote:
> Hello,
> 
> > On Mittwoch, 30. September 2015, Mattia Rizzolo wrote:
> > > > I think there is value in receiving these notifications, they provide
> > > > timely feedback about the status of our packages.
> > > > 
> > > > Maybe we can setup a mailing list for this, something like
> > > > pkg-java-bui...@lists.alioth.debian.org? (we already have
> > > > pkg-java-commits, for example).
> > > 
> > > This wouldn't work with the current implementation, which is emailing
> > > $p...@packages.debian.org.  Anyway, I received a suggestion of setting up
> > > a new PTS keyword, so then people can go and subscribe there, maybe
> > > using the team facility of the new tracker to subscribe to the whole lot
> > > (i beliebe it works that way?).
> > > 
> > > Does anybody knows how to achive that?
> 
> What kind of mails are we referring to?

We are talking about very short mails, actually one-liners like

2015-10-03 11:43 https://reproducible.debian.net/unstable/amd64/derby changed 
from FTBFS -> unreproducible

(this one will be sent out this evening)

> In general, it's OK to use the package tracker to relay important data
> about the packages... but I don't think that a dedicated keyword helps
> here. We have a "build" keyword already and I believe that reproducible
> mails should be sent via that keyword as well.
> 
> That said it depends on the mails... we really want only notifications
> when something significant changes.

Well, we'd like a dedicate keywoard exactly because for a lot of people
this is not significant.
The current implementation of sending mails to $pkg@packages.d.o makes
the mail use the "contact" keyword, and imho this is bad, usually people
interested in contact only are not interested in this kind of info.

> About the implementation it can be done simply by mailing a specific
> email address that encodes both the package and the keyword.

Yes, but I guess this require something "qa side", or is it enough to
just start sending mails to package_reproduci...@packages.qa.debian.org
(or package_reproduci...@tracker.debian.org, but that way old PTS user
wouldn't get those mails)
??

> -- 
> Raphaël Hertzog ◈ Debian Developer
> 
> Support Debian LTS: http://www.freexian.com/services/debian-lts.html
> Learn to master Debian: http://debian-handbook.info/get/
> 

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds