[yast-devel] Build Service Mails on Yast Devel
Hi, Maybe it's just me, but I don't like seeing e-mails from build-service on yast-devel as it's too many of them and I'm a bit lost in a high traffic. One e-mail once a day is OK, but 5 - 8 a day seems to be too much. I'm unable to follow other discussions because of that. What's your opinion? Bye Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tue, 21 Jan 2014 09:54:29 +0100 Lukas Ocilka <lukas.ocilka@suse.com> wrote:
Hi,
Maybe it's just me, but I don't like seeing e-mails from build-service on yast-devel as it's too many of them and I'm a bit lost in a high traffic. One e-mail once a day is OK, but 5 - 8 a day seems to be too much.
I'm unable to follow other discussions because of that. What's your opinion?
Bye Lukas
Well, it is intention ot have it on visible place as it is important information if submit request are declined. On other hand if it is accepted, then it is not so important information, but I cannot disable only one of it. OBS notifications also do not allow batching mails now. Maybe you can ask coolo, if he want to add it. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tue, 21 Jan 2014 09:58:36 +0100 Josef Reidinger <jreidinger@suse.cz> wrote:
On Tue, 21 Jan 2014 09:54:29 +0100 Lukas Ocilka <lukas.ocilka@suse.com> wrote:
Hi,
Maybe it's just me, but I don't like seeing e-mails from build-service on yast-devel as it's too many of them and I'm a bit lost in a high traffic. One e-mail once a day is OK, but 5 - 8 a day seems to be too much.
I'm unable to follow other discussions because of that. What's your opinion?
Bye Lukas
Well, it is intention ot have it on visible place as it is important information if submit request are declined. On other hand if it is accepted, then it is not so important information, but I cannot disable only one of it.
OBS notifications also do not allow batching mails now. Maybe you can ask coolo, if he want to add it.
Josef
And one trick. I have all mails from BS in separated directory where filter store it. It is easy filter X-Mailer Contains "OBS Notification System" I think that for such mails yast-commit is not proper mailing list as there is too big trafic for such important message like unaccepted package. Usually package is not accepted when it do not pass openQA, as other failures catch jenkins before submit. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 21.1.2014 10:03, Josef Reidinger napsal(a):
On Tue, 21 Jan 2014 09:58:36 +0100 Josef Reidinger <jreidinger@suse.cz> wrote:
On Tue, 21 Jan 2014 09:54:29 +0100 Lukas Ocilka <lukas.ocilka@suse.com> wrote: [...]
I'm unable to follow other discussions because of that. What's your opinion?
IMHO yast-devel should be used by people only (no mails generated by bots/scripts). I'd prefer yast-commit list for such mails.
And one trick. I have all mails from BS in separated directory where filter store it. It is easy filter X-Mailer Contains "OBS Notification System"
Good point.
I think that for such mails yast-commit is not proper mailing list as there is too big trafic for such important message like unaccepted package.
So do it the other way round: send the notifications to yast-commit and filter messages from "OBS Notification System" and put them to a separate folder so you can easily see them. You could even add a filter for "Request .* changed to declined" to just see the rejected submits... For me this seems to be a better solution than yast-devel. -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tue, Jan 21, 2014 at 02:39:59PM +0100, Ladislav Slezak wrote:
Dne 21.1.2014 10:03, Josef Reidinger napsal(a):
On Tue, 21 Jan 2014 09:58:36 +0100 Josef Reidinger <jreidinger@suse.cz> wrote:
On Tue, 21 Jan 2014 09:54:29 +0100 Lukas Ocilka <lukas.ocilka@suse.com> wrote: [...]
I'm unable to follow other discussions because of that. What's your opinion?
IMHO yast-devel should be used by people only (no mails generated by bots/scripts). I'd prefer yast-commit list for such mails.
I second that. This also applies to "webyast security scanner" and "forgotten pull requests" mails. Regards, Arvin -- Arvin Schnell, <aschnell@suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 21.1.2014 14:45, Arvin Schnell wrote:
IMHO yast-devel should be used by people only (no mails generated by bots/scripts). I'd prefer yast-commit list for such mails.
I second that. This also applies to "webyast security scanner" and "forgotten pull requests" mails.
The webyast security scanner can be actually fully disabled (in Jenkins). On the other hand, forgotten pull requests are very important for the team to cooperate better. Ideally, there should be no forgotten pull requests IMO and thus I like to see it here. 2c Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 21.1.2014 14:55, Lukas Ocilka napsal(a):
On 21.1.2014 14:45, Arvin Schnell wrote:
IMHO yast-devel should be used by people only (no mails generated by bots/scripts). I'd prefer yast-commit list for such mails.
I second that. This also applies to "webyast security scanner" and "forgotten pull requests" mails.
The webyast security scanner can be actually fully disabled (in Jenkins).
Yes, but I'd rather redirect it to yast-commit .
On the other hand, forgotten pull requests are very important for the team to cooperate better. Ideally, there should be no forgotten pull requests IMO and thus I like to see it here.
Yes, I agree, seeing forgotten PRs is very important. The question is whether it disturbs the other people (who are not interested in PR review at all) too much... Setting a filter for "Pending Pull Requests" subject is trivial, the question is who should set it. All developers interested in them (to not overlook something) or the other people not interested in them (to ignore them)? That's the question here... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 21.1.2014 16:09, Ladislav Slezak wrote:
On the other hand, forgotten pull requests are very important for the team to cooperate better. Ideally, there should be no forgotten pull requests IMO and thus I like to see it here.
Yes, I agree, seeing forgotten PRs is very important. The question is whether it disturbs the other people (who are not interested in PR review at all) too much...
Setting a filter for "Pending Pull Requests" subject is trivial, the question is who should set it. All developers interested in them (to not overlook something) or the other people not interested in them (to ignore them)?
Everyone in the team should participate in Code Review both asking for the review and also doing the actual review for others. Otherwise it will not work. Whether the rest of subscribers are interested? Well, at least some, as they don't belong to Yast team but their pull requests are reviewed by someone from the team. Of course, there will be some yast-devel subscribers who do not participate in code review at all, but they are still interested in the Yast development process or they sometimes ask for help, ideas or opinions. This is a development mailing-list, so I'd expect development to be discussed here. "Too high" traffic might be bad, but creating special mailing list for one purpose is even worse. We have to find the right balance for what needs to go where. A questionnaire might help us :) (added to my TODO) ;) Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 21.1.2014 09:58, Josef Reidinger napsal(a):
On Tue, 21 Jan 2014 09:54:29 +0100 Lukas Ocilka <lukas.ocilka@suse.com> wrote:
Maybe it's just me, but I don't like seeing e-mails from build-service on yast-devel as it's too many of them and I'm a bit lost in a high traffic. [...]
Well, it is intention ot have it on visible place as it is important information if submit request are declined.
It's important information for core YaST developers, but not so much for other subscribers, who maybe maintain few modules or just want to follow YaST development. -- David Majda SUSE developer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tue, 21 Jan 2014 10:26:52 +0100 David Majda <dmajda@suse.cz> wrote:
Dne 21.1.2014 09:58, Josef Reidinger napsal(a):
On Tue, 21 Jan 2014 09:54:29 +0100 Lukas Ocilka <lukas.ocilka@suse.com> wrote:
Maybe it's just me, but I don't like seeing e-mails from build-service on yast-devel as it's too many of them and I'm a bit lost in a high traffic. [...]
Well, it is intention ot have it on visible place as it is important information if submit request are declined.
It's important information for core YaST developers, but not so much for other subscribers, who maybe maintain few modules
Problem is that we submit all packages under yast-team user in jenkins, so even if you maintain one module, you would like to know, that your package is not accepted to factory.
or just want to follow YaST development.
Yes, in this case you only see if package is accepted or declined or if some comments done for submission ( I can turn off comments if you would like ). Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tue, 21 Jan 2014 09:54:29 +0100 Lukas Ocilka <lukas.ocilka@suse.com> wrote:
Hi,
Maybe it's just me, but I don't like seeing e-mails from build-service on yast-devel as it's too many of them and I'm a bit lost in a high traffic. One e-mail once a day is OK, but 5 - 8 a day seems to be too much.
I'm unable to follow other discussions because of that. What's your opinion?
Bye Lukas
Hi to summary discussion and try to reach conclude what I should change: - move OBS/IBS notifications ( so whole yast-team user ) to yast-commit and it is up to everybody to filter reasonable to see if his package is not accepted - pending pull request mail keep on yast-devel - brakeman for webyast disable on jenkins. I am right? If noone complain I will do proper action on monday at 12 CET Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Fri, 24 Jan 2014 15:47:41 +0100 Josef Reidinger <jreidinger@suse.cz> wrote:
On Tue, 21 Jan 2014 09:54:29 +0100 Lukas Ocilka <lukas.ocilka@suse.com> wrote:
Hi,
Maybe it's just me, but I don't like seeing e-mails from build-service on yast-devel as it's too many of them and I'm a bit lost in a high traffic. One e-mail once a day is OK, but 5 - 8 a day seems to be too much.
I'm unable to follow other discussions because of that. What's your opinion?
Bye Lukas
Hi to summary discussion and try to reach conclude what I should change:
- move OBS/IBS notifications ( so whole yast-team user ) to yast-commit and it is up to everybody to filter reasonable to see if his package is not accepted
- pending pull request mail keep on yast-devel
- brakeman for webyast disable on jenkins.
I am right?
If noone complain I will do proper action on monday at 12 CET
Josef
No one complained, so I changed it as described above. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 27.1.2014 16:16, Josef Reidinger wrote:
Hi to summary discussion and try to reach conclude what I should change:
- move OBS/IBS notifications ( so whole yast-team user ) to yast-commit and it is up to everybody to filter reasonable to see if his package is not accepted
- pending pull request mail keep on yast-devel
- brakeman for webyast disable on jenkins.
I am right?
If noone complain I will do proper action on monday at 12 CET
Josef
No one complained, so I changed it as described above.
LGTM :) Thanks Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (5)
-
Arvin Schnell -
David Majda -
Josef Reidinger -
Ladislav Slezak -
Lukas Ocilka