|
Replies:
11
-
Last Post:
Feb 23, 2007 7:41 AM
by: richlowe
|
Threads:
[
Previous
|
Next
]
|
|
Posts:
802
From:
Plano, TX
Registered:
4/27/05
|
|
|
|
test questions to test OGB election process
(presented as a poll)
Posted:
Feb 20, 2007 10:37 AM
|
|
Wise people [1] decided that it would make a lot of sense to run a test of
the new OpenSolaris voting facilities before using it for the first time
to elect a new OpenSolaris Governing Board (OGB). We [2] could just
present a list of "silly" questions and ask the community members
interested in testing the system to vote and then present the resulting
sillyness. But then .. what if we devised a somewhat useful list of
questions and presented them to the community as a test of the new voting
software? Hmm.. perhaps, instead of a list of silly questions, why not
formulate a list that looks like a poll and present it for "voting".
Perhaps this would interest a larger pool of "testers" and allow them to
evaluate the results produced by the SVT based, voting system.
OK - with that decided and Stephen Hahn volunteering to run it, the next
challenge is to formulate a reasonable poll and present it to the
community. Since the main goal of this exercise is to test the voting
system, and since we are on a short timeline to elect the new OGB, it was
felt that a poll could be formulated quickly [3] - with the disadvantage
of not providing much time for community review. In a *real*
community-wide poll - more time would be required to formulate the poll
and, doubtless, the poll and the resulting data would be more usefull to
everyone. But again .... this is just a test! The community is
encouraged to provide feedback on the poll content before its presented -
but the final content will be decided (quickly) by the OGB and run in
order to allow the election process to proceed expediciously.
Instructions to test voters: Please examine the following list of test
poll questions and vote on them in *priority* order. Remember that the
voting software implements the Single Transferable Vote [4] using the Meek
algorithm [5] and that you don't have to vote on every item presented.
The priority order of your selection is very important. Please review the
STV system before voting if you are unfamiliar with it.
------------
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
- prioritize the rollout of the Mercurial Source Control Management system
- provide new guidelines for the formation of Communities and Projects
- examine the OpenSolaris CDDL and ascertain if it still meets the needs
of the OpenSolaris community
- re-assess the current Community/Project organization
- provide a (fast) SPARC based kernel/project community build facility
- provide a (fast) x86/AMD64 based kernel/project community build facility
- elect a new OGB before the end of March 2007
- develop a process to remove inactive Communities or Projects
- launch a membership drive
- evaluate if mailman/jive should be upgraded or replaced
- open source the OpenSolaris website application
- increase community participation in the day-to-day running of the
OpenSolaris infrastructure
- provide support on OpenSolaris.Org for submitting, managing and tracking
RTIs (Request To Integrate)
- provide an OpenSolaris code review facility (to replace cr.grommit.com)
- provide an OpenSolaris wiki
- provide a community test facility (SPARC and x86/AMD64)
- expend more resources to minimize/eliminate spam
- fix the reliability issues with (disappearing) web pages
- support OpenGrok indexing of projects with per-project indexing and
searching
- improve tools used to author/edit OpenSolaris.Org web pages
- establish a mechanism to provide regular idea interchange and
consultation between the OGB and Sun executive management
---------------
[1] See cab-discuss list for details
[2] as in the OGB in conjunction with Stephen Hahn - the owner of this new
voting system.
[3] NB: the initial set of poll test questions were developed with the kind
participation of small group of individuals
[4] STV see http://en.wikipedia.org/wiki/Single_Transferable_Vote
[5] Meek algorithm see http://sourceforge.net/projects/votesystem/
Regards,
Al Hopper Logical Approach Inc, Plano, TX. al@logical-approach.com
Voice: 972.379.2133 Fax: 972.379.2134 Timezone: US CDT
OpenSolaris.Org Community Advisory Board (CAB) Member - Apr 2005
OpenSolaris Governing Board (OGB) Member - Feb 2006
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
Posts:
3,657
From:
DE
Registered:
6/16/05
|
|
|
|
Re: test questions to test OGB election
process(presented as a poll)
Posted:
Feb 21, 2007 1:08 PM
in response to: alhopper
|
|
Al Hopper wrote:
[snip]
> - establish a mechanism to provide regular idea interchange and
> consultation between the OGB and Sun executive management
- Provide a project-specific bugzilla (for example via moving
bugs.grommit.com to something like project-bugs.opensolaris.org)
- Get the JIve messaging system either replaced or fixed to handle
emails correctly
- Enhance the webpage engine at opensolaris.org to use a Subversion
repository as backend storage with diret access for project leads
- Enhance the webpage engine at opensolaris.org to support DocBook/XML
(maybe even as replacement for the xx@@@!!!-"TML" stuff (which is IMO
very frustrating))
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland dot mainz at nrubsig dot org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
Posts:
142
From:
Newport Beach, California
Registered:
4/27/05
|
|
|
|
Re: test questions to test OGB election process
(presented as a poll)
Posted:
Feb 21, 2007 2:48 PM
in response to: alhopper
|
|
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
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,901
From:
NZ
Registered:
6/16/05
|
|
|
|
Re: test questions to test OGB election process
(presented as a poll)
Posted:
Feb 21, 2007 2:55 PM
in response to: fielding
|
|
Hi,
Roy T. Fielding wrote:
> 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 it might actually be fun asking the current OGB candidates for their views
on some of these issues as part of the campaigning period ;)
Glynn
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
Posts:
802
From:
Plano, TX
Registered:
4/27/05
|
|
|
|
Re: test questions to test OGB election process
(presented as a poll)
Posted:
Feb 21, 2007 6:02 PM
in response to: gman
|
|
On Thu, 22 Feb 2007, Glynn Foster wrote:
> Hi,
>
> Roy T. Fielding wrote:
> > 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 it might actually be fun asking the current OGB candidates for their views
> on some of these issues as part of the campaigning period ;)
Agreed. But anything that gets the community thinking about how we can
increase developer mindshare is a Good Thing IMHO.
Regards,
Al Hopper Logical Approach Inc, Plano, TX. al@logical-approach.com
Voice: 972.379.2133 Fax: 972.379.2134 Timezone: US CDT
OpenSolaris.Org Community Advisory Board (CAB) Member - Apr 2005
OpenSolaris Governing Board (OGB) Member - Feb 2006
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
Posts:
802
From:
Plano, TX
Registered:
4/27/05
|
|
|
|
Re: test questions to test OGB election process
(presented as a poll)
Posted:
Feb 21, 2007 6:00 PM
in response to: fielding
|
|
On Wed, 21 Feb 2007, Roy T. Fielding wrote:
> 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
We can't do that - many projects are tied to other SCMs; in many cases, to
remain compatible with upstream sources. Mercurial has been designated
the preferred SCM for ON and the preferred SCM for new projects. So the
question is whether prioritizing the rollout of Mercurial will help
increase developer mindshare. And where this item lies in the list of
priorities.
> > - 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.
Agreed.
> > - 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.
But the question allows us to learn if the community thinks that
opensourcing it would help increase developer mindshare. If the community
thinks that its irrelevant, then they won't vote for it.
> > - 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
No - see more below - but fails miserably as a question because you saw it
as a dupe.
> > - 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
Remember the goal is to increase Opensolaris developer mindshare. As
such, it makes sense to re-evaluate all licensing options - including the
current CDDL license - not just to limit it to the analysis of GPLv3.
So a shorter version of the original would read:
d. re-evaluate current licensing and recommend changes
> f. reorganize the existing Community/Project organization
> h. provide a test build facility
There are separate needs/issues here:
1) test facility to run any/all operating system test suites and
benchmark suites to ensure that a change does not break something or
impact system performance (negatively).
2) build facility for SPARC
3) build facility for x86/AMD64
Since the voting system is STV - it would be interesting to see which
facilities are relevant to increasing developer mindshare. For example,
SPARC build systems tend to be more expensive to acquire - _fast_ SPARC
build systems are (usually) beyond the resources of a single FOSS
developer/contributor[1]. So, my suspicion is that a SPARC based build
facility might be the most relevant option to increasing developer
mindshare - but it sure would be nice to get some real-world feedback from
the community.
So a shorter version of the above would still be 3 items as follows:
h1. provide a SPARC based kernel/project build facility
h2. provide an x86/AMD64 based kernel/project build facility
h3. provide an ON test facility (SPARC & x86)
> 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
>
Thanks Roy. I'll give this some more thought and push out another
revision for comment.
[1] for example, Roland Mainz' (working on the ksh93 integration project)
fastest SPARC build system is an Ultra5 - which is a miserable system to
do *any* development work on.
Al Hopper Logical Approach Inc, Plano, TX. al@logical-approach.com
Voice: 972.379.2133 Fax: 972.379.2134 Timezone: US CDT
OpenSolaris.Org Community Advisory Board (CAB) Member - Apr 2005
OpenSolaris Governing Board (OGB) Member - Feb 2006
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,495
From:
Registered:
5/18/05
|
|
|
|
Re: test questions to test OGB election process
(presented as a poll)
Posted:
Feb 21, 2007 9:49 PM
in response to: fielding
|
|
> 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
+1
-John
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
Posts:
768
From:
US
Registered:
6/17/05
|
|
|
|
Re: test questions to test OGB election
process (presented as a poll)
Posted:
Feb 22, 2007 6:13 AM
in response to: fielding
|
|
Roy T. Fielding wrote:
> 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
>
While I agree that shorter questions would be better, your shortening here
changes some of the questions, rather than just phrasing them more briefly.
At least b. j. k. l, and q. changed meaning fairly substantially, I think.
To be clear, are you purely suggesting the briefer language, or the briefer
language *and* the different questions?
-- Rich
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,695
From:
US
Registered:
4/28/05
|
|
|
|
Re: test questions to test OGB election process
(presented as a poll)
Posted:
Feb 22, 2007 6:49 AM
in response to: fielding
|
|
+1 both to reducing the number of questions to 12 or so, and shortening the
questions themselves to 50 characters or so.
Eric
On Wed, 21 Feb 2007, Roy T. Fielding wrote:
> 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
>
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
Posts:
3,657
From:
DE
Registered:
6/16/05
|
|
|
|
mailman removal ? / was: Re: test questions to test OGB
election process(presented as a poll)
Posted:
Feb 22, 2007 6:56 PM
in response to: alhopper
|
|
Al Hopper wrote:
[snip]
> - evaluate if mailman/jive should be upgraded or replaced
Please remove "mailman" from that list. It's one of the pieces which
currently works more or less flawlessly.
Most of the problems we have with email, postings and SPAM are coming
from the "Jive"-addon (I wish that thing would be boiled in acid or
worse).
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland dot mainz at nrubsig dot org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,695
From:
US
Registered:
4/28/05
|
|
|
|
Re: mailman removal ? / was: Re: test questions to test
OGB election process(presented as a poll)
Posted:
Feb 23, 2007 7:37 AM
in response to: gisburn
|
|
On Thu, 22 Feb 2007, Roland Mainz wrote:
> Al Hopper wrote:
> [snip]
>> - evaluate if mailman/jive should be upgraded or replaced
>
> Please remove "mailman" from that list. It's one of the pieces which
> currently works more or less flawlessly.
+1. Further to that point: An upgrade of Mailman is in the works, so it'll
get better; we're in good company since so many other opensource projects
use Mailman; and it's written in a very popular, powerful, accessible
language (Python).
Eric
>
> Most of the problems we have with email, postings and SPAM are coming
> from the "Jive"-addon (I wish that thing would be boiled in acid or
> worse).
>
> ----
>
> Bye,
> Roland
>
> --
> __ . . __
> (o.\ \/ /.o) roland dot mainz at nrubsig dot org
> \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
> /O /==\ O\ TEL +49 641 7950090
> (;O/ \/ \O;)
>
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
Posts:
768
From:
US
Registered:
6/17/05
|
|
|
|
Re: mailman removal ? / was: Re: test questions to
test OGB election process(presented as a poll)
Posted:
Feb 23, 2007 7:41 AM
in response to: gisburn
|
|
Roland Mainz wrote:
> Al Hopper wrote:
> [snip]
>> - evaluate if mailman/jive should be upgraded or replaced
>
> Please remove "mailman" from that list. It's one of the pieces which
> currently works more or less flawlessly.
>
Which goes back to my (unanswered) query about whether this was intended to
shorten the questions, or actually change them, as it did.
-- Rich
_______________________________________________
cab-discuss mailing list
cab-discuss at opensolaris dot org
|
|
|
|
|
