Re: New python maintenance team
Raphael Hertzog wrote: But I would really like turbogears maintained within python-modules since it's mainly good glue between several general-purpose Python modules. (But it's up to you in the end.) Let's merge the projects. There is only 3 of us and I think it would be best to be part of a large project. -- Bob Tanner [EMAIL PROTECTED] | Phone : (952)943-8700 http://www.real-time.com, Minnesota, Linux | Fax : (952)943-8500 Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
On Wed, 12 Apr 2006, Bob Tanner wrote: But I would really like turbogears maintained within python-modules since it's mainly good glue between several general-purpose Python modules. (But it's up to you in the end.) Let's merge the projects. There is only 3 of us and I think it would be best to be part of a large project. Indeed. I added the 3 members of pkg-turbogears in the python-modules alioth project. Let's go for it! (Please request the removal of pkg-turbogears on alioth once you don't need it any more) Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
Raphael Hertzog wrote: (Please request the removal of pkg-turbogears on alioth once you don't need it any more) Waiting on confirmation and then I'll submit the remove request. -- Bob Tanner [EMAIL PROTECTED] | Phone : (952)943-8700 http://www.real-time.com, Minnesota, Linux | Fax : (952)943-8500 Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
On 4/12/06, Bob Tanner [EMAIL PROTECTED] wrote: Raphael Hertzog wrote: (Please request the removal of pkg-turbogears on alioth once you don't need it any more) Waiting on confirmation and then I'll submit the remove request. Please, move cherrypy from pkg-turbogears svn repository first. :-) Thanks, -- stratus
Re: New python maintenance team
On Tue, 11 Apr 2006, Bob Tanner wrote: OK, thanks to everyone who volunteered so far. There's already a pkg-python Alioth project and an associated SVN repository. Right now it's empty but Matthias will start using it this week-end (if all goes well). This is just for core python right? Yeah, pkg-python would be just core python. But python-modules is more general purpose. Just want to make sure I understand the thread, python package projects, like pkg-turbogears are to remain separate? But I would really like turbogears maintained within python-modules since it's mainly good glue between several general-purpose Python modules. (But it's up to you in the end.) Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
Raphael Hertzog ([EMAIL PROTECTED]): Yeah, pkg-python would be just core python. But python-modules is more general purpose. Just want to make sure I understand the thread, python package projects, like pkg-turbogears are to remain separate? But I would really like turbogears maintained within python-modules since it's mainly good glue between several general-purpose Python modules. Does gaupol [1] qualify? It is rather standalone application than a python module but I would be glad to join the group. [1] http://home.gna.org/gaupol/ http://debian.pox.one.pl/gaupol_0.4.0-1_all.deb -- -=[ Piotr Ozarowski ]=- -=[ http://www.ozarowski.pl ]=- pgpfpxZZr67yQ.pgp Description: PGP signature
Re: New python maintenance team
On 4/11/06, Piotr Ozarowski [EMAIL PROTECTED] wrote: Raphael Hertzog ([EMAIL PROTECTED]): Yeah, pkg-python would be just core python. But python-modules is more general purpose. Just want to make sure I understand the thread, python package projects, like pkg-turbogears are to remain separate? But I would really like turbogears maintained within python-modules since it's mainly good glue between several general-purpose Python modules. Does gaupol [1] qualify? It is rather standalone application than a python module but I would be glad to join the group. Hi Piotr, The simple rule is that if i can import gaupol and it will be really useful for any other python application (packaged or not), it could be into the team. I think that gaupol itself don't qualify, but what's the status of pyenchant ? It's a gaupol dependency, right ? Sounds like a python-modules valid candidate. Thanks, -- stratus
Re: New python maintenance team
Gustavo Franco ([EMAIL PROTECTED]): the status of pyenchant ? It's a gaupol dependency, right ? Sounds like a python-modules valid candidate. There is an ITP bug reported against this package (package itself is available at mentors.debian.net), but it is little old - there are 2 new upstream versions. I'll ask author if he still wants to maintain it. -- -=[ Piotr Ozarowski ]=- -=[ http://www.ozarowski.pl ]=- pgpA1XEImfCJn.pgp Description: PGP signature
Re: New python maintenance team
On Thu, Apr 06, 2006 at 07:11:31PM +0200, Matthias Klose wrote: Raphael Hertzog writes: On Thu, 06 Apr 2006, Sebastian Rittau wrote: Am Donnerstag, den 06.04.2006, 09:58 +0200 schrieb Raphael Hertzog: I'm not experienced enough with Python to lead such a maintenance team, but I'm looking forward to such a team. Even though you may think you are not experienced enough, it seems you just stepped forward and volunteered to lead this team. ;) I think initiative is more important than knowing the ins and outs of Python. I do hope Matthias could lead such a team. He responded to my mail this morning. He didn't take a clear position about the team but he indicated that he would come with a proposal this week-end (and that he would also upload python2.5 in experimental). He would like to tie this transition with the new infrastructure for handling python modules. [just realized that my mail did go to Raphael only, not intended] Raphael, thanks for your interest. It's true that I did not respond to emails ignoring our discussions from January and February on this very list. It would be nice to build on these discussions for the transition. Any news from your side? I think I did make it clear, that we should get away from the transition system for all kind of packages and implemented that (but side-tracked by other work in the last month). Please expect an update from this at this weekend. I think everyone is agreed that we want greater automization of python transitions, but the longer this is postponed, the more problematic this becomes for etch. It's my impression that there is enough untapped manpower available to work on starting this transition the old, hard way that it's not to our advantage to continue postponing it due to the promise of better methods -- when those methods will still require sourceful uploads for the first round of implementation anyway. I think it's now been about a month since I suggested that we should focus on implementing the python infrastructure in a piece-wise manner in order to get this transition moving along; and still there's been no visible progress in that time, which makes that another month we could've used to start on this the hard way. :/ It would certainly be easier to do the transition using the new infrastructure, but that still blocks on having that infrastructure in place. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: New python maintenance team
Le vendredi 07 avril 2006 à 03:35 -0700, Steve Langasek a écrit : I think everyone is agreed that we want greater automization of python transitions, but the longer this is postponed, the more problematic this becomes for etch. I can only agree. The move to python 2.4 is an urgent matter, as too many things are depending on it now. If some new framework is developed, it will take several months before it is used in enough packages to be useful, and several more months is too much. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
Re: New python maintenance team
I fully agree with Joss. Can we have an Alioth group created? And a TODO list, possibly, so that as we are already more than just two guys we can start working on something :) ~marco Il giorno ven, 07/04/2006 alle 14.11 +0200, Josselin Mouette ha scritto: Le vendredi 07 avril 2006 à 03:35 -0700, Steve Langasek a écrit : I think everyone is agreed that we want greater automization of python transitions, but the longer this is postponed, the more problematic this becomes for etch. I can only agree. The move to python 2.4 is an urgent matter, as too many things are depending on it now. If some new framework is developed, it will take several months before it is used in enough packages to be useful, and several more months is too much. signature.asc Description: Questa è una parte del messaggio firmata digitalmente
Re: New python maintenance team
On Fri, 07 Apr 2006, Marco Cabizza wrote: Can we have an Alioth group created? And a TODO list, possibly, so that as we are already more than just two guys we can start working on something :) There's already a python-modules Alioth project and during the BSP next week, it may be a good time to suggest those maintainers to join the team and integrate their packages. I'll try to finish the documentation and make an announce this WE if possible. For the maintenance of the core python packages, Matthias is the Maintainer and even if there's a pkg-python Alioth project, he hasn't yet started to use it. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
On Thu, 06 Apr 2006, Raphael Hertzog wrote: Hello everybody, I'm not experienced enough with Python to lead such a maintenance team, but I'm looking forward to such a team. Who would be interested to help ? OK, thanks to everyone who volunteered so far. There's already a pkg-python Alioth project and an associated SVN repository. Right now it's empty but Matthias will start using it this week-end (if all goes well). http://alioth.debian.org/projects/pkg-python/ http://svn.debian.org/wsvn/pkg-python/ Given that 5-6 persons volunteered, Matthias probably won't give write access to everybody directly. So the right course of action is to make use of the Package Tracking System to subscribe to the various python source packages: http://packages.qa.debian.org/p/python-defaults.html http://packages.qa.debian.org/p/python2.4.html http://packages.qa.debian.org/p/python2.3.html And start helping out by submitting patches to the BTS, by forwarding bugs upstream, doing bug triaging and so on. After some time I'm confident that Matthias will add you to the Alioth project. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
Steve Langasek [EMAIL PROTECTED] writes: I think everyone is agreed that we want greater automization of python transitions, but the longer this is postponed, the more problematic this becomes for etch. It's my impression that there is enough untapped manpower available to work on starting this transition the old, hard way that it's not to our advantage to continue postponing it due to the promise of better methods -- when those methods will still require sourceful uploads for the first round of implementation anyway. FWIW, seconded. Please just upload python2.4 as the default python version. We have enough time get the infrastructure in place and attempt the automated transition for python2.5. Ganesan -- Ganesan Rajagopal (rganesan at debian.org) | GPG Key: 1024D/5D8C12EA Web: http://employees.org/~rganesan| http://rganesan.blogspot.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New python maintenance team
Hello everybody, given that Matthias doesn't respond to our mails concerning the maintenance of python and the switch to python2.4 by default, it should be time to initiate the movement (with or without him). The first python2.5 alpha release is out, and maybe the new team could start with that: packaging python2.5 in experimental along with preparing the switch to python2.4. I'm not experienced enough with Python to lead such a maintenance team, but I'm looking forward to such a team. Who would be interested to help ? I can at least create an alioth project if nobody steps up as a leader for that ... Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
2006/4/6, Raphael Hertzog [EMAIL PROTECTED]: Who would be interested to help ? I am very interested. (Alioth sanxiyn-guest) Seo Sanghyeon
Re: New python maintenance team
Who would be interested to help ?Despite I'm not an uploader, I could be of some help in python business. I'm already packaging some app's for ubuntu.Keep in touch for further info.Cumps
Re: New python maintenance team
I'm in - marco-guest on alioth. ~marco Il giorno gio, 06/04/2006 alle 09.58 +0200, Raphael Hertzog ha scritto: Hello everybody, given that Matthias doesn't respond to our mails concerning the maintenance of python and the switch to python2.4 by default, it should be time to initiate the movement (with or without him). The first python2.5 alpha release is out, and maybe the new team could start with that: packaging python2.5 in experimental along with preparing the switch to python2.4. I'm not experienced enough with Python to lead such a maintenance team, but I'm looking forward to such a team. Who would be interested to help ? I can at least create an alioth project if nobody steps up as a leader for that ... Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ signature.asc Description: Questa è una parte del messaggio firmata digitalmente
Re: New python maintenance team
Am Donnerstag, den 06.04.2006, 09:58 +0200 schrieb Raphael Hertzog: I'm not experienced enough with Python to lead such a maintenance team, but I'm looking forward to such a team. Even though you may think you are not experienced enough, it seems you just stepped forward and volunteered to lead this team. ;) I think initiative is more important than knowing the ins and outs of Python. Who would be interested to help ? I would like to help. - Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
On Thu, 06 Apr 2006, Sebastian Rittau wrote: Am Donnerstag, den 06.04.2006, 09:58 +0200 schrieb Raphael Hertzog: I'm not experienced enough with Python to lead such a maintenance team, but I'm looking forward to such a team. Even though you may think you are not experienced enough, it seems you just stepped forward and volunteered to lead this team. ;) I think initiative is more important than knowing the ins and outs of Python. I do hope Matthias could lead such a team. He responded to my mail this morning. He didn't take a clear position about the team but he indicated that he would come with a proposal this week-end (and that he would also upload python2.5 in experimental). He would like to tie this transition with the new infrastructure for handling python modules. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
Raphael Hertzog writes: On Thu, 06 Apr 2006, Sebastian Rittau wrote: Am Donnerstag, den 06.04.2006, 09:58 +0200 schrieb Raphael Hertzog: I'm not experienced enough with Python to lead such a maintenance team, but I'm looking forward to such a team. Even though you may think you are not experienced enough, it seems you just stepped forward and volunteered to lead this team. ;) I think initiative is more important than knowing the ins and outs of Python. I do hope Matthias could lead such a team. He responded to my mail this morning. He didn't take a clear position about the team but he indicated that he would come with a proposal this week-end (and that he would also upload python2.5 in experimental). He would like to tie this transition with the new infrastructure for handling python modules. [just realized that my mail did go to Raphael only, not intended] Raphael, thanks for your interest. It's true that I did not respond to emails ignoring our discussions from January and February on this very list. It would be nice to build on these discussions for the transition. Any news from your side? I think I did make it clear, that we should get away from the transition system for all kind of packages and implemented that (but side-tracked by other work in the last month). Please expect an update from this at this weekend. I'm not experienced enough with Python to lead such a maintenance team, but I'm looking forward to such a team. I'm sure one or more teams could be useful, packagers should be able to decide on their own if they want to join a team. There are lot of packages, where people did ask for maintainance (i.e. python-xml), but got no response. On the other teams like deb-scipy seem to just work. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
El Thu, Apr 06, 2006 at 09:58:02AM +0200, Raphael Hertzog va escriure: Who would be interested to help ? My time is limited but I'll be interested in joining the team. -- Sergio Talens-Oliag [EMAIL PROTECTED] http://people.debian.org/~sto/ Key fingerprint = 29DF 544F 1BD9 548C 8F15 86EF 6770 052B B8C1 FA69 signature.asc Description: Digital signature
Re: New python maintenance team
Who would be interested to help ? I'm interested to help too (Alioth abuss-guest) Antal A. Buss
