-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 For us, I think the value of a DEP is in putting the conclusion of a discussion in one place, rather than forcing everyone to read the entire thread to know how it went. To that end, I don't think anything needs to change about how we accept DEPs.
Alex -----BEGIN PGP SIGNATURE----- Version: Mailvelope v0.8.0 Comment: Email security by Mailvelope - http://www.mailvelope.com wsFcBAEBCAAQBQJTTCE4CRASX1xn3+lAhAAAjBoP/3c3P30xlHh1Z3BDvrS5 LHuzyQR/Lp3rws+83Cnh0Xi154xcWkd1np5PvbXXya747NSLEIayryDHiYlw hhdeGFA77TJxG/q6LRjbDAgFq7YsLERtIYLkWvWmiFTuKZDHELj4oGGs9SQS LjGm+r0M32LQPpV8yui3rBP1AbBl1/KddztyzzQqNdYEhvahxiScKFaOE+vH bSbsCONZv1TCFDcpy4y70Mlz9CzLsNpanO9Mjq8066RG0MB9HKr6w5Yqi6OS ItYQrmiiLcAwARi3BlRqBsmBcWGJ55pOfNXq3GPwScWiQ1ySap2W4+rbml1C 7Fxfp1KIE4DfLmfiQuPgCWZhrpr1hRBdVRXXHvWkYnPmxlXWUFxFwgrtSeZh fC5t9F3jmSG02L2JnwHjhynSOTyh9d+bCbRE/hdij+DP0v9iZBGNvzQq04Dy X72xJ99R7mRKHrHjvPa0IMuRqpXia/fPn1+2t2Ujf32nXDc+V3l+BTWm9W+D b1LFjpfJJwXoho4VK5bPu+NDibWR62HZ64ee3Hq2/g+H7o8WGNPk4YOFwCmS eLnrM44Zg+nwtzhstiW15nS2znIMrce6Xmllv2lDw1VBawNEdTZ9H5utKu04 Iv3JGLqLP/2g4wQC87ITWvkKwOCNhKROMuizmilqwclW+gsiOQ7cgYj5AOp5 t1gz =YJkP -----END PGP SIGNATURE----- On Mon, Apr 14, 2014 at 1:54 PM, Donald Stufft <don...@stufft.io> wrote: > > On Apr 14, 2014, at 1:51 PM, Adrian Holovaty <adr...@holovaty.com> wrote: > > Yesterday at PyCon, about a dozen people from the Django core team had a > lunch meeting to talk about various ideas we should implement. One idea was > to start doing a Django equivalent of Python's PEPs, which would serve as a > formal way to document large new features/changes in Django. > > The goal would be to have "design documents" in a single place, rather > than relying on parsing dozens of micro-decisions made in mailing list > threads, Trac tickets, etc. And, importantly, we would only use this for > medium-to-large features, so as not to introduce too much inertia. > > We also talked about doing it immediately, just using pull requests on > GitHub, to get some momentum going. No need to build any fancy systems, etc. > > Today at the sprints, I went ahead and started drafting how this would > work. Here is a new GitHub repo for DEPs (Django Enhancement Proposals): > > https://github.com/django/deps > > And here is DEP 1, a draft attempt to document how the process works: > > https://github.com/django/deps/blob/master/deps/0001.txt > > Note the "TODO: Next steps" at the bottom. I'm not exactly sure what the > best process would be once a DEP is formally created. Can somebody with > more familiarity with Python's PEP process provide some suggestions? > > Adrian > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CABm4ZCT1S1_ybYVe_0BGKvGAsQx3VDsD0KWZtBfR9fD6nOU7vQ%40mail.gmail.com<https://groups.google.com/d/msgid/django-developers/CABm4ZCT1S1_ybYVe_0BGKvGAsQx3VDsD0KWZtBfR9fD6nOU7vQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > Normally in the PEP process once you have a PEP you go through rounds of > discussion on the mailing list. The PEP is responsible for documenting the > solution the PEP suggests as well as any dissenting opinions. Once the PEP > author believes there is no more discussion to be had they ask for > pronouncement. This is where the BDFL or BDFL-Delegate (Guido doesn’t care > about everything, so he can appoint someone to decide in his place) reads > over the PEP and accepts it or rejects it. If it is accepted the status > changes from Draft to Accepted and it stays that way until it gets > implemented and committed. Then it changes from accepted to final and the > PEP process is done. > > One thing i’m not sure of, how is DEPs going to work without a BDFL? > Generally they are used to get feedback and provide a clear concise > argument to the BDFL in cases where there is not a good way to get a rough > consensus amongst python-dev. > > ----------------- > Donald Stufft > PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 > DCFA > > -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: 125F 5C67 DFE9 4084 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFRnB2V6SdnQ-9%3D_YAK9biV7q0TJnkXrjP0kNxtd_vC4nJHzbg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
