Subject:
|
Re: Legends of Todd
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Fri, 22 Apr 2005 00:13:01 GMT
|
Viewed:
|
2488 times
|
| |
|
|
In lugnet.admin.general, Leonard Hoffman wrote:
> In lugnet.admin.general, Orion Pobursky wrote:
> > In lugnet.admin.general, Leonard Hoffman wrote:
> > > the Admins' basic idea of how the P&P process
> > > would work is essentially what you described here. We write it, work on it.
> > > Share it with a few people and get their input, get the document into a finished
> > > form and then share it with the public. This process was interupted before it
> > > was finished.
> >
> > I posted this already but this is not the impression that I got from the
> > announcement post or various other conversions with those involved. The
> > impression I got was that the committee was going to generate the P&P and then
> > it would be implemented without a general public discussion period. I think
> > this course of action would be a horrible mistake and only lead to further
> > division here on Lugnet.
>
> Isn't it possible for people to discuss something even if it is currently being
> implemented?
In my opinion, no, especially if the implementation directly affect those whould
would discuss it.
For example:
The club you belong to forms a committee to review the dress code. It just so
happens (by coincidenece) that everyone on the committe hates baseball caps so
they make wearing them a bannable offense. You like to wear baseball caps; in
fact, you have a whole collection at home. Now you are face with either abiding
by the unfair baseball cap ban while arguing with the committee, wearing
baseball caps in protest and being kicked out or, leaving the club voluntarily.
The outcome of any of these decisions is negative.
> Or is it the point that something should be submitted to the community before
> implementation just for the sake of it? In which case, does the Administration
> need the community's approval after submitting it, before implementing it?
The flip side of my above example is this:
The committee forms the draft rules since it's easier to start with a small
group. They then submit it to the general membership for review before it is
implemented. You speak up and say that you like baseball caps and a significant
number of other members support you. The committee realizes thier short
sightedness and changes the draft. Once the public review process is over and
all suggestions and discussions are considered, the committee implements the new
dress code. Not everyone is completely satisifed with the new policy but most
everyone are comfortable with it.
Note that the committee still has the deciding power but now public input is
used to mold the policy into something most can agree on. This method has
worked to great success with the LDraw.org policies so I don't know why it can't
be applied here.
|
|
Message has 1 Reply:
 | | Re: Legends of Todd
|
| (...) To me, "abiding by the unfair ban while arguing with the committee" is a worthwhile thing to do. Since, this might happen even if the policy is submitted to the membership. TO use your example - what if you are gone on the day the ban is (...) (19 years ago, 22-Apr-05, to lugnet.admin.general)
|
Message is in Reply To:
| | Re: Legends of Todd
|
| (...) Isn't it possible for people to discuss something even if it is currently being implemented? Or is it the point that something should be submitted to the community before implementation just for the sake of it? In which case, does the (...) (19 years ago, 21-Apr-05, to lugnet.admin.general)
|
90 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
