Twas brillig at 02:42:09 08.09.2009 UTC-07 when vor...@debian.org did gyre and gimble:
SL> Spare me your ignorant preaching and go read the mailing list SL> archives. Mailing list archives are not documentation. SL> It once lived at <http://people.debian.org/~piman/python-policy/> - SL> before the python policy process degenerated into such an absurd SL> mess that the maintainer left Debian entirely. Policy did not have any kind of rationale. I read it many times. The only question was: WHY?? SL> No, I'm not a dictator; I'm just a member of the Debian Release SL> Team who has watched in frustration as the python political SL> nonsense has failed for three years to deliver anything that SL> actually facilitates python version transitions - which was the SL> main reason for drafting a new python policy in the first place. This is not clear from the policy. SL> Thanks for pissing on the release team. Thanks for beating straw man. >> Single "why?" document would help to resolve situation much better than >> endless whining about "bad python-support developers". Just accept the >> facts that you've failed to communicate ideas behind policy, SL> The python-support maintainer knows the reasons already. This was SL> not a failure of communication, only a failure of collaboration. It would not be accepted in first place if there would be written rationale behind the policy. When I first had to chose between the helpers I went with the one which did not require me to pass magic jumbo-jumbo, and that was python-support with clearly stated the REASONS for all the stuff. python-central was the magic: "add this here and don't even try to ask us why it needs to be here". >> reevaluate situation and propose something that is constructive, >> this will be beneficial for all of us. SL> And why would that work any better now than it did three years ago? You've got an experience: unwritten knowledge leads to truely idiotic situations like current one. SL> If anything, the responses in this thread show that the list is far SL> more beset with python-support apologists now, who are even less SL> willing to approach the problem from a policy perspective and are SL> only interested in defending their favorite tool. I would repeat own words: BULLSHIT. But I don't want to discuss at this level. I know you're pissed of, but this won't help resolve situation. -- http://fossarchy.blogspot.com/
pgpW29y87Srsu.pgp
Description: PGP signature
