On Apr 4, 2009, at 22:38, Peter Tribble wrote:

> These are the open governance bugs in bugzilla. I've appended my  
> comments.
>
> 931           min     P4      NEW             OGB 2008/009 - Establish 
> regular reports
> from Projects on their status
>
> I think we ought to pick this up and drive it forward. I would  
> expect some
> sort of report from all collectives (projects, user groups, and  
> communities).
> At least annually, if not quarterly.Operationally, we could tie it  
> in to the
> newsletter, but it should be something that every collective should do
> anyway and shouldn't be a huge bureaucratic effort.
>
> (Implementation suggestion: simply create a mailing list. Reports  
> may be
> "The foo user group met 3 times in the last quarter", "The bar project
> released a new version of the code", "The baz community group created
> two new projects fred and joe". We want bullet points, not the  
> complete
> works of Shakespeare.)

This idea followed the example of Apache, where each top-level project  
writes regular reports to the Board giving details of their progress  
since the last report. I agree with the level of detail you propose,  
and suggest that we create a reporting calendar so that there is a  
fresh project report every meeting. This report could then form the  
basis of the feature spots the website community produces.


>
>
> 932   min     P4      NEW             OGB 2007/002 Community and Project 
> Reorganisation
>
> My own feeling is that this should be dropped. I don't want to see  
> the OGB
> dictatiting the structure of the community. Rather, it should evolve  
> naturally.
> (That's not to say that the OGB shouldn't guide and encourage  
> communities
> and projects, and should point out where synergies and gaps exist that
> individual collectives may have missed, but we shouldn't be telling  
> the
> community how to fracture itself.)

I think this one has actually been superseded by the new Constitution  
and should be dropped on that basis. Also the next one as well, as you  
say.

>
>
> 933   min     P4      NEW             OGB 2007/003: Communities with < 3 Core 
>  
> Contributors
>
> We should wait for constitutional reform.
>
> 1383  nor     P4      NEW             set of mailing list issues
>
> Close. If there are individual issues then open new bugs, although  
> they
> don't look like governance to me.
>
> 1920  min     P4      NEW             OGB Directive to change "leader" to 
> "editor" in  
> web app
>
> Hm. An OGB directive. Does the new infrastructure follow this  
> directive?
> If so, there's no problem.
>
> 1937  maj     P2      NEW             OGB 2008/010 Simplifying the structure 
> of the
> OpenSolaris Community
>
> I *think* that this is the new constitution. Given that it failed, we
> should probably create a new bug to track future work. Although
> John Plocher's comments follow 2007/002. Is there anything else
> bundled in this that we need to track?

This preceded work on the new Constitution and should be closed on the  
basis we will be reviewing and proposing a slightly modified version  
of that some time this year.

>
>
> 2186  min     P4      NEW             Make some useful SQL queries available 
> for the  
> grants
>
> Is there any reason this is still open?
>
> 2246  min     P4      NEW             Create Emancipation Community Group
>
> What's the status here? As far as I can tell from the website  
> Emancipation
> is still a project.

Again, the distinction will not be relevant under the new Constitution  
so I suggest this one be closed as well.

S.


Reply via email to