incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c..@incubator.apache.org
Subject [Incubator Wiki] Updated: JcmsProposal
Date Sun, 17 Oct 2004 11:47:24 GMT
   Date: 2004-10-17T04:47:24
   Editor: RaphaelLuta <raphael@apache.org>
   Wiki: Incubator Wiki
   Page: JcmsProposal
   URL: http://wiki.apache.org/incubator/JcmsProposal

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -1,160 +1,169 @@
-!!! X Project Incubation Status TEMPLATE
+= Proposal for new project JCMS =
 
-This document is the template for project incubation status.
+Accepted by the Portals PMC on September 27, 2004.
 
-What to do to set it up:
+== Rationale ==
 
-* copy this file and name it <projectname>.cwiki
-* add this page in incubator/site/site.xml as for other projects
-* add a section in incubator/site/projects/index.xml
+JCMS offers a complete platform for creating, managing, and
+publishing content in your portal.  JCMS integrates content repositories,
+workflow, collaboration and personalization via existing open source
+projects and powerful standards like WEBDAV, JCR, ... . It includes
+features like taxonomy, content versioning, fine grained access control,
+collaborative editing, publication workflow, scheduling, indexing,
+searching and more. It will  support many document types like XML,
+HTML, PDF, MS Office, Open office, ect.  JCMS is specifically focussed
+on content services for portals but can also be used for a web
+based content management system or a document management application.
 
