[Theforum] policy for #evolt

Marlene Bruce marlene at members.evolt.org
Thu Jan 10 08:30:34 CST 2002


At 12:17 PM +0000 1/10/02, Garrett Coakley wrote:
><http://www.irchelp.org/irchelp/faq.html>
><http://www.openprojects.net/catalysts.shtml>

This is an interesting page. Since OPN doesn't yet have a catalyst 
training program, I think everyone joining IRC should try to act as a 
positive catalyst for the channel (if this were an ideal world). IOW, 
perhaps we should encourage everyone joining #evolt to read this page.

><http://www.openprojects.net/channel_guidelines.shtml>
>Can I also raise the point that it's all very well and good saying "do we
>want it to be more like evolt.org or IRC?", but while it's been hosted by
>an outside party (openprojects.net) then you won't have a great deal of
>leeway in the matter.

Are you sure? It states on this page that the guidelines offered are 
optional. Still, they're good community guides. The concept of 
"channel temperature" is interesting, and it seems to be a similar 
problem we're having on some of evolt's email lists.

However, the problem that recently arose with #evolt was the booting 
of someone for lurking. About halfway down the page on 
http://www.irchelp.org/irchelp/altircfaq.html, it states, "Channel 
operators are kings/queens of their channel. This means they can kick 
you out of their channel for no reason. If you don't like this, you 
can start your own channel and become a channel operator there."

In my opinion, this shouldn't apply to #evolt. To me, it goes against 
the spirit that we're trying to foster through evolt. For example, on 
any of the evolt lists a person can lurk indefinitely without being 
unsubscribed. If we want to be consistent, a person should be able to 
lurk on #evolt indefinitely without being booted off. So IMO this 
particular rule shouldn't be included in the #evolt policy (at least 
not as written and intended above).

Still, some people here who are used to IRC being run a certain way 
will undoubtedly disagree with my opinion. What I'm looking for is 
for people to state their preference, including somehow:

a) why the rule would be useful (this may seem obvious, but please 
state why anyway)
b) that the rule mirrors existing attitudes in other evolt 
communication venues, or
c) conversely, why the rule should diverge from current practices 
elsewhere on evolt.

Most of all I'd like to encourage any discussion on setting up an 
#evolt policy remain as ego-less as possible.

Just reviewed some of the discussion on bots previously on this list. 
What a headache! Was there ever a consensus out of your IRC vote, 
Martin?

If there wasn't, maybe we shouldn't have an official #evolt channel. 
Maybe I'm wasting my time on something that we shouldn't "officially" 
associate with evolt. After all, after reading some more of the FAQ, 
it seems anyone can take the #evolt channel if they catch it at the 
right time. Unless there's a way to control that with certainty, this 
all seems to be a moot point.

What's the point of #evolt on top of everything else we offer our 
members? Do we really see it adding enough value to make all this 
discussion worthwhile? I don't want to waste any more of my time or 
yours if it's unnecessary.

Thanks,
Marlene




More information about the theforum mailing list
https://lists.evolt.org/pipermail/theforum/Week-of-Mon-20020107/002463.html
lists.evolt.org
crawl=CC-MAIN-2019-09
7457
application/http; msgtype=response
sha1:MKS7DOUZWBBJQ7GMRYEKZV6JG3N7TETG
<urn:uuid:63ef6f2c-0cf6-42b4-b522-7e9ff21c660a>
2019-02-18T18:22:20Z
198.199.71.69
text/html
sha1:7FX22JUNG563XWXPS5RL4B5JFFOUUB7J
<urn:uuid:ac91a24a-fa33-466b-a56b-32b783745597>
https://lists.evolt.org/pipermail/theforum/Week-of-Mon-20020107/002463.html
response
<urn:uuid:e47dced4-f17f-4596-937f-64ea2be613ce>
isPartOf: CC-MAIN-2019-09
publisher: Common Crawl
description: Wide crawl of the web for February 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-69-73-156.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/