🚀 go-pugleaf

John Whitehead writes:

> Judy Hallman writes:
> 
> >It seems to me that we want to post to rtpfreenet, ALL meeting
> >announcements, minutes of all meetings, and general information, and that
> >we want to encourage lots of discussion about details on the tf-tech,
> >tf-ops, tf-data, tf-fund, and tf-pub lists. It makes sense to me to
> >automatically forward ALL the postings to triangle.freenet. In which case
> >we would NOT want to forward from triangle.freenet to rtpfreenet.
> 
> I disagree.  I agree that all postings from rtpfreenet should go to
> triangle.freenet, but I also think that everything on triangle.freenet
> should go to rtpfreenet.  Otherwise the people on the mailing list will
> still have to keep up with the newsgroup, and people who prefer the
> newsgroup will not be heard by the mailing list-only people.  The whole
> point of this should be that they are the same thing, so anyone can
> choose which format they want to use without missing any info.
> 
> But the tf-* lists need not be gated to triangle.freenet.
> 

I agree 100% with John.  All posts to rtpfreenet and triangle.freenet
should be gatewayed both ways, so that posting to one will get it
automatically posted on the other.  Even more importantly, I think
it would be a crying shame to gateway the tf-* discussion lists to
triangle.freenet.  There is a palpable difference between the type
of discussion you can get from a small group of activists working
amongst themselves or in full public view.  We'll get a lot more
done without the various discussion participants having to worry about
what they're saying in a wide-area public forum.  Let triangle.freenet
(and rtpfreenet) be for public announcements, and let the tf-*
discussion lists be open to all sorts of creative musings.  After
all, anyone who wants to can sign up for those lists, too.

My $0.03 (after taxes).

            -- Mike Grubb
               <mg@acpub.duke.edu>