Re: Workspace vs Projects (WAS Re: Forums)

Chris, thanks for the detailed response, I never expected so much :)

You are correct that the actual organization is definately project centric.  
However, what I think that we want to do is make those that feel comfortable 
within the project structure feel comfortable exchanging ideas with those 
individuals on other projects.  I would prefer not to have multiple 
instances.

I'm going to ask the group for a little bit of help now so that I can do my 
best to make sure where we go helps the larger community.  I intend to 
sponsor development for a system that meets our needs, while at the same time 
hopefully fulfulling the needs of the larger community.  I'm going to do my 
best to describe what I would like to see to meet our needs (perhaps some are 
only perceived, but thats irrelavent).  I will do my best to take into 
consideration any points that people make that may be able to make the system 
fulfill the overal goals of the OGo project.

Some times I think a little bit to fast for my hands to get information on 
paper and it comes out garbled, let me know if you have any questions.

1. As everyone by now I'm sure is aware we'll make the "notes" capability 
threaded and somewhat forum like.

2. Since it seems to me that the idea of a project in the case of OGo is that 
it is a container of all of the other sorts of information, I would like to 
make it perhaps act a bit more as such.  I would like to see a Project be 
able to contain another project.  This would allow for my needs of projects 
having subprojects having subprojects....  Additionally it might be able to 
be used to create a relatively unique feature of being able to roll up 
projects into Master Projects that could show schedules accross the entire 
virtual organization.  I don't know if, with the current architecture, nested 
projects would be difficult to implement.  

For example.  We might have a project called "Anthrax" (some may consider it a 
work area).  It can contain discussions, documents, tasks, etc.  Inside of 
this project, is RegionA Anthrax Project and RegionB Anthrax Project.  Again 
with its own set of discussions, documents, etc.  And so on to whatever depth 
is appropriate.  In addition to these specific projects, some other general 
projects would be created that are typically used for document sharing and 
discussions.  This would be used for things like administrative functions and 
general discussion.  

3.  Add some project reporting capablities such as Gantt Charts.

Ideally I would like to see jetspeed portlets for this, but that is somewhat 
outside the scope of what I can sponsor right now.  It is also a purely 
selfish request because we have other things that are going into jetspeed and 
it would just make that easier :P  And before anyone tells me, I do know that 
there are a few available.

This is the basic idea of what I would like to pursue.  I'm open to 
suggestions, or even comments of that can already be done like Y or thats 
just stupid (with explanation of course).  I would like to encourage anyone 
that uses or needs this type of functionality to comment....I would guess 
that there are other needs that I have not forseen and others may have just 
as much as I would guess that some people with think some of this is silly.

Thanks,
Dustin

On Tuesday 27 July 2004 5:51 pm, Chris H wrote:
> Here is one way to design a very basic system and will require some work:
>
> Basic requirement:
>
> "Representatives from each of these regional centers have been tasks with
> implementing a collaborative scheme that increases communications not only
> within the regional center, but also communications between researchers and
> administrators at different rce's."
>
> Let use a key concept here as " implementing a collaborative scheme that
> increases communications" and lets leave the definition of "communications"
> open ended for now. Note this will need to be defined in detail at a later
> date.
>
> Since the organization is "project centric" this will be a key component of
> the design concept. Secondly as security is an issue based on the subject
> matter more then on an organizational level, user authentication and
> protection of data (not from theft but from alteration) is an important
> element to be consider as well.
>
> So on with the task:
>
> 1. Authenticate all users through a refined LDAP schema
> 2. For each "project ie: anthrax" use a separate OGo instance
> 3. Discussions, threaded or other, incorporated with each "project"<>ogo
> instance.
> 4. As new projects are raised a new instance of OGo is implemented via a
> load script.
> 5. Domain issues are basic: http://marce.vbi.vt.edy/<new project name>
> 6. Add a separate install and instances of OGo for institutional or
> organizational requirements to keep them separate from "project"
> infrastructure. ie: MARCE Admin Core; NIAID RCE Program Office. Its
> important to keep these infrastructure elements separate from the project
> structures both for maintenance, workflow and security considerations.
> 7. hardware, postgresql layout, apache, loadbalancing, system maintenance
> are all issues that need to be considered as well.
>
> So then for each "project, eg: anthrax"
> -the news system becomes the general info distribution tool,
> -all tasks are related to the subject matter, ie: master subject=anthrax
> -calendars are specific to the "project" and contributors who have access
> to that "project" and related to the subject matter, one public/shared
> others private.
> -the OGo projects module becomes the main information container for, notes,
> tasks, documents and possibly discussions related to the "project:anthrax"
> -create an OGo project called "workspace" to make it easier for
> contributors to orientate as this is what they are used too.
> -so intellectually users are confronted with for example;
> Project Anthrax>	News
> 				Tasks
> 				Schedule
> 				Contacts
> 				Workspace
> 				Discussions
> Project Emerging Viruses
> 				News
> 				Tasks
> 				Schedule
> 				Contacts
> 				Workspace
> 				Discussions
> All are accessible via URL pending permissions...:)
>
> eg: 	http://marce.vbi.vt.edy/anthrax
> 	http://marce.vbi.vt.edy/emerging_viruses
>
> Note: http://marce.vbi.vt.edy then becomes the main external information
> portal and access point to the various "projects" This is where zope can
> become very handy for the portal front end by allowing for controlled
> migration of data between the firewall LAN  and WAN if and where required.
> This requires some work however.
>
> More elements and workflow components can be defined once the term
> "communications" is defined as stated above. This term's definition will
> also have a direct impact on user authentication and authorization schemas.
>
> So whats missing?
> -mail system config: not included as this is easy but there is no data on
> that -discussion forums (threaded or other) but this can be developed or
> added via third party
> -db replication: this would be nice to have but requires further
> investigation with the postgresql project and probably needs some
> development effort. - security review and audit.
>
> Could work right across the board ..:)
>
> /ch

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