On 03/06/15 17:28, Haïkel wrote:
2015-06-03 17:23 GMT+02:00 Thomas Goirand <z...@debian.org>:
i
On 06/03/2015 12:41 AM, James E. Blair wrote:
Hi,
This came up at the TC meeting today, and I volunteered to provide an
update from the discussion.
I've just read the IRC logs. And there's one thing I would like to make
super clear.
I still haven't read the logs as we had our post-mortem meeting today,
but I'll try to address your points.
We, ie: Debian & Ubuntu folks, are very much clear on what we want to
achieve. The project has been maturing in our heads for like more than 2
years. We would like that ultimately, only a single set of packages Git
repositories exist. We already worked on *some* convergence during the
last years, but now we want a *full* alignment.
We're not 100% sure how the implementation details will look like for
the core packages (like about using the Debconf interface for
configuring packages), but it will eventually happen. For all the rest
(ie: Python module packaging), which represent the biggest work, we're
already converging and this has zero controversy.
Now, the Fedora/RDO/Suse people jumped on the idea to push packaging on
the upstream infra. Great. That's socially tempting. But technically, I
don't really see the point, apart from some of the infra tooling (super
cool if what Paul Belanger does works for both Deb+RPM). Finally,
indeed, this is not totally baked. But let's please not delay the
Debian+Ubuntu upstream Gerrit collaboration part because of it. We would
like to get started, and for the moment, nobody is approving the
/stackforge/deb-openstack-pkg-tools [1] new repository because we're
waiting on the TC decision.
First, we all agree that we should move packaging recipes (to use a
neutral term)
and reviewing to upstream gerrit. That should *NOT* be delayed.
We (RDO) are even willing to transfer full control of the openstack-packages
namespace on github. If you want to use another namespace, it's also
fine with us.
Then, about the infra/tooling things, it looks like a misunderstanding.
If we don't find an agreement on these topics, it's perfectly fine and
should not
prevent moving to upstream gerrit
So let's break the discussion in two parts.
1. upstream gerrit shared by everyone and get this started asap
In an attempt to document how this would look for RDO, I've started a
patch[1] that I'll iterate on while this discussions converges on a
solution that will work.
This patch would result in 80 packaging repositories being pulled into
gerrit.
I've left a TODO in the commit message to track questions I believe we
still have to answer, most notably
o exactly what namespace/prefix to use in the naming, I've seen lots of
opinions but I'm not clear if we have come to a decision
o Should we use "rdo" in the packaging repo names and not "rpm"? I think
this ultimatly depends whether the packaging can be shared between RDO
and Suse or not.
o Do the RDO packaging repo's fall under this project[2] or is it its
own group
[1] https://review.openstack.org/#/c/189497
[2] https://review.openstack.org/#/c/185187
2. continue discussion about infra/tooling within the new project, without
presumin the outcome.
Does it look like a good compromise to you?
Regards,
H.
Cheers,
Thomas Goirand (zigo)
[1] https://review.openstack.org/#/c/185164/
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
