develooper Front page | perl.bootstrap | Postings from July 2000

Re: Voting/Decision making guidelines

Thread Previous | Thread Next
Chris Nandor
July 25, 2000 09:48
Re: Voting/Decision making guidelines
Message ID:
At 17:33 +0100 2000.07.25, Tim Bunce wrote:
>On Tue, Jul 25, 2000 at 10:57:34AM -0400, Dan Sugalski wrote:
>> At 10:44 AM 7/25/00 -0400, Chris Nandor wrote:
>> >At 14:42 +0100 2000.07.25, Hugo wrote:
>> > >people realising it before it is too late. I think this is one thing
>> > >that the voting may have been intended to address - "hey folks, this
>> > >may be the _last_ chance to make your views known" - but I think it
>> > >is probably not the best way. If the RFC approach is done right, I
>> > >think it can solve this problem: for that, I think a) there needs to
>> > >be a way to say 'notify me when the RFC text changes', and b) the text
>> > >of the RFC needs to be updated (among other occasions) when consensus
>> > >starts to emerge but before any final decision is taken.
>> >
>> >Excellent ideas.  That way people don't have to monitor mailing lists just
>> >so they can keep an eye out for when something that they know interests
>> >them is going to come along.
>> In which case it might be useful to have some means of automatic
>> notification when an RFPC (or one of its children) changes. A mutant
>> mailing list, or website signup thing or something.
>Perforce can do that automatically. Maybe cvs/sourceforge can as well.

Aha, this is what I was hoping for.  SourceForge can't AFAIK, though there
are probably add-ons to CVS that can.  But in any event, yes, this would be
Cool.  Probably have special (read-only) mailing lists for each document or
group of documents, and updates for that document go to the mailing list,
making subscribing and unsubscribing simple.

Chris Nandor       |      |
Andover.Net        | |

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About