Re: /usr/X11R6 process
Hi,
>>"Philip" == Philip Hands <phil@hands.com> writes:
Philip> I meant in the sense that it might be a good idea to have one
Philip> person that can tell one of the Policy Editors that they
Philip> should actually go ahead and edit the policy, once the agreed
Philip> policy decision process is complete.
I really think that we can handle this informally as in "Ok, I
have time, I shall do this". I do not think that we need a Person In
Authority to do this. A strictly peer relationship can work. No czar
should be installed until there is demonstrated need. In any case,
the proposerts or seconders can do the necessary prodding.
Philip> I'm not convinced that there is a desperate need for this,
Philip> but occasionally things fail to get done, simply because
Philip> nobody feels they have the authority to do it.
Any of the maintainers have the authority to edit agreed on
changes into the policy. Let us just say that we all agree to send
mail to the other vlunteers before we change anything.
Philip> If the default the default state is that one of the several
Philip> Policy Editors is assumed to take it on themselves to do the
Philip> CVS update, and that works, fine.
The default is that anyone who has time takes upon themselves
to do the updates. If everyone is busy, a) we need more volunteer
editors, and b) the proposers can nag people, c) the tech cmtt ca
nag, d) it is not the end of the world if the change has to wait a
couple of days ;-)
If this is a recurring problem, then indeed we need some one
to prod and nag and so on. I vote we let the tech committee do the
job.
Philip> BTW I still think there needs to be a Policy Team Leader,
Philip> just in order to make sure that individual changes get done
Philip> by one person, rather than none or several. I don't really
Philip> care who does it --- Manoj, do you want the job ?
I don't think we need a team leader. I think that we should
not institute bureaucracy until there is demonstrated need. See, we
have the policy repository all set up, and the packages being
injected into the repository, and we did not need a czar to whip us i
shape. One of us volunteered.
I guess the bottom line is that if you volunteer to be a
policy maintainer, you have committed to watching the -policy list
and incorporating changes agreed upon into the manuals. We should
only need one person, in an ideal situation. Since we have other
commitments, there is a four way redundancy (the only problem being
one of syncronization -- and I think it can be handled informally)
manoj
--
You can bear anything if it isn't your own fault. Katharine Fullerton
Gerould
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: