[21:22] Rosco2: I came to think about yet another possibility - creating a new team for Debian Multimedia, like ubuntustudio-bugs. Since they have a different set of packages to us [21:22] Rosco2: Possibly, we could just join that team instead [21:23] Rosco2: Also, lp has an API. Been a while since I tried using it. Might be possible to make subscriptions with a script, which would save a lot of time === zequence_ is now known as zequence [21:24] we could rename ubuntustudio-bugs debian-multimedia-bugs. If we want to do that [21:25] And then create a new team again called ubuntustudio-bugs. All though, if a script could take care of package subscriptions, it would not be a lot of work just creating a new team from scratch, and then do the subscriptions [21:25] Well, just thinking out loud [21:26] Hmmm. I had been thinking of asking if we could have a small number join the existing Debian Multimedia team on LP. [21:27] Rosco2: Does it subscribe to packages? [21:27] That was based on the fact that we could encourage people to join US-bugs, but they could only do basic triage [21:28] I thing the Deb-maint team are listed as the maintainer of the packages [21:29] I was going to ask them if they then have the power to set importance and extra stuff that only "Bug Control" can do. [21:30] Ah, right [21:31] I am listed as maintainer for one package, but I can't do much, so I am not sure [21:32] API would be useful for the meta packages we know we are interested in. [21:33] But then I just started looking at ubuntustudio-desktop, and it has lots of stuff we don't need to care about like gedit [21:34] But some stuff we probably do like alsa-utils [21:36] I will have a look, and see if it helps with photography etc. [21:40] Rosco2: DE stuff is not something we should care about at all [21:40] Rosco2: Only the multimedia metas [21:40] ..as we don't really have our own DE, though ours is slightly custom [21:41] Yeah - you are right. Skipping that one. [21:42] Our main concern is of course the multimedia packages we distribute, while I could see a point in keeping an eye out for a bigger scope. I would assume debian-multimedia maintains everything there, except for a few things, like pulseaudio [21:46] Pulseaudio already gest a lot of attention, so we don't really need to do much there, except for jack - pulseaudio integration. [21:47] I spotted a few packages that come up in audio discussions like pavucontrol & apps like audacious. [21:49] Maybe I will put it last in the pile incase they are not listed in the other multimedia metas [21:49] Funny you mention Pulesaudio. [21:49] I subscribed to that and there a hundreds of bugs. [21:50] Rosco2: I suppose any multimedia application in the desktop meta already gets attention. Not sure what would be best there. [21:50] pulseaudio is important of course, since it's a core component [21:51] As the PA - Jack bridge was part of the PA source I was forced to get bugs for the whole lot. [21:51] Yeah [21:51] Will try some of the filters to whittle it down [21:52] I think you can filter on importance or something like that. [21:53] Rosco2: Ah, I remember when trying out the PPA, that getting info on bugs is pretty easy. But, that doesn't help forwarding them, unless someone sets up a bot to forward stuff. [21:54] Also, we could set up a mail list for that team [21:55] We used to have a ubuntustudio-bugs at list.ubuntu for a little while, and I tried using that, but came to the conclusion at the time that it wasn't very practical and had that mail list deleted [21:56] API, not PPA :P [21:56] It's a bit too late in the evening for me [21:56] I'm turning in. Catch you later [21:57] Mailing list is probably good if the team builds up, and we want to help teach each other how to triage [21:57] Yeah - same here - busy day tomorrow