On 29 Aug 2008, at 21:04, Jeffrey Hutzelman wrote:
OK, then. Now let's see if we can agree on some text. I'll propose the following as a replacement for the next-to-last paragraph of 2.3.2:This combination of roles makes it difficult for a single individual to serve as registrar. Instead, it is proposed to expand the role of registrar to include a number of individuals from the community. This group would initially be composed as described in section 3. Once established, the registrars set their own procedures for adding new registrars, removing registrars, and determining the size of the group. In the event there are no registrars, a new group will be formed consisting of one representative from each active AFS implementation and one representative chosen by the chairs.I would also add the following sentence to the last paragraph of 2.3.2:The registrars must make the current set of registries available to the community, including versions in the preferred source form.
I'm happy to adopt these. In an ideal world, I'd like to keep the bootstrapping details separate from the core document - so I'd prefer to delete the final sentence of your first paragraph, if that's acceptable, and remove "Once established" from the first sentence of the second.
Simon. _______________________________________________ AFS3-standardization mailing list [email protected] http://michigan-openafs-lists.central.org/mailman/listinfo/afs3-standardization
