Re: [Python-modules-team] [Openstack-devel] ITP: python-gear -- python-gear: pure python async library to interact with, gearman

2013-10-02 Thread Thomas Goirand
On 10/02/2013 05:01 AM, Scott Kitterman wrote:
> 
> 
> Julien Danjou  wrote:
>> On Tue, Oct 01 2013, Thomas Goirand wrote:
>>
>>> Could you please maintain this package using Git? It'd be nice, since
>>> that's an OpenStack stuff, and that everything there is maintained
>> using
>>> Git. If there is still resistance in the Python Module team, then you
>>> can use collab-maint. Your thoughts?
>>
>> This is not OpenStack related at all, there's no reason to limit its
>> maintenance to the OpenStack team.
>> I don't think the Python module team aims to switch to Git, so
>> collab-maint would be a good choice if git is retained.
> 
> Last time we discussed this,  we identified some things that needed to
> be resolved before we could switch.

I don't think there was anything to be resolved, just it needed someone
to work on it.

> The problem isn't resistance, but
> that the magic some people seem to be waiting for to do the work is
> being slow. 

I don't agree with this view. I saw that the Git repository of the team
has been *deactivated* by one of the PMT admins on Alioth. :(

Yes, there is resistance.

> Anyone who wants to switch to git should work on switching.

I would like to start uploading my modules in the Git of Alioth of the
team, regardless if there is still some old SVN repositories or not (and
this, because it's taking too much time until anyone does something,
though we've got some stuff to do...).

Though I don't have the admin rights on the PMT team to reactivate the
Git repo. Seeing that lots of people are using collab-maint instead of
the team VCS because SVN sux shows there's really a problem here, and
that we really need to accept Git repositories, even if old ones haven't
migrated (yet). Saying that we only want a single VCS type is already an
obsolete statement, as that's not the case anymore anyway if we consider
those in collab-maint.

Thomas


___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


Re: [Python-modules-team] [Openstack-devel] ITP: python-gear -- python-gear: pure python async library to interact with, gearman

2013-10-01 Thread Julien Danjou
On Tue, Oct 01 2013, Daniel Kahn Gillmor wrote:

> I'm doing this this by moving packages that i plan to work on into
> collab-maint, instead of the python modules team.  Sorry :(

I'm doing this too for what it's worth, and I don't think it's a
problem. Collab-maint is good to do that, and I can't see any issue
using it rather than the Python team repositories.

-- 
Julien Danjou
;; Free Software hacker ; independent consultant
;; http://julien.danjou.info


signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] [Openstack-devel] ITP: python-gear -- python-gear: pure python async library to interact with, gearman

2013-10-01 Thread Daniel Kahn Gillmor
On 10/01/2013 05:01 PM, Scott Kitterman wrote:
> Julien Danjou  wrote:
>> This is not OpenStack related at all, there's no reason to limit its
>> maintenance to the OpenStack team.
>> I don't think the Python module team aims to switch to Git, so
>> collab-maint would be a good choice if git is retained.
> 
> Last time we discussed this,  we identified some things that needed to be 
> resolved before we could switch. The problem isn't resistance,  but that the 
> magic some people seem to be waiting for to do the work is being slow. 

This is unfortunately not my recollection of events, but i don't have
the time or mental energy to dig back through the archives right now and
rehash that struggle.  I'll just say that as someone who hoped to help
the python module team move to git, i felt the resistance was
sufficiently strong that my limited time was best used elsewhere.

> Anyone who wants to switch to git should work on switching. I'm not planning 
> to work on it myself because I don't care which we use. 

I'm doing this this by moving packages that i plan to work on into
collab-maint, instead of the python modules team.  Sorry :(

--dkg



signature.asc
Description: OpenPGP digital signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] [Openstack-devel] ITP: python-gear -- python-gear: pure python async library to interact with, gearman

2013-10-01 Thread Scott Kitterman


Julien Danjou  wrote:
>On Tue, Oct 01 2013, Thomas Goirand wrote:
>
>> Could you please maintain this package using Git? It'd be nice, since
>> that's an OpenStack stuff, and that everything there is maintained
>using
>> Git. If there is still resistance in the Python Module team, then you
>> can use collab-maint. Your thoughts?
>
>This is not OpenStack related at all, there's no reason to limit its
>maintenance to the OpenStack team.
>I don't think the Python module team aims to switch to Git, so
>collab-maint would be a good choice if git is retained.

Last time we discussed this,  we identified some things that needed to be 
resolved before we could switch. The problem isn't resistance,  but that the 
magic some people seem to be waiting for to do the work is being slow. 

Anyone who wants to switch to git should work on switching. I'm not planning to 
work on it myself because I don't care which we use. 

Scott K


___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


Re: [Python-modules-team] [Openstack-devel] ITP: python-gear -- python-gear: pure python async library to interact with, gearman

2013-10-01 Thread Julien Danjou
On Tue, Oct 01 2013, Thomas Goirand wrote:

> Could you please maintain this package using Git? It'd be nice, since
> that's an OpenStack stuff, and that everything there is maintained using
> Git. If there is still resistance in the Python Module team, then you
> can use collab-maint. Your thoughts?

This is not OpenStack related at all, there's no reason to limit its
maintenance to the OpenStack team.
I don't think the Python module team aims to switch to Git, so
collab-maint would be a good choice if git is retained.

-- 
Julien Danjou
/* Free Software hacker * independent consultant
   http://julien.danjou.info */


signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team