Re: Workspace vs Projects (WAS Re: Forums)

> > Well, I'm not against that. I only wonder whether "project type people"
> > will then be confused because OGo doesn't support "projects" anymore
> > (not too unlikely I guess).
> This statement is so confusing but reviewing the following shed some light on 
> the above. See;
> http://docs.opengroupware.org/Members/helge/DocumentAPI/DocStorage/
> > What we could do is to use project types (there already is a database
> > field for that) to differentiate between workspaces and projects.
> > But I'm not sure whether this is worth the effort given that they would
> > do exactly the same thing (and the type would just switch the labels).
> Personally and from where I sit its purely a terminology factor. In NA the 
> terms workspace is more common due to scarcity and specialization of project 
> management software of which most automatically assume MS Project and its 
> inherent capabilities when you use the word, "project" 

Yes, at least here in the USA I think this is certainly true.  Project =
dependencies, gant charts, and outcome.  In which case OGo doesn't
really do "projects". 

> The problem with calling it definitely a workspace, more common in NA, is that 
> it does not provide sufficient detail of the functionality or capability of 
> the document store 
> 
> In short I cannot offer a solution as this thread has really confused me and 
> started my thinking. 

This, IMHO, is what makes groupware software so interesting - there are
so many ways to conceptualize any of these problems.

> It then becomes a packaging consideration once the design is overcome. A 
> serious element to consider but this would be more consistent with the notion 
> of workspace then a simple renaming convention. 

I'm not certain I understand this statement.

-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss