Discussion about the OpenGroupware.org project and OGO

Hi Folks!

Please reply (not 'Reply-to-all') to this on the
'discuss' list, to keep things 'list relevant'.  I'm
cross posting just to get anyone's opionions on
'users' that may not be on 'discuss' yet...

I've been following some threads on the users list
with interest.  I'll get to that in a minute.  First
of all, I'd like to thank SKYRIX for opening up the
source to make OGO a possibility.  Secondly, I'd like
to thank Helge and the other OGO developers for all
the hard work they've been doing, and for all the
support they're providing the OGO community.  Keep up
the great work, folks!

What I'd like to throw open for discussion is some
observations, having been on the list for a while, and
as an "amateur linux end-user".  People are ***
EXCITED *** about OGO, and all that OGO represents to
them (freedom from M$, more features, more reliabilty,
whatever...).    And people, because they're excited,
want it NOW.  Where I think people may be getting a
little frustrated, is that there doesn't appear to be
any dates, timelines or milestones around when OGO
goes 1.0.  Helge has said, much like the Debian folks,
"when it's ready".  There's nothing wrong with that;
its just that it's not what these excited people want
to hear.  I know the project is in it's infancy, and
is going through growing pains right now, but
newcomers may not know that yet.

What I'm throwing open for discussion is the
following: (and maybe we can capture some of that
discussion into documentation which can be posted)

How is the project going to be managed, and how will
goals, milestones, deliverables and targets be decided
upon? (Process, teams, etc.)

What will define 1.0? (Features, functionality, docs,
support, etc.)

What bugs HAVE to be fixed before 1.0 can happen
(gating issues)?

What features MUST be complete before 1.0 can happen,
and how do those features get "voted on" or otherwise
decided upon?

How can the COMMUNITY best contribute to make all of
that happen?

How can we best recruit people to work on the project?
 (I've been browsing through bugzilla, and the list of
enhancement requests just keeps on growing...)

How can we avoid burning out our key developers? (or
"pissing them off" so they don't want to play here any
more ;-)

+ anything else you folks can think of...

Please Note:  This is not meant to critize anyone, or
the project itself.  People have done a great job, and
OGO is usable as-is, and many folks on the list are
deploying it into production (this coming from a guy
who still can't get OGO working with Apache properly,
but that's another issue ;-)

This is thrown out for discussion in the hopes of
improving the project, and the lives of those working
on it.  *** Please *** keep comments and discussion
civilized... there are humans with feelings (possible
STRONG feelings) on the other end of that e-mail, and
we don't want to offend those who may consider OGO
their baby.  I'm only saying this because things were
getting a little heated on the "clients" thread, and I
don't want to see any hurt feelings here.

Thanks for your time!

/Mike

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca
-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss