Re: What to do for new packages
Hi Reinhard, |--== On Mon, 22 Dec 2008 18:56:30 +0100, Reinhard Tartler siret...@tauware.de said: RT sorry for the late and terse response, I hope that I'll have more time RT after christmas to actually implement some of these decisions... Don't worry, I think there's absolutely no pressure with this, as we agreed that the migration should be done on best effort basis. RT Free Ekanayaka fr...@debian.org writes: RT I'd suggest this: RT * maintainer is set to RT pkg-multimedia-maintain...@lists.alioth.debian.org How should the team's name look like? The full maintainer field currently looks like: Debian multimedia packages maintainers pkg-multimedia-maintain...@lists.alioth.debian.org which is a bit long. What about trimming it to Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org RT Good point, yes, let's use that Ok, so if there are no objections I will start setting the Maintainer to: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org in my next uploads. RT merry christmas ! Merry Christmas to all the team! Ciao, Free -- To UNSUBSCRIBE, email to debian-multimedia-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What to do for new packages
Hi Felipe, |--== On Thu, 18 Dec 2008 15:37:22 -0300, Felipe Sateler fsate...@gmail.com said: FS El 18/12/08 14:24 Free Ekanayaka escribió: |--== On Thu, 18 Dec 2008 13:55:20 -0300, Felipe Sateler FS fsate...@gmail.com said: * commit messages are copied to both pkg-multimedia-commits@ and the PTS for the relevant package. The former results then in a very busy mailing list but if one is interested only in a specifc package he can just subscribe to the PTS. FS I just setup this, and I have a problem: the list is members only. I'm not FS sure how to deal with this, since I don't think most people will want to FS suscribe to the commits list. Specially sporadic contributors. We should FS either whitelist mail sent from alioth (is this possible?), allow non-members FS posts, or don't send mail there at all. If possible I would go for whitelist-ing mail sent from alioth, mailman should support it, check Privacy Options - Sender filters in the list's administrative interface. FS I worked around this by making the script send the mail from the FS users.alioth.debian.org address of the pusher instead of the committer's FS address. FS So, when creating the repository, use the setup-repository script that will FS take care of this. Nice job. FS BTW, Free, I added you to the project. Welcome :) Thanks! :) Free -- To UNSUBSCRIBE, email to debian-multimedia-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What to do for new packages
sorry for the late and terse response, I hope that I'll have more time after christmas to actually implement some of these decisions... Free Ekanayaka fr...@debian.org writes: RT I'd suggest this: RT * maintainer is set to RTpkg-multimedia-maintain...@lists.alioth.debian.org How should the team's name look like? The full maintainer field currently looks like: Debian multimedia packages maintainers pkg-multimedia-maintain...@lists.alioth.debian.org which is a bit long. What about trimming it to Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Good point, yes, let's use that RT * pkg-multimedia gets an git repository (Felipe, please request RTone and start moving the packages. btw, is it possible to RTredirect the old locations to the new ones? - I don't think so, RTbut you never know) This probably goes without saying, but I would include the tags: Vcs-Git: git://git.debian.org/git/pkg-multimedia/PACKAGE.git Vcs-Browser: http://git.debian.org/?p=pkg-multimedia/PACKAGE.git in all debian/control files. yes, sounds reasonable. RT These points should be seen as proposed clarification to RT http://wiki.debian.org/DebianMultimedia/Merge RT The selling argument was (I think) that debian-multimedia.org RT already exists and is well known, but has no relationship to RT demudi, which in fact even predates debian-multimedia. Yeah, sad to have to say goodbye to Debian Multimedia (the Debian one), I feel that name was quite easy and catchy. Anyway the important thing to me is to get a well maintained package set. Indeed. merry christmas! -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to debian-multimedia-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What to do for new packages
Hi Felipe, |--== On Wed, 17 Dec 2008 16:39:28 -0300, Felipe Sateler fsate...@gmail.com said: FS El 17/12/08 16:29 Reinhard Tartler escribió: * pkg-multimedia gets an git repository (Felipe, please request one and start moving the packages. btw, is it possible to redirect the old locations to the new ones? - I don't think so, but you never know) FS I requested a git repository. It got created already :) I've requested to be added to the pkg-multimedia project, I'll start moving a few git repositories as soon as I get into the group. Ciao! Free -- To UNSUBSCRIBE, email to debian-multimedia-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What to do for new packages
El 17/12/08 16:29 Reinhard Tartler escribió: Felipe Sateler fsate...@gmail.com writes: El 26/11/08 12:27 Felipe Sateler escribió: OK, so I'm about to co-maintain liblo, which is an OSC library, and can be considered a multimedia package (csound, rosegarden and ardour are some big packages using it). So... I want to bring it under the scope of the teams-to-become-one. I have imported the sources into a git repository. demudi already has a git area enabled in alioth, pkg-multimedia doesn't. Should I use the demudi area? What list should I put in the Maintainer field? Given that pkg-multimedia is more active maybe we should it? So what's the conclusion on this? Since pkg-multimedia doesn't have a git repository I just pushed my changes to the demudi git area. I'm still not clear on which mailing list to use yet. The poll didn't have much participation, and ended up in a 3:2 win for pkg-multimedia. Yeah, good idea. Feel free to correct me, but if nobody objects about this very small win, I'd suggest this: * maintainer is set to pkg-multimedia-maintain...@lists.alioth.debian.org * discussion happens on that list as well * pkg-multimedia gets an git repository (Felipe, please request one and start moving the packages. btw, is it possible to redirect the old locations to the new ones? - I don't think so, but you never know) * packages formerly in svn are being migrated on a best efford basis without a fixed deadline. * commit messages are copied to both pkg-multimedia-commits@ and the PTS for the relevant package. The former results then in a very busy mailing list but if one is interested only in a specifc package he can just subscribe to the PTS. I just setup this, and I have a problem: the list is members only. I'm not sure how to deal with this, since I don't think most people will want to suscribe to the commits list. Specially sporadic contributors. We should either whitelist mail sent from alioth (is this possible?), allow non-members posts, or don't send mail there at all. These points should be seen as proposed clarification to http://wiki.debian.org/DebianMultimedia/Merge I put these and Free's suggestions into that page. I also copied the setup-script from collab-maint and modified it a bit for our purposes. PS: I think we can stop CCing each other, it's pretty clear we all read the lists. Saludos, Felipe Sateler signature.asc Description: This is a digitally signed message part.
Re: What to do for new packages
|--== On Thu, 18 Dec 2008 13:55:20 -0300, Felipe Sateler fsate...@gmail.com said: * commit messages are copied to both pkg-multimedia-commits@ and the PTS for the relevant package. The former results then in a very busy mailing list but if one is interested only in a specifc package he can just subscribe to the PTS. FS I just setup this, and I have a problem: the list is members only. I'm not FS sure how to deal with this, since I don't think most people will want to FS suscribe to the commits list. Specially sporadic contributors. We should FS either whitelist mail sent from alioth (is this possible?), allow non-members FS posts, or don't send mail there at all. If possible I would go for whitelist-ing mail sent from alioth, mailman should support it, check Privacy Options - Sender filters in the list's administrative interface. These points should be seen as proposed clarification to http://wiki.debian.org/DebianMultimedia/Merge FS I put these and Free's suggestions into that page. I also copied the FS setup-script from collab-maint and modified it a bit for our purposes. Thanks. Ciao! Free -- To UNSUBSCRIBE, email to debian-multimedia-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What to do for new packages
El 18/12/08 14:24 Free Ekanayaka escribió: |--== On Thu, 18 Dec 2008 13:55:20 -0300, Felipe Sateler fsate...@gmail.com said: * commit messages are copied to both pkg-multimedia-commits@ and the PTS for the relevant package. The former results then in a very busy mailing list but if one is interested only in a specifc package he can just subscribe to the PTS. FS I just setup this, and I have a problem: the list is members only. I'm not FS sure how to deal with this, since I don't think most people will want to FS suscribe to the commits list. Specially sporadic contributors. We should FS either whitelist mail sent from alioth (is this possible?), allow non-members FS posts, or don't send mail there at all. If possible I would go for whitelist-ing mail sent from alioth, mailman should support it, check Privacy Options - Sender filters in the list's administrative interface. I worked around this by making the script send the mail from the users.alioth.debian.org address of the pusher instead of the committer's address. So, when creating the repository, use the setup-repository script that will take care of this. BTW, Free, I added you to the project. Welcome :) Saludos, Felipe Sateler signature.asc Description: This is a digitally signed message part.
Re: What to do for new packages (was: Multimedia Teams in Debian)
El 26/11/08 12:27 Felipe Sateler escribió: OK, so I'm about to co-maintain liblo, which is an OSC library, and can be considered a multimedia package (csound, rosegarden and ardour are some big packages using it). So... I want to bring it under the scope of the teams-to-become-one. I have imported the sources into a git repository. demudi already has a git area enabled in alioth, pkg-multimedia doesn't. Should I use the demudi area? What list should I put in the Maintainer field? Given that pkg-multimedia is more active maybe we should it? So what's the conclusion on this? Since pkg-multimedia doesn't have a git repository I just pushed my changes to the demudi git area. I'm still not clear on which mailing list to use yet. The poll didn't have much participation, and ended up in a 3:2 win for pkg-multimedia. While I don't really care which list to use, we should use the resources of only one project, I guess (ie, if we are going to use pkg-multimedia we should create a git area for it). I can ask for the git area to be created if you want. Saludos, Felipe Sateler signature.asc Description: This is a digitally signed message part.
Re: What to do for new packages
El 17/12/08 16:29 Reinhard Tartler escribió: * pkg-multimedia gets an git repository (Felipe, please request one and start moving the packages. btw, is it possible to redirect the old locations to the new ones? - I don't think so, but you never know) I requested a git repository. I don't know what you mean by redirecting the old locations to the new ones, could you explain please? Saludos, Felipe Sateler signature.asc Description: This is a digitally signed message part.
Re: What to do for new packages
Felipe Sateler fsate...@gmail.com writes: El 26/11/08 12:27 Felipe Sateler escribió: OK, so I'm about to co-maintain liblo, which is an OSC library, and can be considered a multimedia package (csound, rosegarden and ardour are some big packages using it). So... I want to bring it under the scope of the teams-to-become-one. I have imported the sources into a git repository. demudi already has a git area enabled in alioth, pkg-multimedia doesn't. Should I use the demudi area? What list should I put in the Maintainer field? Given that pkg-multimedia is more active maybe we should it? So what's the conclusion on this? Since pkg-multimedia doesn't have a git repository I just pushed my changes to the demudi git area. I'm still not clear on which mailing list to use yet. The poll didn't have much participation, and ended up in a 3:2 win for pkg-multimedia. Yeah, good idea. Feel free to correct me, but if nobody objects about this very small win, I'd suggest this: * maintainer is set to pkg-multimedia-maintain...@lists.alioth.debian.org * discussion happens on that list as well * pkg-multimedia gets an git repository (Felipe, please request one and start moving the packages. btw, is it possible to redirect the old locations to the new ones? - I don't think so, but you never know) * packages formerly in svn are being migrated on a best efford basis without a fixed deadline. * commit messages are copied to both pkg-multimedia-commits@ and the PTS for the relevant package. The former results then in a very busy mailing list but if one is interested only in a specifc package he can just subscribe to the PTS. These points should be seen as proposed clarification to http://wiki.debian.org/DebianMultimedia/Merge The selling argument was (I think) that debian-multimedia.org already exists and is well known, but has no relationship to demudi, which in fact even predates debian-multimedia. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to debian-multimedia-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What to do for new packages
Hi Reinhard, |--== On Wed, 17 Dec 2008 20:29:52 +0100, Reinhard Tartler siret...@tauware.de said: RT Felipe Sateler fsate...@gmail.com writes: El 26/11/08 12:27 Felipe Sateler escribió: OK, so I'm about to co-maintain liblo, which is an OSC library, and can be considered a multimedia package (csound, rosegarden and ardour are some big packages using it). So... I want to bring it under the scope of the teams-to-become-one. I have imported the sources into a git repository. demudi already has a git area enabled in alioth, pkg-multimedia doesn't. Should I use the demudi area? What list should I put in the Maintainer field? Given that pkg-multimedia is more active maybe we should it? So what's the conclusion on this? Since pkg-multimedia doesn't have a git repository I just pushed my changes to the demudi git area. I'm still not clear on which mailing list to use yet. The poll didn't have much participation, and ended up in a 3:2 win for pkg-multimedia. RT Yeah, good idea. Feel free to correct me, but if nobody objects about RT this very small win, Fine for me. RT I'd suggest this: RT * maintainer is set to RTpkg-multimedia-maintain...@lists.alioth.debian.org How should the team's name look like? The full maintainer field currently looks like: Debian multimedia packages maintainers pkg-multimedia-maintain...@lists.alioth.debian.org which is a bit long. What about trimming it to Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org similarly to other projects like pkg-gnome: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org ? RT * discussion happens on that list as well Ok. RT * pkg-multimedia gets an git repository (Felipe, please request one and RTstart moving the packages. btw, is it possible to redirect the old RTlocations to the new ones? - I don't think so, but you never know) This probably goes without saying, but I would include the tags: Vcs-Git: git://git.debian.org/git/pkg-multimedia/PACKAGE.git Vcs-Browser: http://git.debian.org/?p=pkg-multimedia/PACKAGE.git in all debian/control files. RT * packages formerly in svn are being migrated on a best efford basis RTwithout a fixed deadline. Agreed. RT * commit messages are copied to both pkg-multimedia-commits@ and the RTPTS for the relevant package. The former results then in a very busy RTmailing list but if one is interested only in a specifc package he RTcan just subscribe to the PTS. Good idea. RT These points should be seen as proposed clarification to RT http://wiki.debian.org/DebianMultimedia/Merge RT The selling argument was (I think) that debian-multimedia.org already RT exists and is well known, but has no relationship to demudi, which in RT fact even predates debian-multimedia. Yeah, sad to have to say goodbye to Debian Multimedia (the Debian one), I feel that name was quite easy and catchy. Anyway the important thing to me is to get a well maintained package set. Ciao! Free -- To UNSUBSCRIBE, email to debian-multimedia-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What to do for new packages
Free Ekanayaka [EMAIL PROTECTED] writes: FS OK, I've started a page: http://wiki.debian.org/DebianMultimedia/Merge. Please FS add, edit, remove whatever you think necessary. I just filled a stub based on FS what I think we have agreed. Excellent. Apparently pkg-multimedia does not have a wiki page yet, we might want to use the DebianMultimedia one as base to move forward. Yes, I agree that using existing wiki pages minimizes confusion. demudi already has a git area enabled in alioth, pkg-multimedia doesn't. Should I use the demudi area? What list should I put in the Maintainer field? Given that pkg-multimedia is more active maybe we should it? I really don't mind using pkg-multimedia-maintainers, since it is more active. I've setup a doodle poll, please vote here: http://doodle.com/v6df6bx2akdft73f FS Great! I placed my vote. I agree with Fabian that debian-multimedia may be FS associated with Marillat's repository, and we should avoid that. That is true, even though I would point out that as far as I remember Marillat's repository used to be called simply marillat, and only later the name has been changed to debian-multimedia (about 1.5/2 years ago I think). The debian-multimedia mailing Debian list and associated team is there since more than 5 years now. Marillat and the other maintainers at debian-multimedia.org could have asked our opinion before using that name. However in these 2 years, that repository has gained a lot of publicity and fame, and we cannot ignore that. For that reason I suggest that we use a distinguishable name, even if we or you have used/invented that name before Christian Marillat. Ideally we can invite Christian to collaborate or even join the debian effords! I have already invited him to have a look at the ffmpeg package, and am still waiting for response from him. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: What to do for new packages
Hi Reinhard, |--== On Mon, 01 Dec 2008 09:26:33 +0100, Reinhard Tartler [EMAIL PROTECTED] said: RT Free Ekanayaka [EMAIL PROTECTED] writes: FS OK, I've started a page: http://wiki.debian.org/DebianMultimedia/Merge. Please FS add, edit, remove whatever you think necessary. I just filled a stub based on FS what I think we have agreed. Excellent. Apparently pkg-multimedia does not have a wiki page yet, we might want to use the DebianMultimedia one as base to move forward. RT Yes, I agree that using existing wiki pages minimizes confusion. Exactly, at a later point we might want to rename the wiki page according to the team name we choose. FS Great! I placed my vote. I agree with Fabian that debian-multimedia may be FS associated with Marillat's repository, and we should avoid that. That is true, even though I would point out that as far as I remember Marillat's repository used to be called simply marillat, and only later the name has been changed to debian-multimedia (about 1.5/2 years ago I think). The debian-multimedia mailing Debian list and associated team is there since more than 5 years now. Marillat and the other maintainers at debian-multimedia.org could have asked our opinion before using that name. RT However in these 2 years, that repository has gained a lot of publicity RT and fame, and we cannot ignore that. For that reason I suggest that we RT use a distinguishable name, even if we or you have used/invented RT that name before Christian Marillat. RT Ideally we can invite Christian to collaborate or even join the debian RT effords! I have already invited him to have a look at the ffmpeg RT package, and am still waiting for response from him. That is a very good idea. I think Marillat's repository was born to host packages which were not legally distributable by Debian, but it guess it know hosts also packages which could be included in Debian, maybe with a few modifications. It would really make sense to have a common repository for maintaining these packages, in order to share patches and minimize duplicated work. Is anybody in touch with Christian? Ciao! Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: What to do for new packages
Free Ekanayaka [EMAIL PROTECTED] writes: FS What list should I put in the Maintainer field? I'd suggest PROJECT@lists.debian.org please note that we have more control over mailman controlled lists than over debian listadmin maintained lists. That's why I'd prefer the lists.alioth.debian.org lists. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: What to do for new packages
El 27/11/08 18:01 Reinhard Tartler escribió: Felipe Sateler [EMAIL PROTECTED] writes: OK, so I'm about to co-maintain liblo, which is an OSC library, and can be considered a multimedia package (csound, rosegarden and ardour are some big packages using it). ok. cool! So... I want to bring it under the scope of the teams-to-become-one. I have imported the sources into a git repository. IIRC we agreed on tracking upstream releases in an upstream branch, maintain debian packaging in a branch derived from the upstream branch but keep patches to the upstream source in quilt. Is that correct? We should really document that somewhere. Probably on wiki.debian.org would be a good place. OK, I've started a page: http://wiki.debian.org/DebianMultimedia/Merge. Please add, edit, remove whatever you think necessary. I just filled a stub based on what I think we have agreed. demudi already has a git area enabled in alioth, pkg-multimedia doesn't. Should I use the demudi area? What list should I put in the Maintainer field? Given that pkg-multimedia is more active maybe we should it? I really don't mind using pkg-multimedia-maintainers, since it is more active. I've setup a doodle poll, please vote here: http://doodle.com/v6df6bx2akdft73f Great! I placed my vote. I agree with Fabian that debian-multimedia may be associated with Marillat's repository, and we should avoid that. Free's point about using the same project for lists and everything is also important. Using different alioth projects would be confusing, I think. BTW, I have applied for joining the pkg-multimedia project, in case we end up using any resources there. I noticed you have already been added! welcome! Cool. Saludos, Felipe Sateler signature.asc Description: This is a digitally signed message part.
Re: What to do for new packages
Felipe Sateler [EMAIL PROTECTED] writes: OK, so I'm about to co-maintain liblo, which is an OSC library, and can be considered a multimedia package (csound, rosegarden and ardour are some big packages using it). ok. cool! So... I want to bring it under the scope of the teams-to-become-one. I have imported the sources into a git repository. IIRC we agreed on tracking upstream releases in an upstream branch, maintain debian packaging in a branch derived from the upstream branch but keep patches to the upstream source in quilt. Is that correct? We should really document that somewhere. Probably on wiki.debian.org would be a good place. demudi already has a git area enabled in alioth, pkg-multimedia doesn't. Should I use the demudi area? What list should I put in the Maintainer field? Given that pkg-multimedia is more active maybe we should it? I really don't mind using pkg-multimedia-maintainers, since it is more active. I've setup a doodle poll, please vote here: http://doodle.com/v6df6bx2akdft73f BTW, I have applied for joining the pkg-multimedia project, in case we end up using any resources there. I noticed you have already been added! welcome! -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
