Re: [openstack-dev] Can sqlalchemy-migrate-core just be oslo.db core?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/10/14 23:44, Doug Hellmann wrote: On Oct 9, 2014, at 4:30 PM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: The sqlalchemy-migrate project is basically maintenance mode and the core team [1] is kind of a weird mix of people - all great people I'm sure, but I think it's more a team of people that stepped up when OpenStack took over the project and said they'd babysit it but it's pretty idle. Given we have oslo.db now, and sqlalchemy-migrate is all DB goodies, can we just have the oslo.db core team [2] own sqlalchemy-migrate now too? Here are the sqlalchemy-migrate open reviews: https://review.openstack.org/#/q/status:open+project:stackforge/sqlalchemy-migrate,n,z [1] https://review.openstack.org/#/admin/groups/186,members [2] https://review.openstack.org/#/admin/groups/331,members If the oslo.db team wants to participate, that’s obviously fine, but I don’t think we want to just add everyone in bulk. AIUI, the team’s goal is to get the migration stuff in oslo.db working with alembic so we can stop using sqlalchemy-migrate. Till that time, we're left with the library used by multiple projects. I feel it's hard to get any review in meaningful time for the library, so if moving the library under the oslo.db tent will help it move, I'm both hands for that. /Ihar -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUN7B4AAoJEC5aWaUY1u57JLIH/jn9iREgmRhvfiZosiN9knxV xrVFgEpZ35G5kGmWrnnnKvbWUIvIawwoA2OCOCMXScL5xwzLtn9+prvcujvGK3g1 /zk1aVKnKv90zR6j0ATgTq49tQQpVVe1KkaePzWRYIkU22f7KAPGmwjQlLfebV06 bWOS5HyUeueAIno67EVY3AM669JtKmS6ZqswIciEfMvsOmdDDrDje1qVUH9VVsoy UkvOQ+CPCTqwjIpbkbDrfIXJpA5qm0cCwPx8wDoYnEUN7laGjTtV0JMwGKwjBti0 y4ubs0X5xOU2ayr7xJXbeHCSB5eZKVZesbDyOCCk+lIaldih3qN6AR+Snncwjy4= =Ex7c -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Can sqlalchemy-migrate-core just be oslo.db core?
On Oct 10, 2014, at 6:10 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: Signed PGP part On 09/10/14 23:44, Doug Hellmann wrote: On Oct 9, 2014, at 4:30 PM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: The sqlalchemy-migrate project is basically maintenance mode and the core team [1] is kind of a weird mix of people - all great people I'm sure, but I think it's more a team of people that stepped up when OpenStack took over the project and said they'd babysit it but it's pretty idle. Given we have oslo.db now, and sqlalchemy-migrate is all DB goodies, can we just have the oslo.db core team [2] own sqlalchemy-migrate now too? Here are the sqlalchemy-migrate open reviews: https://review.openstack.org/#/q/status:open+project:stackforge/sqlalchemy-migrate,n,z [1] https://review.openstack.org/#/admin/groups/186,members [2] https://review.openstack.org/#/admin/groups/331,members If the oslo.db team wants to participate, that’s obviously fine, but I don’t think we want to just add everyone in bulk. AIUI, the team’s goal is to get the migration stuff in oslo.db working with alembic so we can stop using sqlalchemy-migrate. Till that time, we're left with the library used by multiple projects. I feel it's hard to get any review in meaningful time for the library, so if moving the library under the oslo.db tent will help it move, I'm both hands for that. It is not generally our community’s practice to assign core responsibility for a code base to anyone, especially without asking. Invite anyone to join the reviewer team, but please do not assume that just because there is a team working on database related code they are also interested in working on this code. Doug /Ihar ___ 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] Can sqlalchemy-migrate-core just be oslo.db core?
On 10/10/2014 06:10 PM, Ihar Hrachyshka wrote: On 09/10/14 23:44, Doug Hellmann wrote: On Oct 9, 2014, at 4:30 PM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: The sqlalchemy-migrate project is basically maintenance mode and the core team [1] is kind of a weird mix of people - all great people I'm sure, but I think it's more a team of people that stepped up when OpenStack took over the project and said they'd babysit it but it's pretty idle. Given we have oslo.db now, and sqlalchemy-migrate is all DB goodies, can we just have the oslo.db core team [2] own sqlalchemy-migrate now too? Here are the sqlalchemy-migrate open reviews: https://review.openstack.org/#/q/status:open+project:stackforge/sqlalchemy-migrate,n,z [1] https://review.openstack.org/#/admin/groups/186,members [2] https://review.openstack.org/#/admin/groups/331,members If the oslo.db team wants to participate, that’s obviously fine, but I don’t think we want to just add everyone in bulk. AIUI, the team’s goal is to get the migration stuff in oslo.db working with alembic so we can stop using sqlalchemy-migrate. Till that time, we're left with the library used by multiple projects. I feel it's hard to get any review in meaningful time for the library, so if moving the library under the oslo.db tent will help it move, I'm both hands for that. /Ihar I'm not sure adding core reviewers would help, but I agree we have a maintenance issue with sqlalchemy-migrate. I've seen useful patches staging without core reviewer answers. I'm myself a core there, but I don't think I have the needed level to do good reviews. Cheers, Thomas Goirand (zigo) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Can sqlalchemy-migrate-core just be oslo.db core?
On 10/9/2014 3:30 PM, Matt Riedemann wrote: The sqlalchemy-migrate project is basically maintenance mode and the core team [1] is kind of a weird mix of people - all great people I'm sure, but I think it's more a team of people that stepped up when OpenStack took over the project and said they'd babysit it but it's pretty idle. Given we have oslo.db now, and sqlalchemy-migrate is all DB goodies, can we just have the oslo.db core team [2] own sqlalchemy-migrate now too? Here are the sqlalchemy-migrate open reviews: https://review.openstack.org/#/q/status:open+project:stackforge/sqlalchemy-migrate,n,z [1] https://review.openstack.org/#/admin/groups/186,members [2] https://review.openstack.org/#/admin/groups/331,members If no one wants this, I'll nominate myself for the sqlalchemy-migrate core team to try and keep the lights on. Here's my code: https://review.openstack.org/#/q/owner:mrie...@us.ibm.com+project:stackforge/sqlalchemy-migrate,n,z And reviews: https://review.openstack.org/#/q/reviewer:mrie...@us.ibm.com+project:stackforge/sqlalchemy-migrate,n,z -- Thanks, Matt Riedemann ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Can sqlalchemy-migrate-core just be oslo.db core?
On Oct 9, 2014, at 4:30 PM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: The sqlalchemy-migrate project is basically maintenance mode and the core team [1] is kind of a weird mix of people - all great people I'm sure, but I think it's more a team of people that stepped up when OpenStack took over the project and said they'd babysit it but it's pretty idle. Given we have oslo.db now, and sqlalchemy-migrate is all DB goodies, can we just have the oslo.db core team [2] own sqlalchemy-migrate now too? Here are the sqlalchemy-migrate open reviews: https://review.openstack.org/#/q/status:open+project:stackforge/sqlalchemy-migrate,n,z [1] https://review.openstack.org/#/admin/groups/186,members [2] https://review.openstack.org/#/admin/groups/331,members If the oslo.db team wants to participate, that’s obviously fine, but I don’t think we want to just add everyone in bulk. AIUI, the team’s goal is to get the migration stuff in oslo.db working with alembic so we can stop using sqlalchemy-migrate. Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
