| PT: Review open Bugs Motion to close all these bugs, as we've agreed not to use bugs as a means of tracking agenda items. They're all either under discussion elsewhere, or no longer relevant. |
| ID | Sev | Pri | Summary
|
| 1937 | maj | P2 | OGB 2008/010 Simplifying the structure of the OpenSolaris Community
|
| 931 | min | P4 | OGB 2008/009 - Establish regular reports from Projects on their status
|
| 932 | min | P4 | OGB 2007/002 Community and Project Reorganisation
|
| 933 | min | P4 | OGB 2007/003: Communities with < 3 Core Contributors
|
| 1383 | nor | P4 | set of mailing list issues
|
| 1920 | min | P4 | OGB Directive to change "leader" to "editor" in web app
|
| 2186 | min | P4 | Make some useful SQL queries available for the grants
|
| 2246 | min | P4 | Create Emancipation Community Group
|
|
| PT: Cleanup of Policies Page | Motion that, if the bugs be all closed out, that the list of bugs be removed from the policies page [1] and that 2007/002 and 2007/003 be struck from the list of policies under discussion, as we aren't discussing them for future approval at all.
|
| PT: Reports at C1 | [2] Motion: that we invite collectives (community groups, projects, and user groups) to submit reports highlighting their recent achievements (over the last year). The reports to take the form of a single powerpoint slide (pictures are good), or text we can massage to that form. We will create a single amalgamated presentation and put each page on a display board at C1.
This would also lay the groundwork for regular community reports which we would seek to receive from all collectives on a regular basis in the future. (See OGB 2009/006)
|
| Initials: wiki link title | wiki link
|
| Date Added | Who | What
|
| 10 June, 2009 | Plocher/Simon | Charter update, preamble draft, next draft constitution iteration Talk:OGB_2008/010_OpenSolaris_Constitution_2009
|
| 10 June, 2009 | Plocher | Need a mechanism to alert members and facilitators when membership grants are due to expire. People shouldn't have to manually poll. Look into y!Pipe stuff to highlight, how to do more active alerts, maybe use facilitators project and monthly report of new/expiring/expired grants, maybe automate in cron?
|
| 13 May, 2009 | Plocher | draft best practices for mail man list moderation settings, draft a new policy related to list moderation (http://www.opensolaris.org/jive/thread.jspa?threadID=102430&tstart=0)
|
| 10 June, 2009 | Michelle | update website FAQ based on Plocher's best practices
|
| April 30, 2009 | Deirdré | twitter
|
| April 30, 2009 | Plocher | look into a way to turn on/off archival setting on pages for agenda.
- Wikipedia has "Protected" pages of several flavors. I'm checking with Al Hopper to see if Genunix has this feature. [5]
- Start with old agendas, move on to policies
|
| 17 March, 2010 | gat | Request for new information on new releases to be published on the opensolaris main sites.
Most major open source operating systems release apha, beta, and release candidate information to allow users to test the new release. Also, simply to let users interact with the production system. This is an important feature of non-(Apple,)Microsoft operating systems. I think that both opensolaris.org and opensolaris.com should both feature more of this type of information. When the month that the new release comes (after the extra month of being withheld) videos demonstrating how new the 2009.06 release is should not be seen on opensolaris.com. It just seems that attention is only given to the current release on the websites, with the exception of genunix.org. This seems odd because it is almost falsely advertising that the stuff that was new then hasn't been improved, nor new stuff added.
|
