Currently only a small number of people have access to the internal OSAF repository file area but with a public facing feature we need to consider who inside OSAF will have access to the repository files. The can and will have private data on them so it needs to be a short-list.
I am creating a web area that will have an auth-list to control access but who should drive the contents of that list?
--- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "General" mailing list http://lists.osafoundation.org/mailman/listinfo/general
