[PKG-Openstack-devel] Accepted python-eventlet 0.20.0-1 (source all) into unstable

[Ondrej Novy]

Hi,

2017-11-12 2:11 GMT+01:00 Thomas Goirand <zigo at debian.org>:

> If you look at the case of Eventlet, it's used only in OpenStack. And
> not just only once, but 38 times (in 38 packages both as runtime and
> build dependency). So to me, it really doesn't fit the bill of being
> "general purpose", and OpenStack is too dependent on it. Best is if it
> can follow the OpenStack release too.
>

I'm using eventlet in our company project. It's not OpenStack upstream and
I don't see reason why it should be under OS team. It's general purpose
python library and really import for me. And we made a deal: ALL non OS
upstream python packages should be moved to DPMT. No more rules.

If you want to control upgrading of eventlet, you can with correct setting
of DPMT into uploaders, not maintainers.

All packages in global constrains is important for OS, let's move them all
to OS team? Already talked about this, we already made a decision and deal.


> I don't understand why you "jumped" on this particular package, just to
> change team, and do other types of cosmetic changes. I would have very
> much preferred if you tried to do what I'm doing right now: upgrading to
> the version matching the upper-constraints.txt file (ie: 0.20.0), and
> fix the Python 2.7 issues that it brings (yes, Eventlet has switched
> some of its code to Python 3 only). I would have very much preferred if
> you took some other less key packages, like falcon, all the
> python-nose*, and many others (see below).
>

because I'm comaintainer and I hate openstack-pkg-tools for building.
Pybuild is much better and I want to use pybuild for every of my python
non-openstack packages. And we need more cooperation from DPMT team.

I did, on IRC, and I'm ok to discuss it more, there or in this list.
>

you didn't asked, you just 'reported' that you did it. You need to
communicate FIRST.

zigo | onovy: As Eventlet is used exclusively in OpenStack, I don't think
it makes sense to push it to DPMT, so I I've took it back.

You should ask __first__, then talk, and then (optionally) upload if we
make a deal. If I'm co-maintainer, we __need__ to communicate.


> >     Revert this upload or I will quit openstack team.
>
> Oh... (shocked!). Are you sure it's the way to deal with things? I would
> very much prefer if you calm down, and just discuss before this type of
> message. If you do leave, I'll miss you, and others probably too. But I
> wont act under this type of pressure, blackmailing others is *not* the
> way to solve issues, or to discuss what you feel is a problem.
>

you started. You didn't discussed it and made change. We can talk after you
do rollback. If you are not going to rollback it, please remove me from
team. We made deal and you broke it. Sorry, your decision.

Sorry, but I'm really pissed off and it looks like it's not possible to
cooperate with you at all. I tried, but for you it's "one man show" - only
your opinion is right. So let's do OS yourself and I will migrate my
deployment to Ubuntu. Bye.

-- 
Best regards
 Ondřej Nový

Email: novy at ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20171112/5bfee8a5/attachment.html>