|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
|
|
GStreamer per component virtual usersHi all,
I'm looking for a way to watch single GStreamer components in GNOME Bugzilla. Right now it's not possible because Default Assignee for each component is set to gstreamer-bugs@... [1] I had a brief discussion with Andre about it. He told me there is a chance to add a virtual user for each component (e.g. gst-plugins-good@..., gst-plugins-bad@..., ...) so that who doesn't want to receive notifications for all components can just watch single virtual users. Could you set up everything to make it work? I'm not listed as a GStreamer developer in bugzilla but we discussed about it on IRC (I can get them to comment here if needed) and they all agree as long as: - gstreamer-bugs@... will still receive all bug mails for the gstreamer product - people who's watching gstreamer-bugs@... will still receive all mails Thanks! Filippo 1. http://bugzilla.gnome.org/describecomponents.cgi?product=gstreamer _______________________________________________ Gnome-bugsquad mailing list Gnome-bugsquad@... http://mail.gnome.org/mailman/listinfo/gnome-bugsquad |
|
|
Re: GStreamer per component virtual usersOn Fri, Jun 05, 2009 at 09:22:39PM +0200, Filippo Argiolas wrote:
> about it on IRC (I can get them to comment here if needed) and they > all agree as long as: > - gstreamer-bugs@... will still receive all bug > mails for the gstreamer product > - people who's watching gstreamer-bugs@... will > still receive all mails Impossible. If you watch someone, you watch that person. This doesn't include the everyone that person is also watching. Meaning: gstreamer-bugs@... watches gst-*@... userA watches gst-plugins-good@... userB watches gstreamer-bugs@... If a change is made by userC in plugins-good: userC gets an email userB won't get an email userA gets an email gstreamer-bugs@... gets an email Note: gets an email depends on the user settings. Might not want their own changes, etc. -- Regards, Olav _______________________________________________ Gnome-bugsquad mailing list Gnome-bugsquad@... http://mail.gnome.org/mailman/listinfo/gnome-bugsquad |
|
|
Re: GStreamer per component virtual usersOn Sat, Jun 6, 2009 at 1:24 PM, Olav Vitters<olav@...> wrote:
> On Fri, Jun 05, 2009 at 09:22:39PM +0200, Filippo Argiolas wrote: >> about it on IRC (I can get them to comment here if needed) and they >> all agree as long as: >> - gstreamer-bugs@... will still receive all bug >> mails for the gstreamer product >> - people who's watching gstreamer-bugs@... will >> still receive all mails > > Impossible. If you watch someone, you watch that person. This doesn't > include the everyone that person is also watching. Uhm, so there wouldn't be any way to watch all gstreamer products (let alone watching each single product)? Wouldn't gstreamer-bugs@... still be default QA contact for all products and, so users watching it wouldn't still receive all notifications? Filippo _______________________________________________ Gnome-bugsquad mailing list Gnome-bugsquad@... http://mail.gnome.org/mailman/listinfo/gnome-bugsquad |
|
|
Re: GStreamer per component virtual usersOn Sat, Jun 06, 2009 at 02:19:28PM +0200, Filippo Argiolas wrote:
> Uhm, so there wouldn't be any way to watch all gstreamer products (let > alone watching each single product)? Wouldn't > gstreamer-bugs@... still be default QA contact for > all products and, so users watching it wouldn't still receive all > notifications? You mean you want the default assignee and QA person to be different dummy addresses (mailing list and @gnome.bugs)? Then nobody can assign something to themselves anymore. -- Regards, Olav _______________________________________________ Gnome-bugsquad mailing list Gnome-bugsquad@... http://mail.gnome.org/mailman/listinfo/gnome-bugsquad |
|
|
Re: GStreamer per component virtual usersOn Sat, Jun 6, 2009 at 2:37 PM, Olav Vitters<olav@...> wrote:
> On Sat, Jun 06, 2009 at 02:19:28PM +0200, Filippo Argiolas wrote: >> Uhm, so there wouldn't be any way to watch all gstreamer products (let >> alone watching each single product)? Wouldn't >> gstreamer-bugs@... still be default QA contact for >> all products and, so users watching it wouldn't still receive all >> notifications? > > You mean you want the default assignee and QA person to be different > dummy addresses (mailing list and @gnome.bugs)? Then nobody can assign > something to themselves anymore. I'm not sure I'm following you, I've looked into bugzilla docs (both current and 2.x versions) and there is no place where it says Default Assignee and QA should be the same. How would it prevent anyone to reassign the bug to another user (themself or someone else)? Regards, Filippo _______________________________________________ Gnome-bugsquad mailing list Gnome-bugsquad@... http://mail.gnome.org/mailman/listinfo/gnome-bugsquad |
|
|
Re: GStreamer per component virtual usersAm Samstag, den 06.06.2009, 16:23 +0200 schrieb Filippo Argiolas:
> > You mean you want the default assignee and QA person to be different > > dummy addresses (mailing list and @gnome.bugs)? Then nobody can assign > > something to themselves anymore. > > I'm not sure I'm following you, I've looked into bugzilla docs (both > current and 2.x versions) and there is no place where it says Default > Assignee and QA should be the same. This has nothing to do with technical docs. This is about workflows that are (more or less) defined in a project. > How would it prevent anyone to > reassign the bug to another user (themself or someone else)? If you want to use both Assignee *and* QA address for watching those "users" you will lose watching when someone assigns a bug yo himselves (and hence removes the default assignee from the bug). andre -- mailto:ak-47@... | failed http://www.iomc.de/ | http://blogs.gnome.org/aklapper _______________________________________________ Gnome-bugsquad mailing list Gnome-bugsquad@... http://mail.gnome.org/mailman/listinfo/gnome-bugsquad |
|
|
Re: GStreamer per component virtual usersOn Sun, Jun 7, 2009 at 8:39 PM, Andre Klapper<ak-47@...> wrote:
> Am Samstag, den 06.06.2009, 16:23 +0200 schrieb Filippo Argiolas: >> How would it prevent anyone to >> reassign the bug to another user (themself or someone else)? > > If you want to use both Assignee *and* QA address for watching those > "users" you will lose watching when someone assigns a bug yo himselves > (and hence removes the default assignee from the bug). Well I could say that this would be the expected behavior: if someone assigns a bug to himself he's going to take care of it until it's resolved so there is no reason for the others to keep watching it and they can just CC themselves if still interested. Anyway, let me summarize the choices we have as I understood: 1. Create a virtual user for each component, set it as default assignee and leave the mailing list as default QA contact. This will allow to watch both single components (with virtual users) and the whole product at once (with the mailing list) but it will have that little downside discussed above. 2. Create a virtual user for each component, set it both as default assignee and QA contact. This will allow to watch single components but there won't be any way to watch the whole product. It wouldn't have though that downside. 3. Leave as it is now with no chance to follow single components. If you can confirm I'm not missing anything I'll contact the other gstreamer hackers to see how we want to proceed. Thanks, Filippo _______________________________________________ Gnome-bugsquad mailing list Gnome-bugsquad@... http://mail.gnome.org/mailman/listinfo/gnome-bugsquad |
|
|
Re: GStreamer per component virtual usersAm Sonntag, den 07.06.2009, 21:22 +0200 schrieb Filippo Argiolas:
> On Sun, Jun 7, 2009 at 8:39 PM, Andre Klapper<ak-47@...> wrote: > > If you want to use both Assignee *and* QA address for watching those > > "users" you will lose watching when someone assigns a bug yo himselves > > (and hence removes the default assignee from the bug). > > Well I could say that this would be the expected behavior: if someone > assigns a bug to himself he's going to take care of it until it's > resolved so there is no reason for the others to keep watching it and > they can just CC themselves if still interested. I disagree. I want to watch a bug from when I decided to subscribe until its end. I don't want to manually CC again just because someone starts working on it. Without this manual CC'ing I would never receive an email when it gets fixed. When we talked on IRC I didn't realize that you do not automatically watch users that are watched by users that you watch, but Olav is of course right and now that I think about it it makes sense - otherwise this would trigger huge amounts of mail (and loops). Gstreamer: So either everything remains as it is, or virtual users are created for each component and set as default QA contact, and every real person has to add all those virtual users to their watchlist if interested in watching the entire Gstreamer product. andre -- mailto:ak-47@... | failed http://www.iomc.de/ | http://blogs.gnome.org/aklapper _______________________________________________ Gnome-bugsquad mailing list Gnome-bugsquad@... http://mail.gnome.org/mailman/listinfo/gnome-bugsquad |
|
|
Re: GStreamer per component virtual usersOn Sun, Jun 7, 2009 at 9:58 PM, Andre Klapper<ak-47@...> wrote:
> Am Sonntag, den 07.06.2009, 21:22 +0200 schrieb Filippo Argiolas: >> On Sun, Jun 7, 2009 at 8:39 PM, Andre Klapper<ak-47@...> wrote: >> > If you want to use both Assignee *and* QA address for watching those >> > "users" you will lose watching when someone assigns a bug yo himselves >> > (and hence removes the default assignee from the bug). >> >> Well I could say that this would be the expected behavior: if someone >> assigns a bug to himself he's going to take care of it until it's >> resolved so there is no reason for the others to keep watching it and >> they can just CC themselves if still interested. Hey, I'm back, I had a bunch of exams (and still have some next week :-() and completely forgot about this thing :-P > I disagree. > I want to watch a bug from when I decided to subscribe until its end. I > don't want to manually CC again just because someone starts working on > it. Without this manual CC'ing I would never receive an email when it > gets fixed. Ok, I'm sorry then, I didn't have a clear idea about our bugzilla setup and how bugzilla actually worked. Anyway I'd still say that if I'm watching a whole product and someone assigns a bug to himself I would be fine to not receive any more mail from that bug since someone else is caring about it. It's not like you decided to watch a bug and you get unsubscribed, there's CC for that, we're talking about watching a whole product and not getting notifications for assigned bugs. > Gstreamer: So either everything remains as it is, or virtual users are > created for each component and set as default QA contact, and every real > person has to add all those virtual users to their watchlist if > interested in watching the entire Gstreamer product. I finally managed to come up with some good filtering with gmail, I don't have disk space requirements and I can easily ignore bugs I don't care labelling them by product name. So I'm fine to leave everything as it is now, if any other gstreamer hacker will feel the need for this change I guess we'll bring this up again. Thanks for making everything more clear and sorry for the noise! Ciao, Filippo _______________________________________________ Gnome-bugsquad mailing list Gnome-bugsquad@... http://mail.gnome.org/mailman/listinfo/gnome-bugsquad |
| Free embeddable forum powered by Nabble | Forum Help |