[cab-discuss] test questions to test OGB election process (presented as a poll)

Roy T. Fielding fielding at gbiv.com
Wed Feb 21 14:48:56 PST 2007


I think the questions need to be shortened to 50 characters or so,
depending on how the ballot is constructed.  Also, they need to
be phrased to match the lead-in of "prioritize the following" by
starting with a verb.

And they should not contain subjective comments on solutions.

> OpenSolaris Test Vote/Poll:  Question:  Which of the following items,
> presented in a randomized order, should be prioritized by the OGB  
> in order
> to promote OpenSolaris and increase its developer mindshare:
>
> - provide a highly usable Defect Management System which allows a
> OpenSolaris contributor to perform queries, enter or update  
> records, and
> "own" bugs

   a. deploy a public defect management system

> - prioritize the rollout of the Mercurial Source Control Management  
> system

   b. deploy Mercurial source control across all projects

> - provide new guidelines for the formation of Communities and Projects

   c. enforce guidelines for Community and Project formation

> - examine the OpenSolaris CDDL and ascertain if it still meets the  
> needs
> of the OpenSolaris community

   d. analyze and comment on the next draft of GPLv3
   e. reinvestigate the choice of licenses for OpenSolaris products

> - re-assess the current Community/Project organization
> - develop a process to remove inactive Communities or Projects

   f. reorganize the existing Community/Project organization
   g. remove inactive Communities or Projects

> - provide a (fast) SPARC based kernel/project community build facility
> - provide a (fast) x86/AMD64 based kernel/project community build  
> facility

   h. provide a test build facility for SPARC architecture
   i. provide a test build facility for x86 architecture

> - elect a new OGB before the end of March 2007

That question is irrelevant.

> - launch a membership drive

I have no idea what that means.

> - evaluate if mailman/jive should be upgraded or replaced

   j. replace or remove jive interface
   k. replace or remove mailman interface

> - open source the OpenSolaris website application

Also irrelevant -- that is a decision already made by Sun.

> - increase community participation in the day-to-day running of the
> OpenSolaris infrastructure

   l. create an infrastructure project to run opensolaris.org

> - provide support on OpenSolaris.Org for submitting, managing and  
> tracking
> RTIs (Request To Integrate)

   m. deploy a public Request To Integrate (RTI) system

> - provide an OpenSolaris code review facility (to replace  
> cr.grommit.com)

   n. deploy a public code review facility on opensolaris.org

> - provide an OpenSolaris wiki

   o. deploy a public wiki on opensolaris.org

> - provide a community test facility (SPARC and x86/AMD64)

duplicate

> - expend more resources to minimize/eliminate spam

we don't control those resources

> - fix the reliability issues with (disappearing) web pages

duplicate of other questions regarding jive software

> - support OpenGrok indexing of projects with per-project indexing and
> searching

   p. deploy OpenGrok indexing of projects

> - improve tools used to author/edit OpenSolaris.Org web pages

   q. replace opensolaris.org tools with an open source CMS or wiki

> - establish a mechanism to provide regular idea interchange and
> consultation between the OGB and Sun executive management

   r. establish regular communication with Sun executive management

The list is still way too long -- any more than 12 questions is
just testing the endurance of the reader, not their priorities.
I suggest we reduce it to:

   a. deploy a public defect management system
   b. deploy Mercurial source control across all projects
   d. analyze and comment on the next draft of GPLv3
   f. reorganize the existing Community/Project organization
   h. provide a test build facility
   j. replace or remove jive interface
   k. replace or remove mailman interface
   l. create an infrastructure project to run opensolaris.org
   m. deploy a public Request To Integrate (RTI) system
   n. deploy a public code review facility on opensolaris.org
   o. deploy a public wiki on opensolaris.org
   q. replace opensolaris.org tools with an open source CMS or wiki

....Roy




More information about the cab-discuss mailing list