-For this file (syntax reference is at http://xml.apache.org/forrest/wiki-sample.html):
+The JCMS engine groups together different content stores into
+the same virtual content tree. In this way, the portal application
+can access to heterogenous content servers based on different
+technologies (WEBDAV, JCR or proprietary content stores).
+The JCMS content model is a high level object model giving an
+abstraction on the underlying technology used by the content store.
+The core object model is composed of "Document", "Folder","Link",
+A specific application can inherit this model and extend it to fit
+any specific purpose.
 
-* substitute the XYZ project name with the real one
-* fill in the "Description"
-* edit "Project info" to contain only effective resources
-* start doing "Incubation work items"
+JCMS is also proposed as the default CMS service for Jetspeed 2.
+In order to have a complete portal integration, the JCMS project will
+offer a series of JSR-168 portlets like content browser, editors and content
+administration portlets.
 
-When an "Incubation work item" is done, place the date in the supplied space, 
-and if necessary update "Project info" to reflect changes in resources.
+=== Criteria ===
 
-There are also sections where to place project news and incubation status reports.
+==== Meritocracy ====
 
-''On the first edit of this file, please delete this notice.''
+The community around JCMS is not yet fully defined so no formal
+community rules are formally enforced, however given the committers
+ties and experience with current Apache projects, all common Apache
+community rules and guidelines are ccurrently used de facto and
+will be applied within the JCMS community. 
 
-{{{ -----8-<---- cut here -------8-<---- cut here -------8-<---- cut here -------8-<----
 }}}
+==== Community ====
 
+There is not yet a JCMS community but there is a huge amount of
+demands on the Jetspeed mailing for this kind of tools.
+So, we can expect that the JCMS community will be mainly the
+current Jetspeed community. Due to the fact that JCMS will support
+Webdav, a lot of Slide users will be also interested by JCMS.
 
-!!! XYZ Project Incubation Status
+==== Core Developers ====
 
-This page tracks the project status, incubator-wise.
-For more general project status, look on the project website.
+Currently, there are 2 developpers, one of them having a large experience at
+Apache.
 
-!!! Description
 
-The XYZ Project is a wonderful project that does things and goes places.
+==== Alignment ====
 
-!!! News
+The initial code base is targeted to run within Jetspeed, but the
+goal is to allow the framework to run on any JSR-168 compliant portal solution 
+and any kind of java application like web services, ....
+The services can be running on any Spring or PicoContainer applications
+and the JCMS portlets will be JSR-168 compatible. 
 
-* none yet
+=== Warning Signs ===
 
-!!! Project info
+==== Orphaned products ====
 
-* link to the main website
+The framework being proposed is an evolution of 2 different works made by
+Christophe Lombart and David Sean Taylor. Last year, David build a CMS
+solution for the BBC and Which Online in the UK and at the same time, 
+Christophe build a document management application for the European Commission.
 
-* link to the page(s) that tell how to participate
-  (Website,Mailing lists,Bug tracking,Source code)
-  
-* link to the project status file
-  (Committers,non-incubation action items,project
-   resources, etc)
+After some discussions, they realised the interest to build a common
+version of their work and publish it to the open source community.
 
-If the project website and code repository are not yet setup,
-use the following table:
+==== Inexperience with open source ====
 
-|| item              || type     || reference                 
-|  Website           | www       | [http://incubator.apache.org/X/|http://incubator.apache.org/X/]
-|  .                 | wiki      | .
-|  Mailing list      | dev       | incubator-dev@incubator.apache.org
-|  .                 | cvs       | incubator-cvs@apache.org
-|  Bug tracking      | .         | .
-|  Source code       | CVS       | incubator-X
-|  Mentors           | id1       | Name1 Surname1
-|  .                 | id2       | Name2 Surname2
-|  Committers        | .         | .
-|  Extra             | .         | .
-  
+Both developers have experience working with open source projects. David
+Sean Taylor has experience as committer on other Apache projects and PMC member
+of Apache Portals.
 
-!!! Incubation status reports
+==== Homogenous developers ====
 
-* none yet
+The current list of committers includes developers from different companies.
+The committers are geographically distributed across the U.S. and Europe.
+They are experienced with working in a distributed environment. 
 
-!!! Incubation work items
+==== Reliance on salaried developers ====
 
-!! Project Setup
+Christophe Lombart working for Sword Technologies plan to use JCMS in
+the last year quarter.
+David Sean Taylor is self-employed, with no current contracts using
+JCMS. However he plans to integrate JCMS into J2 to build out of the box CMS
+solutions at Jetspeed. 
 
-This is the first phase on incubation, needed to start the project at Apache.
+==== No ties to other Apache products ====
 
-'' Item assignment is shown by the Apache id.''
-'' Completed tasks are shown by the completion date (YYYY-MM-dd). ''
+As described in the Alignment section, this framework already has ties
+to many Apache products. The framework is also already license-compatible with
+Apache products; in fact, it is currently licensed under the Apache License 2.0. 
 
-! Identify the project to be incubated
-|| date || item
-| ....-..-.. | Make sure that the requested project name does not already exist and check
www.nameprotect.com to be sure that the name is not already trademarked for an existing software
product.
-| ....-..-.. | If request from an existing Apache project to adopt an external package, then
ask the Apache project for the cvs module and mail address names.
-| ....-..-.. | If request from outside Apache to enter an existing Apache project, then post
a message to that project for them to decide on acceptance.
-| ....-..-.. | If request from anywhere to become a stand-alone PMC, then assess the fit
with the ASF, and create the lists and modules under the incubator address/module names if
accepted.
+==== A fascination with the Apache brand ====
 
-! Interim responsibility
+The committers are intent on developing a strong open source community
+around the JCMS framework;
+Given its close relationship with Jetspeed-2 and Pluto and reliance on
+Slide, we believe that hosting this community within Apache Portals TLP will
+provide the best synergies. 
 
-|| date || item
-| ....-..-.. | Identify all the Mentors for the incubation, by asking all that can be Mentors.

-| ....-..-.. | Subscribe all Mentors on the pmc and general lists. 
-| ....-..-.. | Give all Mentors access to all incubator CVS modules. (to be done by PMC chair)
 
-| ....-..-.. | Tell Mentors to track progress in the file 'incubator/projects/{project.name}.cwiki'

+== Scope of the subprojects ==
 
-! Copyright
+The JCMS project can be split into 3 subprojects :
 
-|| date || item
-| ....-..-.. | Check and make sure that the papers that transfer rights to the ASF been received.
It is only necessary to transfer rights for the package, the core code, and any new code produced
by the project. 
-| ....-..-.. | Check and make sure that the files that have been donated have been updated
to reflect the new ASF copyright. 
+1. The JCMS services : all JCMS services are simple POJO components
+which can be running into different containers.
 
-! Verify distribution rights
+The core JCMS services are :
+ * The Model Service.
+ * The Version Service.
+ * The Security Service.
+ * The Search Service.
+ * The Index Service.
+ * The Workflow Service.
+ * The Event handler Service.
 
-|| date || item
-| ....-..-.. | Check and make sure that for all code included with the distribution that
is not under the Apache license, e have the right to combine with Apache-licensed code and
redistribute. 
-| ....-..-.. | Check and make sure that all source code distributed by the project is covered
by one or more of the following approved licenses:  Apache, BSD, Artistic, MIT/X, MIT/W3C,
MPL 1.1, or something with essentially the same terms.
+The persistence service (this is the key component which will map the
+JCMS object model into the underlying model used to access a specific content store).
 
-! Establish a list of active committers !
+2. The JCMS engines : The target of this subproject is provided nice
+integration with existing container frameworks like Spring, PicoContainer, EJB, ...
 
-|| date || item
-| ....-..-.. | Check that all active committers have submitted a contributors agreement.

-| ....-..-.. | Add all active committers in the STATUS file. 
-| ....-..-.. | Ask root for the creation of committers' accounts on cvs.apache.org. 
+3. The JCMS portlets : This target will provide a set of JSR-168 compatible portlets
+grouped into different portlet categories : content browser, content viewer,
+editor & content administration.
 
-! Infrastructure !
+== Identify the initial source from which the subproject is to be populated ==
+ 
+The initial source will be donated by Christophe and David.
+A snapshot can be found here:
 
-|| date || item
-| ....-..-.. | Ask infrastructure to create source repository modules and grant the committers
karma. 
-| ....-..-.. | Ask infrastructure to set up and archive Mailing lists. 
-| ....-..-.. | Decide about and then ask infrastructure to setup an issuetracking system
(Bugzilla, Scarab, Jira). 
-| ....-..-.. | Migrate the project to our infrastructure. 
+http://www.bluesunrise.com/jetspeed-2/jcms2.zip
 
-! Project specific 
+== Identify the ASF resources to be created ==
 
-''Add project specific tasks here.''
+=== mailing list(s) ===
 
-!! Incubation 
+ * jcms-ppmc via incubator.apache.org (with moderated subscriptions)
+ * jcms-dev  via incubator.apache.org
+ * jcms-user via incubator.apache.org
 
-These action items have to be checked for during the whole incubation process.
+=== Subversion repositories ===
 
-'' These items are not to be signed as done during incubation, as they may change during
incubation.  ''
-'' They are to be looked into and described in the status reports and completed in the request
for incubation signoff.  ''
+ * incubator/jcms
 
-! Collaborative Development 
+=== Jira ===
 
-* Have all of the active long-term volunteers been identified and acknowledged as committers
on the project?
-* Are there three or more independent committers? (The legal definition of independent is
long and boring, but basically it means that there is no binding relationship between the
individuals, such as a shared employer, that is capable of overriding their free will as individuals,
directly or indirectly.)
-* Are project decisions being made in public by the committers?
-* Are the decision-making guidelines published and agreed to by all of the committers?
+ * JCMS project with categories for Core, Engines, Portlets, Docs
 
-! Licensing awareness 
+== Identify the initial set of committers ==
 
-* Are all licensing, trademark, credit issues being taken care of and acknowleged by all
committers?
+ ||<tablebgcolor='#E0E0FF'>Raphaël Luta||Aptiwan||ASF, Portals||
+ ||David S. Taylor||Bluesunrise||Portals||
+ ||Christophe Lombart||Sword Technologies||||
 
-! Project Specific 
+== Identify Apache sponsoring individual ==
 
-''Add project specific tasks here.''
-
-!! Exit 
-
-''Things to check for before voting the project out.''
-
-! Organizational acceptance of responsibility for the project 
-
-* If graduating to an existing PMC, has the PMC voted to accept it?
-* If graduating to a new PMC, has the board voted to accept it?
-
-! Incubator sign-off 
-
-* Has the Incubator decided that the project has accomplished all of the above tasks?
+ * Raphaël Luta, champion and mentor for the project,
+ (as defined in http://incubator.apache.org/incubation/Roles_and_Responsibilities.html)

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message