-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Jeff,
Well, Evan is certainly a member of the community. I don't think he meant to step on any toes. I intended to suggest only what Derrick's comments summarized, not new mechanisms to submit architecture proposals, so I'll leave it there. An new mechanism I'd benefit from would be scheduled openafs conference developer meetings between hackathons. I think that would help us make more steady progress on tasks like libosi integration. That certainly doesn't require a TAC, but it would probably require a bit of time commitment from some subset of active developers to be useful. Matt Jeffrey Altman 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 - -- Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 http://linuxbox.com tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJEw7LJiSUUSaRdSURCI3GAJ9GaQ98em7tWF5K1V/YnrXVcL9UVQCgg5/V mxXm+P9gNDmQ9y3yb6Mec9c= =wRsJ -----END PGP SIGNATURE----- _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
