Jeff, Absolutely and understood. I wasn't talking about replacing anything already in place or the community! I was simply supporting moving the TAC from "idea" to "implementation."
It is my understanding the questions and architecture issues are already in discussion and being written up as the current process recommends. Evan -- Evan D. Macbeth - Director Sine Nomine Associates [EMAIL PROTECTED] (O): 703-723-6673 - (M): 443-421-0343 On 11/6/08 9:07 AM, "Jeffrey Altman" <[EMAIL PROTECTED]> wrote: > Speaking as a gatekeeper: > > If there are AFS3 protocol changes that you or your colleagues would > like to propose, write them up in the form of an Internet Draft and > submit them to AFS3 Standardization. > > If there are architectural changes you would like to propose for > the OpenAFS code base, write up an architectural design document > and send it to [EMAIL PROTECTED] so that the community > can discuss it and the gatekeepers can provide feedback. > > The technical advisory council will be a subset of the community > that will speak for the community. However, it will never replace > the community. Until it exists, I recommend using the mechanisms > that are already in place. > > Jeffrey Altman _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
