On Apr 3, 2009, at 21:50, Michelle Olson wrote: > Peter Tribble wrote: >> Looking at the current policies, as listed on the web page:
Thanks for getting us started, Peter, nice work. >> * 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. Since we're almost all agreed that we should replace the constitution in its entirety with the new one, I suggest we leave this untouched until we have the new constitution in place, and then adopt suitable wording like this reflecting our then-current intent. It is /not/ our current intent to make amendments to the constitution currently in force but rather to craft a new one based largely on the current draft. > >> 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. One thing we need to watch with care is that it is /not/ appropriate to introduce new items at the start of the meeting and then immediately discuss them, nor is it usually appropriate to introduce completely new work that has no supporting materials and/or discussion on an agenda. So while your wording reflects submission of items, it does not reflect their socialisation or scheduling. That was the reason for the proposed use of a tracking system. Once tracked, agenda items of any weight should be discussed on-list or in other meetings, the facts and proposals summarised and then the considered package brought to the OGB. This allows several work items to be conducted in parallel. We can do this on the agenda wiki if it's what works for people; we can have a "future business" section (rather than an "if there's time" section) and link it to the wiki pages where the work is in progress. However, it seems messy to cut-and-paste that list into a new agenda every week, so I suggest the list of future agenda items be maintained as a free-standing wiki page, and that the bi-weekly agenda list only the matters scheduled for discussion because they are "cooked enough". I thus propose the following text for this policy: Any OpenSolaris Member may submit items for future agendas between meetings by adding it to the genunix wiki page for future agenda items, 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 Members may add any item on the "future agenda items" list to the agenda template for the next meeting at any time before the meeting commences (or: at any time up to 12 hours before the meeting commences). >> * 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. I disagree. Trimming redundant text is well-recognised best practice and failure to do so leads to cumbersome, unreadable messages. S.
