[Python-ideas] Personal views/filters (summaries) for discussions

[anatoly techtonik]

On Sun, Apr 28, 2013 at 9:43 PM, Terry Jan Reedy <tjreedy at udel.edu> wrote:

> On 4/28/2013 11:37 AM, anatoly techtonik wrote:
>
>> I find it really hard to track proposals, ideas and various deviations
>> in mailing lists, which is especially actual for lists such as
>> python-ideas. I bet other people experience this problem too. The
>> typical scenario:
>>
>> 1. You make a proposal
>> 2. The discussion continues
>> 3. Part of the discussion is hijacked
>> 4. Another part brings the problem you haven't seen
>> 5. You don't have time to investigate the problem
>> 6. Discussion continues
>> 7. Thread quickly gets out of scope of daily emails
>> 8. Contact lost
>>
>> Several week later you remember about the proposal:
>>
>> 9. You open the original proposal to notice a small novel
>> 10. You start to reread
>> 11. Got confused
>> 13. Recall the details
>> 14, Find a way out from irrelevant deviation
>> 15. Encounter the problem
>> 16. Spend what is left to investigate the problem
>> 17. Run out of time
>>
>> The major problem I have is steps 9-15. Sometimes these take the most of
>> the time. What would help to make all the collaboration here more
>> productive are colored view/filters (summaries) for discussions. It
>> would work like so:
>>
>> 00. The discussion is laid out as a single page
>>
>
> This is what the PEP process is about. Anyone can summarize a idea as a
> proto-pep either initially or after preliminary discussion. Objections and
> unresolved issues are part of a pep. Revisions and reposting are part of
> the process.


I thought about writing PEPs, but my CPU cycles and Memory are too limited
to support current PEP process. I'd be happy to run a Stackless version of
it, which can be paralleled, suspended or resumed on a different humanware.
-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20130501/ccb23527/attachment.html>