Re: Bug#724980: ITP: trove -- Database as a Service for OpenStack
On 10/01/2013 10:03 PM, Jonathan Dowland wrote:
> On Tue, Oct 01, 2013 at 09:42:37PM +0800, Thomas Goirand wrote:
>> That much?!? Where did you get the list of ITPs for OpenStack?
>
> GET
> 'http://bugs.debian.org/cgi-bin/pkgreport.cgi?owner=zigo%40debian.org;dist=unstable'
> | grep ITP|wc -l
>
> No doubt something smarter is possible with UDD.
Well, you have included in your "36 ITP" the 22 packages which have
already passed the NEW queue...
I see only 8 ITP opened here, and 7 more that are already waiting in the
NEW queue. On the 8 ITP that are opened, there's python-os-apply-config,
python-diskimage-builder, trove, and neutron (that one is already
uploaded to Experimental), which are, I believe, already fit for upload.
python-statsdpy I am unsure I will work on it. python-socksipy should be
renamed as ITA. Then there's edeploy, which isn't ready yet upstream.
google-api-python-client is waiting for a fix upstream (they use
"apiclient" as folder, which IMO is poluting the namespace, and upstream
agrees). FYI, I am currently testing Trove before uploading.
Though, I agree with you, I could open a few RFS:
- tripleo-heat-templates
- ironic
- tripleo-image-elements
- python-ironicclient
There's also these who will need an update before the forthcoming Havana
release:
- python-falcon
- python-wsme >= 0.5b5
- python-cliff >= 1.4.3
- python-sphinxcontrib-pecanwsme >= 0.3
- python-novaclient >= 2.15
- python-ceilometerclient >= 1.0.5
- python-pycadf >= 0.1.9
- oslo.config >= 1.2.1
I don't think it's that hard to update, though I believe one would need
upload rights for it (because unfortunately, it would take as much time
for me to do the work as for sponsoring it).
Though I do think I'll work on them before anyone else does (I hope to
finish that before the release of OpenStack Havana, on the 17th of this
month. If anyone wants to help, then best is to follow the
openstack-devel@lists.alioth.debian.org list, where I do post some TODO
list when asked.
Also, for anyone who wish to join the OpenStack packaging effort, I
would recommend joining #debian-openstack (general discussion and
packaging channel) and #debian-openstack-commits (output of the KGB bot
for the packaging project, and output of my 4 Jenkins machines with
links to build logs after packages are built).
Cheers,
Thomas Goirand (zigo)
Reply to: