Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
I am happy to help to but I don't have much extra bandwidth at the moment, so I can only play a supporting role as a core and not a leadership role. On Sat, Jul 13, 2013 at 2:58 PM, Michael Still mi...@stillhq.com wrote: I'm happy to help, although I'm pretty busy... Michael On Fri, Jul 12, 2013 at 9:37 PM, Boris Pavlovic bo...@pavlovic.me wrote: Hi Sean, I agree to help with sqlalchemy-migrate until we remove it. But probably there should be one more person mikal Best regards, Boris Pavlovic On Fri, Jul 12, 2013 at 3:31 PM, Sean Dague s...@dague.net wrote: On 07/12/2013 04:29 AM, Thierry Carrez wrote: Monty Taylor wrote: This brings us to the most important question: Who wants to be on the core team? That's the important question indeed. Accepting it (permanently or temporarily) under stackforge is an easy decision. But it's useless unless we have a set of people sufficiently interested in it not bitrotting to volunteer to maintain it... I'd recommend the nova-db subteam folks, like: jog0, dripton, boris-42 as good people to be +2 on this. -Sean -- Sean Dague http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
Monty thanks a lot! By the way there are 2 more guys that have a lot of experience with sqlalchemy-migrate: 1) Roman (rpodolyaka) 2) Viktor (vsergeyev) Best regards, Boris Pavlovic On Tue, Jul 16, 2013 at 11:12 PM, Joe Gordon joe.gord...@gmail.com wrote: I am happy to help to but I don't have much extra bandwidth at the moment, so I can only play a supporting role as a core and not a leadership role. On Sat, Jul 13, 2013 at 2:58 PM, Michael Still mi...@stillhq.com wrote: I'm happy to help, although I'm pretty busy... Michael On Fri, Jul 12, 2013 at 9:37 PM, Boris Pavlovic bo...@pavlovic.me wrote: Hi Sean, I agree to help with sqlalchemy-migrate until we remove it. But probably there should be one more person mikal Best regards, Boris Pavlovic On Fri, Jul 12, 2013 at 3:31 PM, Sean Dague s...@dague.net wrote: On 07/12/2013 04:29 AM, Thierry Carrez wrote: Monty Taylor wrote: This brings us to the most important question: Who wants to be on the core team? That's the important question indeed. Accepting it (permanently or temporarily) under stackforge is an easy decision. But it's useless unless we have a set of people sufficiently interested in it not bitrotting to volunteer to maintain it... I'd recommend the nova-db subteam folks, like: jog0, dripton, boris-42 as good people to be +2 on this. -Sean -- Sean Dague http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
I'm happy to help, although I'm pretty busy... Michael On Fri, Jul 12, 2013 at 9:37 PM, Boris Pavlovic bo...@pavlovic.me wrote: Hi Sean, I agree to help with sqlalchemy-migrate until we remove it. But probably there should be one more person mikal Best regards, Boris Pavlovic On Fri, Jul 12, 2013 at 3:31 PM, Sean Dague s...@dague.net wrote: On 07/12/2013 04:29 AM, Thierry Carrez wrote: Monty Taylor wrote: This brings us to the most important question: Who wants to be on the core team? That's the important question indeed. Accepting it (permanently or temporarily) under stackforge is an easy decision. But it's useless unless we have a set of people sufficiently interested in it not bitrotting to volunteer to maintain it... I'd recommend the nova-db subteam folks, like: jog0, dripton, boris-42 as good people to be +2 on this. -Sean -- Sean Dague http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
Monty Taylor wrote: This brings us to the most important question: Who wants to be on the core team? That's the important question indeed. Accepting it (permanently or temporarily) under stackforge is an easy decision. But it's useless unless we have a set of people sufficiently interested in it not bitrotting to volunteer to maintain it... -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
On 07/12/2013 04:29 AM, Thierry Carrez wrote: Monty Taylor wrote: This brings us to the most important question: Who wants to be on the core team? That's the important question indeed. Accepting it (permanently or temporarily) under stackforge is an easy decision. But it's useless unless we have a set of people sufficiently interested in it not bitrotting to volunteer to maintain it... I'd recommend the nova-db subteam folks, like: jog0, dripton, boris-42 as good people to be +2 on this. -Sean -- Sean Dague http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
Hi Sean, I agree to help with sqlalchemy-migrate until we remove it. But probably there should be one more person mikal Best regards, Boris Pavlovic On Fri, Jul 12, 2013 at 3:31 PM, Sean Dague s...@dague.net wrote: On 07/12/2013 04:29 AM, Thierry Carrez wrote: Monty Taylor wrote: This brings us to the most important question: Who wants to be on the core team? That's the important question indeed. Accepting it (permanently or temporarily) under stackforge is an easy decision. But it's useless unless we have a set of people sufficiently interested in it not bitrotting to volunteer to maintain it... I'd recommend the nova-db subteam folks, like: jog0, dripton, boris-42 as good people to be +2 on this. -Sean -- Sean Dague http://dague.net __**_ OpenStack-dev mailing list OpenStack-dev@lists.openstack.**org OpenStack-dev@lists.openstack.org http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-devhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
On 07/12/2013 07:37 AM, Boris Pavlovic wrote: Hi Sean, I agree to help with sqlalchemy-migrate until we remove it. But probably there should be one more person mikal Done. https://github.com/stackforge/sqlalchemy-migrate This is up and active, and it will run unittests. Right now it only runs them on sqlite, but making them run against mysql should be easy (we just need to put the user/pass we use for nova unittests against mysql into the test_db.cfg file - same with postgres) The project is set up to publish docs to RTFD (although there is a bug in that setup right now) and to publish packages to PyPI on tags just like our other projects. Have fun everyone. Best regards, Boris Pavlovic On Fri, Jul 12, 2013 at 3:31 PM, Sean Dague s...@dague.net mailto:s...@dague.net wrote: On 07/12/2013 04:29 AM, Thierry Carrez wrote: Monty Taylor wrote: This brings us to the most important question: Who wants to be on the core team? That's the important question indeed. Accepting it (permanently or temporarily) under stackforge is an easy decision. But it's useless unless we have a set of people sufficiently interested in it not bitrotting to volunteer to maintain it... I'd recommend the nova-db subteam folks, like: jog0, dripton, boris-42 as good people to be +2 on this. -Sean -- Sean Dague http://dague.net _ OpenStack-dev mailing list OpenStack-dev@lists.openstack.__org mailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
On 07/12/2013 07:31 AM, Sean Dague wrote: On 07/12/2013 04:29 AM, Thierry Carrez wrote: Monty Taylor wrote: This brings us to the most important question: Who wants to be on the core team? That's the important question indeed. Accepting it (permanently or temporarily) under stackforge is an easy decision. But it's useless unless we have a set of people sufficiently interested in it not bitrotting to volunteer to maintain it... I'd recommend the nova-db subteam folks, like: jog0, dripton, boris-42 as good people to be +2 on this. I'm happy to help, as long as there are at least 2 others. -- David Ripton Red Hat drip...@redhat.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
OpenStack is currently divided. Older projects like Nova use sqlalchemy-migrate. Some newer projects like Neutron use alembic. I'd personally like to see everything in Alembic, but migrating all the Nova scripts in a way that didn't break compatibility will be a big challenge. It's easier for projects with less to port. Another option is to take over maintaining sqlalchemy-migrate and bend it to our needs. (It's mostly okay, but the big issue for me is its use of strictly incrementing integer sequence numbers. That both causes problems when competing patches in review race for the same filename, and when we try to backport some but not all migration scripts to a stable branch.) We already apply some patches to upstream, so having a friendly maintainer who would apply patches that OpenStack needs would be helpful. This will be a topic at the DB meeting today at 1900 UTC (about 20 minutes from when I send this email). So please attend if it's important to you. On 07/11/2013 02:18 PM, Thomas Goirand wrote: Discussing with Jan Dittberner, who is upstream for sqlalchemy-migrate, it appears that he doesn't have time to maintain it. Is the OpenStack project willing to take over? Jan is ok to hand over everything, moving to Github, give access to Pypi, etc. Below is his reply to me when I asked him. Or is the OpenStack project moving toward Alembic as well? Thoughts anyone? Thomas Goirand (zigo) On 07/12/2013 01:27 AM, Jan Dittberner wrote: I would be very happy to hand over the maintenance of sqlalchemy-migrate to a team that actually uses it. At the moment I take care of the Google Code [1] project for sqlalchemy-migrate and maintain a Jenkins instance at http://jenkins.gnuviech-server.de/. I'm all in favour of moving to github, Google Code was just choosen because it was available at the time the project moved from the initial developer's (Evan Rosson) personal server. I can also give access to the PyPI project page [2] to a prospective new maintainer/team. I wrote some sphinx documentation and improved the tests a while ago but I have no time to maintain it properly. I switched to alembic for my small personal projects. [1] https://code.google.com/p/sqlalchemy-migrate/ [2] https://pypi.python.org/pypi/sqlalchemy-migrate Best regards Jan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- David Ripton Red Hat drip...@redhat.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
On 07/11/2013 02:40 PM, David Ripton wrote: OpenStack is currently divided. Older projects like Nova use sqlalchemy-migrate. Some newer projects like Neutron use alembic. I'd personally like to see everything in Alembic, but migrating all the Nova scripts in a way that didn't break compatibility will be a big challenge. It's easier for projects with less to port. Another option is to take over maintaining sqlalchemy-migrate and bend it to our needs. (It's mostly okay, but the big issue for me is its use of strictly incrementing integer sequence numbers. That both causes problems when competing patches in review race for the same filename, and when we try to backport some but not all migration scripts to a stable branch.) We already apply some patches to upstream, so having a friendly maintainer who would apply patches that OpenStack needs would be helpful. This will be a topic at the DB meeting today at 1900 UTC (about 20 minutes from when I send this email). So please attend if it's important to you. On 07/11/2013 02:18 PM, Thomas Goirand wrote: Discussing with Jan Dittberner, who is upstream for sqlalchemy-migrate, it appears that he doesn't have time to maintain it. Is the OpenStack project willing to take over? Jan is ok to hand over everything, moving to Github, give access to Pypi, etc. Below is his reply to me when I asked him. Hi - We discussed this in the db meeting and decided that as much as we're not thrilled with sqlalchemy-migrate (I believe boris-42 summed it up as bad bad bad very bad things) we've got a pretty strong dependency on it right now and for the next while. SO - let's work on getting it moved into our systems and then we at least have the ability to patch/release if needed. Or is the OpenStack project moving toward Alembic as well? Thoughts anyone? Thomas Goirand (zigo) On 07/12/2013 01:27 AM, Jan Dittberner wrote: I would be very happy to hand over the maintenance of sqlalchemy-migrate to a team that actually uses it. At the moment I take care of the Google Code [1] project for sqlalchemy-migrate and maintain a Jenkins instance at http://jenkins.gnuviech-server.de/. I'm all in favour of moving to github, Google Code was just choosen because it was available at the time the project moved from the initial developer's (Evan Rosson) personal server. I can also give access to the PyPI project page [2] to a prospective new maintainer/team. I wrote some sphinx documentation and improved the tests a while ago but I have no time to maintain it properly. I switched to alembic for my small personal projects. [1] https://code.google.com/p/sqlalchemy-migrate/ [2] https://pypi.python.org/pypi/sqlalchemy-migrate Best regards Jan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
On 07/11/2013 03:12 PM, Monty Taylor wrote: On 07/11/2013 02:40 PM, David Ripton wrote: OpenStack is currently divided. Older projects like Nova use sqlalchemy-migrate. Some newer projects like Neutron use alembic. I'd personally like to see everything in Alembic, but migrating all the Nova scripts in a way that didn't break compatibility will be a big challenge. It's easier for projects with less to port. Another option is to take over maintaining sqlalchemy-migrate and bend it to our needs. (It's mostly okay, but the big issue for me is its use of strictly incrementing integer sequence numbers. That both causes problems when competing patches in review race for the same filename, and when we try to backport some but not all migration scripts to a stable branch.) We already apply some patches to upstream, so having a friendly maintainer who would apply patches that OpenStack needs would be helpful. This will be a topic at the DB meeting today at 1900 UTC (about 20 minutes from when I send this email). So please attend if it's important to you. On 07/11/2013 02:18 PM, Thomas Goirand wrote: Discussing with Jan Dittberner, who is upstream for sqlalchemy-migrate, it appears that he doesn't have time to maintain it. Is the OpenStack project willing to take over? Jan is ok to hand over everything, moving to Github, give access to Pypi, etc. Below is his reply to me when I asked him. Hi - We discussed this in the db meeting and decided that as much as we're not thrilled with sqlalchemy-migrate (I believe boris-42 summed it up as bad bad bad very bad things) we've got a pretty strong dependency on it right now and for the next while. SO - let's work on getting it moved into our systems and then we at least have the ability to patch/release if needed. We've got the upstream pypi and rtfd credentials now, the project should be moved in to openstack systems soon enough. I also went through and cleaned up build and test stuff work work like our stuff works (if we're going to be maintaining it, we might as well, you know, do it how we do things) This brings us to the most important question: Who wants to be on the core team? Or is the OpenStack project moving toward Alembic as well? Thoughts anyone? Thomas Goirand (zigo) On 07/12/2013 01:27 AM, Jan Dittberner wrote: I would be very happy to hand over the maintenance of sqlalchemy-migrate to a team that actually uses it. At the moment I take care of the Google Code [1] project for sqlalchemy-migrate and maintain a Jenkins instance at http://jenkins.gnuviech-server.de/. I'm all in favour of moving to github, Google Code was just choosen because it was available at the time the project moved from the initial developer's (Evan Rosson) personal server. I can also give access to the PyPI project page [2] to a prospective new maintainer/team. I wrote some sphinx documentation and improved the tests a while ago but I have no time to maintain it properly. I switched to alembic for my small personal projects. [1] https://code.google.com/p/sqlalchemy-migrate/ [2] https://pypi.python.org/pypi/sqlalchemy-migrate Best regards Jan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
On 07/12/2013 07:29 AM, Monty Taylor wrote: We've got the upstream pypi and rtfd credentials now, the project should be moved in to openstack systems soon enough. I also went through and cleaned up build and test stuff work work like our stuff works (if we're going to be maintaining it, we might as well, you know, do it how we do things) Cool! You definitively rox my friend. You might as well want to apply Fedora's patch (thanks to Pádraig Brady) for SQLAlchemy 0.8: http://pkgs.fedoraproject.org/cgit/python-migrate.git/commit/?id=603ed1d1 which was the reason I started the discussion with Jan Dittberner. Jan wrote to me that there's more to = 0.8 compat than just this patch, but I had not time to dig it through. Thomas ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
On 2013-07-12 08:01:58 +0800 (+0800), Thomas Goirand wrote: [...] You might as well want to apply Fedora's patch (thanks to Pádraig Brady) for SQLAlchemy 0.8: http://pkgs.fedoraproject.org/cgit/python-migrate.git/commit/?id=603ed1d1 which was the reason I started the discussion with Jan Dittberner. [...] At this point any of you can simply propose it as a code review change to the stackforge/sqlalchemy-migrate project. Also, if anyone wants to volunteer as initial members of sqlalchemy-migrate-core... -- Jeremy Stanley ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SQLAlchemy-migrate needs a new maintainer
On 07/11/2013 08:01 PM, Thomas Goirand wrote: On 07/12/2013 07:29 AM, Monty Taylor wrote: We've got the upstream pypi and rtfd credentials now, the project should be moved in to openstack systems soon enough. I also went through and cleaned up build and test stuff work work like our stuff works (if we're going to be maintaining it, we might as well, you know, do it how we do things) Cool! You definitively rox my friend. You might as well want to apply Fedora's patch (thanks to Pádraig Brady) for SQLAlchemy 0.8: http://pkgs.fedoraproject.org/cgit/python-migrate.git/commit/?id=603ed1d1 which was the reason I started the discussion with Jan Dittberner. Jan wrote to me that there's more to = 0.8 compat than just this patch, but I had not time to dig it through. Done. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
