Hi gang,
it's puzzled me how much effort some of us have been putting in /normative/ documentation of policy, process, roles and responsibilities. It must be a programmer thing :D
It's what IMHO our "clients" asked us for. They want to know what bounds they have to work in, and we clearly need unique terminology.
I also want to make sure that we well know where things stand in every incubation moment, as there has been enough confusion withdouble-triple PMC concurrent votes.
That said, I also think that we need *one* document to guide us, and all the rest should be simply docs that complement it as HOWTOs.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
------------------------------------------------------------------------------------------------------------------------------------------ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
