On Tue, Nov 6, 2012 at 5:40 PM, Brian Harring <ferri...@gmail.com> wrote: > On Tue, Nov 06, 2012 at 12:31:07PM -0500, Mike Gilbert wrote: >> On Mon, Nov 5, 2012 at 7:48 PM, Brian Harring <ferri...@gmail.com> wrote: >> > Either way, I'm honestly not trying to piss folks off here nor stop >> > the efforts to dig us out of the python.eclass mess. That said, *this >> > time around* that eclass should actually have a plan so that we don't >> > wind up in the same cluster fuck scenario as prior. >> > >> > It's a simple enough request; document your roadmap. Asking for >> > reviews w/out that, frankly, is pointless (and sooner or later some >> > asswipe like me is going to start -1'ing things till that's >> > addressed). >> > >> >> If anyone wants to help in drafting a GLEP, I would appreciate it. >> I'll try to start that this week. >> >> There will definitely be some holes, since I really don't have an all >> encompassing plan in my head. But it will be good to fill those in. > > Holes in the glep can be sorted/fleshed out; trust me, way more > preferable sorting it there then in a live implementation the tree > relies upon. :) >
Sorry to do this, but I don't think I'm ever going to get around to writing a glep. However, I'm happy to assist someone else.
