Peter Tribble wrote: > Looking at the current policies, as listed on the web page: > > http://www.opensolaris.org/os/community/ogb/policies/ > > These need to be reviewed to see if they still apply (some are explicitly for > a > particular year, 2008); for those still active we should consider whether to > (a) keep unchanged, (b) rescind, (c) modify. > > I've listed each one, followed by my own comments. > > * OGB 2007/001 Project Instantiation Policy Approved on April 25th, 2007 > > For as long as we're operating under the current constitution, this > policy is good. > Insofar as there's the potential for major reform to simplify the > whole process, major > effort to revise the policy seems unwarranted. (The only things I will > note are the naming > of a specific individual [Eric] as project herald, and the statement > on 4.1 that there's a > project naming policy.) >
I agree with your comments on this policy above. Eric is no longer Project Herald (I believe Jim Grisanzio fills this role today). So, the implementation notes should be updated to reflect the Project Herald change and we should ask Jim if there is a naming policy currently in use. > * OGB 2008/001 Statement of the OGB class of 2008's "can-do" > attitude and approach to governance > > Specific to 2008, and was incorporated into the new constitution. > I think we should rescind this policy and draft a new set of priorities for the board that is focused more on a explicit statement of what we will do, not 'how' it gets done. My very first draft of such a mission statement is as follows: Our mission is to enable OpenSolaris contributors to participate more independently, track and manage the bugs they file and fix more efficiently, access and contribute the software they need more readily, document their projects more effectively and provide a place to ask questions and promote their contributions. > * OGB 2008/002 OGB Policy pertaining to the Constitution > > Needs further thought in the light of any plans we may make to deal > with constitutional > reform. > Agreed. My initial thinking is to modify this policy as follows: OGB Policy pertaining to the Constitution -Seek to work within the existing Constitution wherever possible. -In cases where there is an apparent obstacle, draft and submit a Constitutional Amendment to the next Annual Meeting. ** > * OGB 2008/003 Enabling email-based decision making > > I think we continue with this. > Agreed. > * OGB 2008/004 Proposal on the logistics of Regular meetings of the OGB > > Needs revision. Clearly, the day and time aren't right. Agreed, I've updated this policy and associated OGB pages with the current day and time. > The > requirement for audio > recordings needs consideration. And the agenda handling needs work > (see next policy). > Agreed, I propose the following rewrite: Any OpenSolaris Member may submit items for the agenda between meetings by adding it to the genunix wiki page for the associated meeting, by request to any OGB member, by posting an agenda item request to ogb-discuss, or by request at the beginning of any OGB concall. > * OGB 2008/005 Proposal on OGB activity/issue naming, tracking and > archival > > Need a new policy for 2009, as this one is explicitly for 2008. First > question: do we > continue to use bugzilla as the primary source? I propose that we rescind this policy and continue to use the wiki agenda to structure our concall. > If so, then we can > probably take this > policy as is. If not, we need to start over. The advantage of bugzilla > is that it essentially > autogenerates the agenda for us. The use of bugzilla seemed to drop > off - for example, > this year we didn't have bugs raised for election candidates that I'm aware > of. > I used the ogb category in bugzilla to file all the grant renewals because they happened on so many different lists and warranted use of a tracking system because I didn't want to make a mistake and needed a clear record of grant requests and the dates I added them (in case I did make a mistake, which I did). But, I didn't need bugzilla to manage the agenda and AIs. > * OGB 2008/006 Proposal on the use of the OGB-Discuss alias > > I think it's good. > Agreed, with the exception I raised earlier this week related to 'always trimming unneeded quoted text form your responses' because 'unneeded' is too subjective. Particularly in the case where feedback is explicitly requested on a new discussion and that feedback gets trimmed not because it is unneeded, but because it is unpopular or controversial. I propose we strike that bullet in the 'general list karma' section and keep the rest. > * OGB 2008/007 Proposal on the use of the OGB-Private alias > > Close. One thing that's missing is what we've actually used the > private list for so > far, namely things like dissemination of personal details or operational > details > that must be restricted to the members of the OGB. > Agreed, I've added your text about personal details to the policy as a proposal. > * OGB 2008/008 Proposal on Website Community and Web Editorial Board > > Looks very stale. Do we simply live with it until the new > infrastructure launches? > We'll need a new policy at that point. Or do we write a revised policy now? > I've updated this policy with the results, as follows: Web community with up-to-date grants on file with the OGB secretary: http://opensolaris.org/os/community/web/ Editorial policy and review process: http://www.opensolaris.org/os/project/website/content/plan/ Infrastructure roadmap: http://www.opensolaris.org/os/about/roadmap/ > * OGB 2007/002 Proposal on Community and Project Reorganisation > * OGB 2007/003 Proposal on Communities with < 3 Core Contributors > See also: BugZilla OGB issues > > Those 2 proposals are in bugzilla, so I'll construct a similar list > for the bugzilla > issues (unless someone else gets in first). > Excellent, thank you Peter, much appreciated! -Michelle
