🚀 go-pugleaf

hey Rob.... rather than simply supply a list of policy proposal changes, how 
about some background as to who you are in relationship to such a form of 
control, why you think such proposals are necessary and some description of an 
infrastructure including moderators that can enforce such policies (including 
who's paying for it and their time)..... and finally, why not simply create a 
newsgroup that can provide for some of the emergency-related announcements 
you've cited.... what's the point of attempting to control a chaotic system 
when, in my view, should remain chaotic... no harm is done by its chaos.... in 
fact, it provides a very real model for anyone studying interpersonal dynamics 
to be able to glean some relevant insights into social phenomena.


"Rob Maxwell" <bc_van_usenet@fastmail.ca> wrote in message 
news:122sge39pjabuae@news.supernews.com...
>
> Newsgroup Control Policy for bc.* and van.* hierarchies.
>
> 1. Proposals for new bc/van groups or removal of same should be submitted to:
> bc_van_usenet@fastmail.ca.
>
> 2. After any needed editing, the proposal will be posted to bc.config.
>
> 3. These proposals will be posted to bc.admin.announce, a newsgroup that will 
> not accept submissions or posts, which will serve as a place to post all 
> administrative-related posts including proposals, ballots, vote results, and 
> announcement of creation or removal of newsgroups.
>
> 4. After the posting of the proposal, there will be a ten-day discussion 
> period.
>
> 4a. If there are significant changes, a new proposal will need to be 
> submitted.
>
> 5. If there are no significant changes, a ten-day voting period will occur.
>
> 6. Any proposed newsgroup that receives 50% or more of the votes in favor of 
> its creation from a minimum of ten different voters will be made within five 
> days of the end of the vote barring any significant objection to the voting 
> results.
>
> 7. Removal of bc or van newsgroups shall follow the above procedure except 
> that two-thirds of the voters must approve removal and the newsgroup shall not 
> have more than an average of three posts per day over a thirty-day period (a 
> total of 90 posts).
>
> 8. Only one newsgroup may be included in a proposal to create or remove.
>
> 9. Final decision on the name and description of proposed new newsgroups shall 
> be of the Administrator.
>
> 10. Exceptions to the above:
>
> a) Administrative newsgroups shall be made or removed at the discretion of the 
> Administrator.
>
> b) Attempts to circumvent the above procedures will result in a reversal 
> action being taken as needed.
>
> c) Patently offensive proposals; groups that serve to promote or embarrass 
> individuals, websites, companies, products, or other entities; topics of a 
> clearly national or global interest; or other potential troublesome
> newsgroups will be ignored.
>
> d) In the event of a major newsworthy occurrence in the Greater Vancouver 
> and/or British Columbian region along the order of the attack upon the World 
> Trade Center on 11 September 2001, the Administrator shall create a bc or van 
> newsgroup that shall include "current-event" in the name at their discretion 
> and remove same at a later date. This creation or removal of a "current-event" 
> shall bypass the discussion/voting procedure outlined above.
>
> 11) Policy changes will be made as needed to adapt to prevailing conditions in 
> the bc.* hierarchy, van.* hierarchy, Usenet (in the greater NetNews sense), 
> the nntp protocol, or current News Administration practices at the discretion 
> of the Administrator.
>
> -END-
>
> -- 
> Rob Maxwell
> Administrator
> bc and van hierarchies
>
>