The page Plan was changed by pdm at Thu 09 of Mar, 2006 [23:02]
You can view the page by following this link:
http://oscom.avantech.net/tiki-index.php?page=Plan
You can view a diff back to the previous version by following this link:
http://oscom.avantech.net/tiki-pagehistory.php?page=Plan&compare=1&oldver=14&newver=15&diff_style=minsidediff
***********************************************************
The changes in this version follow below, followed after by the current full page text.
***********************************************************
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -Lines: 1-71 changed to +Lines: 1-51 @@
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
((Purpose))
-
((Principles))
-
-
((Vision))
((Brainstorming))
-
-
((Organizing))
-
-
((Actions))
-
((Projects List))
- Please note that the term "projects" is being used in a wider sense and is not specifically aimed at software projects. We need dedicated persons for most projects, who volunteer to be in charge. Feel free to add yours below. If you need more space, just add a short description and add a link to a new wiki page
-
((Organization))
-
-
((Organization: Define Involved Groups))
-
- )
-
((Information:))
- OSCOM Wiki Yeah!
- Other information Channels/tools?
- Make suggestions here
+ ((Common Vocabulary))
- Definition of TermsA kind of glossary on oscom.org, maintained in the Wiki. For example: What is an Enterprise Content Management System? What is WebDAV?
+ What is an Enterprise Content Management System? What is WebDAV?
If there are already pages on Wikipedia, we could simply link there. We could also contribute to Wikipedia and just link from oscom.org.
- Collection of Resources
+ ((Resources))
A collection of links to online resources. For example related organizations, articles, news, etc.
- Collection of Events
+ (( Events))
A collection of _all_ events in the content management segment, not only those organized by OSCOM.
- Collection of Content Management Projects
+ ((Content Management Projects))
A page for each content management software project with basic information. Quality of the project is not an issue here, we simply want all projects listed. The OSCOM Awards make the difference when it comes to quality.
- Personal Page of OSCOM Members
+ ((People))
Just like FSFE, each OSCOM member could have his personal area: http://www.fsfe.org/en/fellows
- CMS MatrixWe need to be more active in maintaining the CMS matrix - how to do that?
+ ((CMS Matrix))
- Planet OSCOM
+ (( Planet OSCOM))
Let's aggregate more feeds! Maybe add a contact form to the Planet page to provide new feeds.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -Lines: 81-89 changed to +Lines: 61-69 @@
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- Software Specification
+ ((Specifications))
Maybe it would make sense to create a repository of basic specifications. For example, what should be included in a Weblog, a Wiki, a CMS, an Intranet, etc.? Not too detailed, but as a kind of quality assurance tool for project developers as well as customers/users.
- Student Projects
+ ((Student Projects))
OSCOM could collect information for students who would like to do an internship at a community/company/organization dealing with FOSS content management. We could provide tips, or a list of potential organizations.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -Lines: 91-95 changed to +Lines: 71-75 @@
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- Mailinglists
+ ((Mailinglists))
We keep the mailinglists we currently have. Let's see if we need some more in the future?
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -Lines: 100-106 changed to +Lines: 80-86 @@
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- OSCOM Awards
+ ((OSCOM Awards))
To foster the goals of OSCOM, we could issue OSCOM Awards once per year, where we reward persons or groups for certain achievements in the field of FOSS content management. The main award could be issued for the "Open Source Content Management Project of the Year". There could be other awards like "Open Source Content Management Event of the Year".
- !Summer of Code
+ ((Summer of Code))
Let's spend OSCOM's money by defining projects which would be good for the FOSCOM community at large
***********************************************************
The new page content follows below.
***********************************************************
((Purpose))
((Principles))
((Vision))
((Brainstorming))
((Organizing))
((Actions))
((Projects List))
((Organization))
((Organization: Define Involved Groups))
((Information:))
((Common Vocabulary))
What is an Enterprise Content Management System? What is WebDAV?
If there are already pages on Wikipedia, we could simply link there. We could also contribute to Wikipedia and just link from oscom.org.
((Resources))
A collection of links to online resources. For example related organizations, articles, news, etc.
(( Events))
A collection of _all_ events in the content management segment, not only those organized by OSCOM.
((Content Management Projects))
A page for each content management software project with basic information. Quality of the project is not an issue here, we simply want all projects listed. The OSCOM Awards make the difference when it comes to quality.
((People))
Just like FSFE, each OSCOM member could have his personal area: http://www.fsfe.org/en/fellows
((CMS Matrix))
(( Planet OSCOM))
Let's aggregate more feeds! Maybe add a contact form to the Planet page to provide new feeds.
((Synergy and Collaboration)): Software Implementation
We need more thinking here, whether OSCOM should keep hosting and pushing collaborative software projects (like the WYSIWYG editors).
I would say yes, but not with highest priority. Once we really achieve such collaboration, this is a sign that there is a big need for it and previous information sharing has actually lead to working on a concrete result.
For the start, we should concentrate on knowledge transfer, which will hopefully foster collaboration in the software domain.
Please see ((SoftwareImplementationProjects|Software Implementation Projects))
((Specifications))
Maybe it would make sense to create a repository of basic specifications. For example, what should be included in a Weblog, a Wiki, a CMS, an Intranet, etc.? Not too detailed, but as a kind of quality assurance tool for project developers as well as customers/users.
((Student Projects))
OSCOM could collect information for students who would like to do an internship at a community/company/organization dealing with FOSS content management. We could provide tips, or a list of potential organizations.
We could also collect information about ongoing student projects. They could be in the field of actual software implementation, as well as sales analysis, etc.
((Mailinglists))
We keep the mailinglists we currently have. Let's see if we need some more in the future?
((Events))
Conferences are good for face-to-face conversations and first-hand knowledge transfer. OSCOM should support everyone in organzing related conferences. We could do this by sharing experiences in the Wiki about previous events.
Roadshows are similar to conferences, but they happen at several places and rather focus on product presentations.
((OSCOM Awards))
To foster the goals of OSCOM, we could issue OSCOM Awards once per year, where we reward persons or groups for certain achievements in the field of FOSS content management. The main award could be issued for the "Open Source Content Management Project of the Year". There could be other awards like "Open Source Content Management Event of the Year".
((Summer of Code))
Let's spend OSCOM's money by defining projects which would be good for the FOSCOM community at large
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.