Le 21/09/2018 à 16:35, Guido van Rossum a écrit : > Perhaps worth including in PEP 8002, the overview of other governance > models? (Though the process described here seems to be JS's equivalent > of our PEP process -- it doesn't say anything about how TC39 gets formed > or how non-technical decisions are handled.)
Right, I think further research (and/or a contact with the right persons to answer our questions) may be necessary before including it in the survey. I don't have much time myself, unfortunately (I didn't even get a chance to entirely read the other contributions to the PEP :-/). Regards Antoine. > > ---------- Forwarded message --------- > From: *James Lu* <jam...@gmail.com <mailto:jam...@gmail.com>> > Date: Fri, Sep 21, 2018 at 4:25 AM > Subject: [Python-ideas] JS’ governance model is worth inspecting > To: <python-id...@python.org <mailto:python-id...@python.org>> > > > JS’ decisions are made by a body known as TC39, a fairly/very small > group of JS implementers. > > First, JS has an easy and widely supported way to modify the language > for yourself: Babel. Babel transpires your JS to older JS, which is then > run. > > You can publish your language modification on the JS package manager, npm. > > When a feature is being considered for inclusion in mainline JS, the > proposal must first gain a champion (represented by 🚀)that is a member > of TC-39. The guidelines say that the proposal’s features should already > have found use in the community. Then it moves through three stages, and > the champion must think the proposal is ready for the next stage before > it can move on. I’m hazy on what the criterion for each of the three > stages is. The fourth stage is approved. > > I believe the global TC39 committee meets regularly in person, and at > those meetings, proposals can advance stages- these meetings are > frequent enough for the process to be fast and slow enough that people > can have the time to try out a feature before it becomes main line JS. > Meeting notes are made public. > > The language and its future features are discussed on ESDiscuss.org, > which is surprisingly filled with quality and respectful discussion, > largely from experts in the JavaScript language. > > I’m fairly hazy on the details, this is just the summary off the top of > my head. > > — > I’m not saying this should be Python’s governance model, just to keep > JS’ in mind. > > > _______________________________________________ > Python-ideas mailing list > python-id...@python.org <mailto:python-id...@python.org> > https://mail.python.org/mailman/listinfo/python-ideas > Code of Conduct: http://python.org/psf/codeofconduct/ > > > -- > --Guido van Rossum (python.org/~guido <http://python.org/%7Eguido>) > > > _______________________________________________ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/