On Thu, 10 Sep 2009, Jim Grisanzio wrote: > OGB ... > We are finishing work on displaying the collective and user relationships on > the new site. We will deploy this functionality to auth.opensolaris.org in a > few of weeks. When this is done, all relationships will be displayed openly > on Auth, and all governance grant data will be entered directly into Auth. At > that point, Poll will simply be used for voting purposes, and we'll update > the app to prepare for the March election. > > From an implementation and process standpoint, the most efficient method to > get grant data entered into the system is to distribute the function among > the Community Group Facilitators. They already interact with the OGB > regarding their CG grants. Also, distributing this clerical task speeds the > process on their end, and it relieves the OGB secretary from having to enter > everyone's data across the entire community -- which at election time can be > a significant task under pressure from deadlines. A simple process could be > the following: CG Facilitators post to ogb-discuss their grant changes, the > OGB secretary responds with whatever OGB approval process is in place, then > the CG Facilitators enter the appropriate data into their CG Electorates in > Auth. The threads on ogb-discuss will serve as an open record of the board's > approval, and the public relationships screens on Auth will serve as > confirmation the data was entered correctly. This clearly separates > governance oversight from CG data entry, and it's the cleanest way to > implement the process on the back end in Auth.
Hi Jim - I like this idea of distribution, but am concerned about auditing. Unless some sort of notice (push NOT pull) is sent to the OGB interested parties (right now i believe that would be me & Deirdre), then how will we know if the facilitator skipped the step of posting to ogb-discuss before the grant was added? As you know, wer're currently concerned with only having grants added for people that are aware of their role in governance with a core contributor. I don't see a way to enforce this process with what you've described above. Valerie -- Valerie Fenwick, http://blogs.sun.com/bubbva/ @bubbva Solaris Security Technologies, Developer, Sun Microsystems, Inc. 17 Network Circle, Menlo Park, CA, 94025.
