Re: [OGo-Users] Discussion about the OpenGroupware.org project and OGO

> 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".  

Same, been on the lists since nearly the beginning.  A "professional linux
end-user" and System/Network administrator of a large inter-entity heterogenous
network with lots of Open Source components (as many as possible anyway).

> and all that OGO represents to
> them (freedom from M$, more features, more reliabilty,
> whatever...).    

Open Source groupware, finally.

> And people, because they're excited,
> want it NOW.  

People always 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".  

This is the mantra of nearly every Open Source project;  anyone who has been in
the O.S. community for very long almost knows not to even ask about such
things.  The developers will publish a ROADMAP file when they're ready too.

> 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.)

(1) Documentation (2) Documentation (3) Documentation

They're are more features here than ever get used because the standing question
is "How?".  From - the MRWIDF project permissions,  "I" (insert) means what,
*exactly*? - to Forms and "Publisher", how do those work, precisely?

This is, IMHO, the real advantage of products like Notes & Exchange; choose from
one of hundreds (if not thousands) of books.

(4) There are gaps in the functionality of the XML-RPC API,  this makes 'native'
clients further out.  Maybe ZideStore & DAV is really the better way to do a
client, but back to requirements 1, 2, & 3.  It is REALLY hard to 'explore'
ZideStore since it customizes its behavior to the client; so what is the
cannonical behavior for some given 'mode'?

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

You can vote in Bugzilla; I don't know if that has any relevance.

> How can we avoid burning out our key developers? 

Pay them. :)

> deploying it into production (this coming from a guy
> who still can't get OGO working with Apache properly,
> but that's another issue ;-)

Rest assured it is possible; and to an 'old' UNIX admin remarkably easy.

> 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.

In large part because that thread isn't new, but resurgient.
-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss