A place to cache linked articles (think custom and personal wayback machine)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

index.md 2.1KB

4 jaren geleden
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. title: Transfer of power
  2. url: https://www.mail-archive.com/python-committers@python.org/msg05628.html
  3. hash_url: 5c19cc281938aa8a2140ada2a81d9d15
  4. Now that PEP 572 is done, I don't ever want to have to fight so hard for a
  5. PEP and find that so many people despise my decisions.
  6. I would like to remove myself entirely from the decision process. I'll
  7. still be there for a while as an ordinary core dev, and I'll still be
  8. available to mentor people -- possibly more available. But I'm basically
  9. giving myself a permanent vacation from being BDFL, and you all will be on
  10. your own.
  11. After all that's eventually going to happen regardless -- there's still
  12. that bus lurking around the corner, and I'm not getting younger... (I'll
  13. spare you the list of medical issues.)
  14. I am not going to appoint a successor.
  15. So what are you all going to do? Create a democracy? Anarchy? A
  16. dictatorship? A federation?
  17. I'm not worried about the day to day decisions in the issue tracker or on
  18. GitHub. Very rarely I get asked for an opinion, and usually it's not
  19. actually important. So this can just be dealt with as it has always been.
  20. The decisions that most matter are probably
  21. - How are PEPs decided
  22. - How are new core devs inducted
  23. We may be able to write up processes for these things as PEPs (maybe those
  24. PEPs will form a kind of constitution). But here's the catch. I'm going to
  25. try and let you all (the current committers) figure it out for yourselves.
  26. Note that there's still the CoC -- if you don't like that document your
  27. only option might be to leave this group voluntarily. Perhaps there are
  28. issues to decide like when should someone be kicked out (this could be
  29. banning people from python-dev or python-ideas too, since those are also
  30. covered by the CoC).
  31. Finally. A reminder that the archives of this list are public (
  32. <a rel="nofollow" href="https://mail.python.org/pipermail/python-committers/">https://mail.python.org/pipermail/python-committers/</a>) although membership
  33. is closed (limited to core devs).
  34. I'll still be here, but I'm trying to let you all figure something out for
  35. yourselves. I'm tired, and need a very long break.
  36. --Guido van Rossum (python.org/~guido)