On 11/27/2016 09:16 PM, Bernd Zeimetz wrote: > Dear Thomas, > > On 11/26/2016 10:49 PM, Thomas Goirand wrote: > >> Not amused, > > you might know that your relation to the Python Modules team is not the > best, and I assume you still are not allowed to commit there at all. You > might feel honored, you are the only DD who managed to come into such a > situation.
1/ This is off topic, and has nothing to do with the issue I raised. Please stick to the technical problems. 2/ The toxic atmosphere of the team and my (temporary) eviction, lead by a few aggressive people, is far from gathering consensus. The only thing is that a lot of contributor just ran away from the team. This drove me away too. So, job well done. 3/ I do have write access again since July, after help from a TC member who managed to act as a mediator and discussed the issue with Piotr. > So instead of starting a largish discussion and wasting peoples' time > you could just have said: 'ouch, that was a bad timing, can you help me > to get these packages fixed?' and I'm sure your openstack would be happy > again already. I'm raising this thread because that's the 3rd (or 4th?) time SQLA uploads are breaking OpenStack. I see no other way to make it stop but to expose the issue (and its maintainer) publicly, since he ignored me. I'm calling for a release team transition management, as the package maintainer doesn't seem to know how to handle it the correct way. > You might want to learn that openstack is not Debian. There are way more > packages and things to consider than openstack alone. I do care for everything else in Debian as well. The fact we have package coexisting is exactly why we have transitions managed by the release team: so that every package is considered. The careless attitude isn't on my side here. Cheers, Thomas Goirand (zigo)
