You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@portals.apache.org by Jun Yang <ju...@cisco.com> on 2004/10/12 21:34:31 UTC

Re: proposal to move Cornerstone into a subproject under portals

Dear Santiago and Portals PMC,

Thanks for your time and reply!

So the biggest issue is whether Cornerstone has been actively 
developed.  Yes, it has.  The only reason why we have not regularly 
checked in the changes into Apache's CVS is only convenience.  The 
community of Cornerstone developers right now is within Cisco (with a 
couple of people eagerly waiting to get started as soon as we have the 
right Apache infrastructure).  Jun is the only one who has commit 
priviledge.  So it is most convenient for us to keep the code in Cisco's 
CVS most of the time and check back into Apache CVS occassionally.  We 
just did a diff between our current version of Cornestone that we use at 
Cisco and the version in Apache CVS.  The result is about 1000 lines 
(available upon request).  Enclosed is the listing of new files and 
directories.  They translate into the following new features:

    * Non-invasiveness (supporting completely framework-free service,
      action, business rule code)
    * JSP taglib for rendering DHTML widgets (supporting easier
      front-end development and easy switching between client and
      server-side rendering)
    * Integration with Hibernate, with generator to generate Hibernate
      configuration files, beans, and Cornerstone factories
      configuration files from database metadata
    * Integration with DynAOP (supporting dynamic proxying)
    * Constructor injection (in addition to setter injection)
    * Caching of invocations
    * MultiPlaneRegistry (supporting preservation of customization over
      upgrades)
    * Consolidation of services, actions, business rules and templates
      under invocation (simplified code base)
    * Template engine
    * etc.

and improvements:

    * Automatic transaction support for persistent factories and
      automatic (declarative) transaction support for actions (relieving
      developors of having to worry about transactions most of time;
      proven both productive for developers and performant in Cisco's
      applications)
    * Support of formal arguments in service orchestration
    * Inline DHTML popups (that will not interfere with popup blockers)
    * Cascading selects (e.g. state select driving city select driving
      store location select, etc.)
    * etc.

So Cornestone has been in active development.  We can check in the 
latest changes into Apache CVS.  We also have no problem going through 
incubation if it is determined to be the best route right now.  Please 
let us know if any more information is needed.

Thanks again!

Jun and Emad

New files in current Cornerstone compared with the version in Apache CVS:
Only in cornerstone-current/org/apache/cornerstone/framework: action
Only in cornerstone-current/org/apache/cornerstone/framework/api: alias
Only in cornerstone-current/org/apache/cornerstone/framework/api: app
Only in cornerstone-current/org/apache/cornerstone/framework/api: bean
Only in cornerstone-current/org/apache/cornerstone/framework/api: cache
Only in cornerstone-current/org/apache/cornerstone/framework/api: component
Only in cornerstone-current/org/apache/cornerstone/framework/api: env
Only in 
cornerstone-current/org/apache/cornerstone/framework/api/factory: meta
Only in cornerstone-old/org/apache/cornerstone/framework/api: implementation
Only in cornerstone-current/org/apache/cornerstone/framework/api: invocation
Only in cornerstone-current/org/apache/cornerstone/framework/api/jmx: 
IModelMBeanDescriptorBuilder.java
Only in cornerstone-current/org/apache/cornerstone/framework/api/jmx: 
IModelMBeanInfoBuilder.java
Only in cornerstone-current/org/apache/cornerstone/framework/api: mail
Only in cornerstone-current/org/apache/cornerstone/framework/api: message
Only in 
cornerstone-current/org/apache/cornerstone/framework/api/persistence: 
IPrimaryKeyGenerator.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/api/persistence: alert
Only in 
cornerstone-current/org/apache/cornerstone/framework/api/persistence: 
dbdialect
Only in 
cornerstone-current/org/apache/cornerstone/framework/api/persistence/factory: 
IPersistentObjectCollectionFactory.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/api/persistence/factory: 
RollbackException.java
Only in cornerstone-current/org/apache/cornerstone/framework/api: proxy
Only in cornerstone-old/org/apache/cornerstone/framework/api: service
Only in 
cornerstone-current/org/apache/cornerstone/framework/api/singleton: 
SingletonAlreadyExistsException.java
Only in cornerstone-current/org/apache/cornerstone/framework: app
Only in cornerstone-current/org/apache/cornerstone/framework: cache
Only in cornerstone-current/org/apache/cornerstone/framework: component
Only in cornerstone-current/org/apache/cornerstone/framework/context: 
NameAliasedContext.java
Only in cornerstone-current/org/apache/cornerstone/framework/factory: 
RandomStringFactory.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/factory/ioc: 
DependencyInjectionFactory.java
Only in cornerstone-old/org/apache/cornerstone/framework/factory/ioc: 
InversionOfControlFactory.java
Only in cornerstone-current/org/apache/cornerstone/framework/factory: meta
Only in cornerstone-current/org/apache/cornerstone/framework: hibernate
Only in cornerstone-old/org/apache/cornerstone/framework: implementation
Only in cornerstone-current/org/apache/cornerstone/framework: invocation
Only in cornerstone-old/org/apache/cornerstone/framework/jmx: 
IModelMBeanDescriptorBuilder.java
Only in cornerstone-old/org/apache/cornerstone/framework/jmx: 
IModelMBeanInfoBuilder.java
Only in cornerstone-current/org/apache/cornerstone/framework: mail
Only in cornerstone-current/org/apache/cornerstone/framework: message
Only in cornerstone-current/org/apache/cornerstone/framework/mvc/action: 
ListElementComparator.java
Only in cornerstone-current/org/apache/cornerstone/framework/mvc/action: 
ShowDummyTableAction.java
Only in cornerstone-current/org/apache/cornerstone/framework/mvc/action: 
ShowPageAction.java
Only in cornerstone-current/org/apache/cornerstone/framework/mvc/action: 
ShowTableAction.java
Only in cornerstone-current/org/apache/cornerstone/framework/mvc/action: 
controller
Only in 
cornerstone-current/org/apache/cornerstone/framework/mvc/controller: 
ActionInfo.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/mvc/controller: 
CallServlet.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/mvc/controller: 
ControllerConstant.java
Only in cornerstone-old/org/apache/cornerstone/framework/mvc/controller: 
ControllerServlet.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/mvc/controller: 
ControllerUtil.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/mvc/controller: 
DoServlet.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/mvc/controller: 
ReturnServlet.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/persistence: 
OraclePrimaryKeyGenerator.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/persistence: alert
Only in 
cornerstone-old/org/apache/cornerstone/framework/persistence/datasource: 
BaseDataSource.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/persistence/datasource: 
factory
Only in 
cornerstone-current/org/apache/cornerstone/framework/persistence: dbdialect
Only in 
cornerstone-current/org/apache/cornerstone/framework/persistence/factory: 
BasePersistentObjectCollectionFirstElementFactory.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/persistence/factory: 
generator
Only in cornerstone-current/org/apache/cornerstone/framework/registry: 
MultiPlaneRegistry.java
Only in cornerstone-old/org/apache/cornerstone/framework/registry: 
OverwritableRegistry.java
Only in 
cornerstone-current/org/apache/cornerstone/framework/registry/factory: 
MultiPlanePropertiesRegistryFactory.java
Only in 
cornerstone-old/org/apache/cornerstone/framework/registry/factory: 
OverwritablePropertiesRegistryFactory.java
Only in cornerstone-current/org/apache/cornerstone/framework: rule
Only in cornerstone-old/org/apache/cornerstone/framework/service: 
BaseServiceFactory.java
Only in cornerstone-old/org/apache/cornerstone/framework/service: 
BaseServiceManager.java
Only in cornerstone-old/org/apache/cornerstone/framework/service: 
LogicalService.java
Only in cornerstone-old/org/apache/cornerstone/framework/service: 
ServiceDescriptor.java
Only in cornerstone-old/org/apache/cornerstone/framework/service: controller
Only in cornerstone-old/org/apache/cornerstone/framework/service: metric
Only in cornerstone-current/org/apache/cornerstone/framework/singleton: 
BaseSingleton.java
Only in cornerstone-current/org/apache/cornerstone/framework: taglib
Only in cornerstone-current/org/apache/cornerstone/framework: template
Only in cornerstone-current/org/apache/cornerstone/framework: test
Only in cornerstone-current/org/apache/cornerstone/framework/util: 
BindVariableParser.java
Only in cornerstone-current/org/apache/cornerstone/framework/util: 
MultiLineValueProperties.java
Only in cornerstone-current/org/apache/cornerstone/framework/util: 
NameValueListOnList.java
Only in cornerstone-current/org/apache/cornerstone/framework/util: 
Types.java
Only in cornerstone-current/org/apache/cornerstone/framework/worker: bo

Santiago Gala wrote:

>El vie, 01-10-2004 a las 14:09 -0700, Jun Yang escribió:
>  
>
>>Dear Portals PMC:
>>
>>We are the main authors of Apache Cornerstone framework that was
>>contributed into the Jetspeed 2 project some time ago.  We propose
>>that it should be moved into its own subproject under
>>portals.apache.com/cornerstone.
>>
>>Motivation
>>      * Active Development
>>              * The Cornerstone framework has been actively developed
>>                at Cisco.  It has accumulated 2.5 years of development
>>                from inception.
>>      * Production Proven
>>              * One of the largest Cisco internal applications that
>>                was built on Cornerstone has been running smoothly for
>>                a year.  Two more applications using Cornerstone are
>>                in development and will be deployed to production by
>>                the end of this year.
>>              * Almost all Cornerstone features are driven by real-
>>                life requirements at Cisco.
>>      * Technology
>>              * Cornerstone is an end-to-end framework that covers all
>>                the way from persistence to service framework to MVC
>>                to DHTML.  Currently Apache doesn't have an end-to-end
>>                framework like it.  Most other containers are focused
>>                on the service layer.
>>              * Multi-dimensional customizability is a unique feature
>>                of Cornerstone which is not found in other frameworks.
>>                See the attached Abstract for details.
>>      * Proximity to Portals
>>              * Cornerstone was originally developed for a portal
>>                application that ran on Jetspeed 1.  Its continued
>>                evolution has taken into account the unique
>>                characteristics of a portal application.  Although not
>>                integrated into Jetspeed 2 yet, many of the features
>>                are directly suited for it.  For example, all the
>>                DHTML features that support what we call a rich thin
>>                client.
>>We have assembled a team within Cisco and around the world of
>>developers (9 total) excited at participating in Cornestone
>>development.  We are all ready to go :).
>>
>>    
>>
>
>There have been discrepancy in the PMC about having Cornerstone as a
>subproject without passing through incubation. Incubation was skipped
>when the repository entered jetspeed and there has been little community
>development since the code landed here.
>
>I think incubation could be skipped if the Cornestone code base starts
>being worked actively (be it in a branch or sandbox) WRT integration
>with jetspeed or pluto, in the current status. It is not the same
>creating a subproject from an active community than creating it from a
>code base showing little to no activity (only build related commits show
>for this part of the code base)
>
>The current consensus is that Cornerstone should build community first.
>Wether if this is done passing back through the incubator or starting
>development activty in the current repository remains to be discussed. 
>
>We can have the discussion in the dev list (general@portals or other
>lists).
>
>  
>
>>Thanks for your consideration!  And thanks for the Jetspeed team for
>>hosting Cornerstone!
>>
>>Jun and Emad
>>    
>>


Re: proposal to move Cornerstone into a subproject under portals

Posted by Santiago Gala <sg...@hisitech.com>.
El mar, 12-10-2004 a las 12:34 -0700, Jun Yang escribió:
> Dear Santiago and Portals PMC,
> 
> Thanks for your time and reply!
> 
> So the biggest issue is whether Cornerstone has been actively
> developed.  Yes, it has.  The only reason why we have not regularly
> checked in the changes into Apache's CVS is only convenience.  The

The issue is not that much "actively developed" as "developed in a
diverse community".

> community of Cornerstone developers right now is within Cisco (with a
> couple of people eagerly waiting to get started as soon as we have the
> right Apache infrastructure).  Jun is the only one who has commit

Diversity of communities is a typical incubation issue. I mean, having a
code base in the ASF who has most or nearly all committers in the same
company is considered to be a bad signal.

> priviledge.  So it is most convenient for us to keep the code in
> Cisco's CVS most of the time and check back into Apache CVS
> occassionally.  We just did a diff between our current version of
> Cornestone that we use at Cisco and the version in Apache CVS.  The
> result is about 1000 lines (available upon request).  Enclosed is the
> listing of new files and directories.  They translate into the
> following new features: 
>       * Non-invasiveness (supporting completely framework-free
>         service, action, business rule code) 
>       * JSP taglib for rendering DHTML widgets (supporting easier
>         front-end development and easy switching between client and
>         server-side rendering) 
>       * Integration with Hibernate, with generator to generate
>         Hibernate configuration files, beans, and Cornerstone
>         factories configuration files from database metadata 
>       * Integration with DynAOP (supporting dynamic proxying) 
>       * Constructor injection (in addition to setter injection) 
>       * Caching of invocations 
>       * MultiPlaneRegistry (supporting preservation of customization
>         over upgrades) 
>       * Consolidation of services, actions, business rules and
>         templates under invocation (simplified code base) 
>       * Template engine 
>       * etc. 
> and improvements: 
>       * Automatic transaction support for persistent factories and
>         automatic (declarative) transaction support for actions
>         (relieving developors of having to worry about transactions
>         most of time; proven both productive for developers and
>         performant in Cisco's applications) 
>       * Support of formal arguments in service orchestration 
>       * Inline DHTML popups (that will not interfere with popup
>         blockers) 
>       * Cascading selects (e.g. state select driving city select
>         driving store location select, etc.) 
>       * etc. 
> So Cornestone has been in active development.  We can check in the
> latest changes into Apache CVS.  We also have no problem going through
> incubation if it is determined to be the best route right now.  Please
> let us know if any more information is needed.
> 

It is nice to know. But the whole point is community development. We
could switch development to the Apache CVS and lists, but having a
subproject for a module which is already mostly isolated from the
portals.apache.org development is asking for a failure in community
integration.

And we will not solve the integration issues in the close, so I think it
is better to start speaking about those in the open.

People interested in the integration of Cornerstone with Jetspeed (1
and/or 2), and having the time and energy to invest into it should speak
now. As I said, some community development is needed, even if it is not
a formal incubation process. We already have the IP cleared, only points
about community development remain open. 

I think we can consider people interested in Cornerstone integration
into Jetspeed 1 or 2 (be it in sandbox or a branch). During the process
I'd expect better community integration, i.e., people from the
Cornerstone community committing in J2/J1/Pluto or WSRP4J code, and the
other way around, people coming from the user or developer groups of
portals getting interested in the development and use of Cornerstone.

This is the way I'm pointing towards.

What do you think?

> Thanks again!
> 
> Jun and Emad
> 
> New files in current Cornerstone compared with the version in Apache
> CVS:
> Only in cornerstone-current/org/apache/cornerstone/framework: action
> Only in cornerstone-current/org/apache/cornerstone/framework/api:
> alias
> Only in cornerstone-current/org/apache/cornerstone/framework/api: app
> Only in cornerstone-current/org/apache/cornerstone/framework/api: bean
> Only in cornerstone-current/org/apache/cornerstone/framework/api:
> cache
> Only in cornerstone-current/org/apache/cornerstone/framework/api:
> component
> Only in cornerstone-current/org/apache/cornerstone/framework/api: env
> Only in cornerstone-
> current/org/apache/cornerstone/framework/api/factory: meta
> Only in cornerstone-old/org/apache/cornerstone/framework/api:
> implementation
> Only in cornerstone-current/org/apache/cornerstone/framework/api:
> invocation
> Only in cornerstone-current/org/apache/cornerstone/framework/api/jmx:
> IModelMBeanDescriptorBuilder.java
> Only in cornerstone-current/org/apache/cornerstone/framework/api/jmx:
> IModelMBeanInfoBuilder.java
> Only in cornerstone-current/org/apache/cornerstone/framework/api: mail
> Only in cornerstone-current/org/apache/cornerstone/framework/api:
> message
> Only in cornerstone-
> current/org/apache/cornerstone/framework/api/persistence:
> IPrimaryKeyGenerator.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/api/persistence: alert
> Only in cornerstone-
> current/org/apache/cornerstone/framework/api/persistence: dbdialect
> Only in cornerstone-
> current/org/apache/cornerstone/framework/api/persistence/factory:
> IPersistentObjectCollectionFactory.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/api/persistence/factory:
> RollbackException.java
> Only in cornerstone-current/org/apache/cornerstone/framework/api:
> proxy
> Only in cornerstone-old/org/apache/cornerstone/framework/api: service
> Only in cornerstone-
> current/org/apache/cornerstone/framework/api/singleton:
> SingletonAlreadyExistsException.java
> Only in cornerstone-current/org/apache/cornerstone/framework: app
> Only in cornerstone-current/org/apache/cornerstone/framework: cache
> Only in cornerstone-current/org/apache/cornerstone/framework:
> component
> Only in cornerstone-current/org/apache/cornerstone/framework/context:
> NameAliasedContext.java
> Only in cornerstone-current/org/apache/cornerstone/framework/factory:
> RandomStringFactory.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/factory/ioc:
> DependencyInjectionFactory.java
> Only in cornerstone-old/org/apache/cornerstone/framework/factory/ioc:
> InversionOfControlFactory.java
> Only in cornerstone-current/org/apache/cornerstone/framework/factory:
> meta
> Only in cornerstone-current/org/apache/cornerstone/framework:
> hibernate
> Only in cornerstone-old/org/apache/cornerstone/framework:
> implementation
> Only in cornerstone-current/org/apache/cornerstone/framework:
> invocation
> Only in cornerstone-old/org/apache/cornerstone/framework/jmx:
> IModelMBeanDescriptorBuilder.java
> Only in cornerstone-old/org/apache/cornerstone/framework/jmx:
> IModelMBeanInfoBuilder.java
> Only in cornerstone-current/org/apache/cornerstone/framework: mail
> Only in cornerstone-current/org/apache/cornerstone/framework: message
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/action:
> ListElementComparator.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/action:
> ShowDummyTableAction.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/action:
> ShowPageAction.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/action:
> ShowTableAction.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/action: controller
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/controller:
> ActionInfo.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/controller:
> CallServlet.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/controller:
> ControllerConstant.java
> Only in cornerstone-
> old/org/apache/cornerstone/framework/mvc/controller:
> ControllerServlet.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/controller:
> ControllerUtil.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/controller:
> DoServlet.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/mvc/controller:
> ReturnServlet.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/persistence:
> OraclePrimaryKeyGenerator.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/persistence: alert
> Only in cornerstone-
> old/org/apache/cornerstone/framework/persistence/datasource:
> BaseDataSource.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/persistence/datasource:
> factory
> Only in cornerstone-
> current/org/apache/cornerstone/framework/persistence: dbdialect
> Only in cornerstone-
> current/org/apache/cornerstone/framework/persistence/factory:
> BasePersistentObjectCollectionFirstElementFactory.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/persistence/factory:
> generator
> Only in cornerstone-current/org/apache/cornerstone/framework/registry:
> MultiPlaneRegistry.java
> Only in cornerstone-old/org/apache/cornerstone/framework/registry:
> OverwritableRegistry.java
> Only in cornerstone-
> current/org/apache/cornerstone/framework/registry/factory:
> MultiPlanePropertiesRegistryFactory.java
> Only in cornerstone-
> old/org/apache/cornerstone/framework/registry/factory:
> OverwritablePropertiesRegistryFactory.java
> Only in cornerstone-current/org/apache/cornerstone/framework: rule
> Only in cornerstone-old/org/apache/cornerstone/framework/service:
> BaseServiceFactory.java
> Only in cornerstone-old/org/apache/cornerstone/framework/service:
> BaseServiceManager.java
> Only in cornerstone-old/org/apache/cornerstone/framework/service:
> LogicalService.java
> Only in cornerstone-old/org/apache/cornerstone/framework/service:
> ServiceDescriptor.java
> Only in cornerstone-old/org/apache/cornerstone/framework/service:
> controller
> Only in cornerstone-old/org/apache/cornerstone/framework/service:
> metric
> Only in cornerstone-
> current/org/apache/cornerstone/framework/singleton: BaseSingleton.java
> Only in cornerstone-current/org/apache/cornerstone/framework: taglib
> Only in cornerstone-current/org/apache/cornerstone/framework: template
> Only in cornerstone-current/org/apache/cornerstone/framework: test
> Only in cornerstone-current/org/apache/cornerstone/framework/util:
> BindVariableParser.java
> Only in cornerstone-current/org/apache/cornerstone/framework/util:
> MultiLineValueProperties.java
> Only in cornerstone-current/org/apache/cornerstone/framework/util:
> NameValueListOnList.java
> Only in cornerstone-current/org/apache/cornerstone/framework/util:
> Types.java
> Only in cornerstone-current/org/apache/cornerstone/framework/worker:
> bo
> 
> Santiago Gala wrote: 
> > El vie, 01-10-2004 a las 14:09 -0700, Jun Yang escribió:
> >   
> > > Dear Portals PMC:
> > > 
> > > We are the main authors of Apache Cornerstone framework that was
> > > contributed into the Jetspeed 2 project some time ago.  We propose
> > > that it should be moved into its own subproject under
> > > portals.apache.com/cornerstone.
> > > 
> > > Motivation
> > >       * Active Development
> > >               * The Cornerstone framework has been actively developed
> > >                 at Cisco.  It has accumulated 2.5 years of development
> > >                 from inception.
> > >       * Production Proven
> > >               * One of the largest Cisco internal applications that
> > >                 was built on Cornerstone has been running smoothly for
> > >                 a year.  Two more applications using Cornerstone are
> > >                 in development and will be deployed to production by
> > >                 the end of this year.
> > >               * Almost all Cornerstone features are driven by real-
> > >                 life requirements at Cisco.
> > >       * Technology
> > >               * Cornerstone is an end-to-end framework that covers all
> > >                 the way from persistence to service framework to MVC
> > >                 to DHTML.  Currently Apache doesn't have an end-to-end
> > >                 framework like it.  Most other containers are focused
> > >                 on the service layer.
> > >               * Multi-dimensional customizability is a unique feature
> > >                 of Cornerstone which is not found in other frameworks.
> > >                 See the attached Abstract for details.
> > >       * Proximity to Portals
> > >               * Cornerstone was originally developed for a portal
> > >                 application that ran on Jetspeed 1.  Its continued
> > >                 evolution has taken into account the unique
> > >                 characteristics of a portal application.  Although not
> > >                 integrated into Jetspeed 2 yet, many of the features
> > >                 are directly suited for it.  For example, all the
> > >                 DHTML features that support what we call a rich thin
> > >                 client.
> > > We have assembled a team within Cisco and around the world of
> > > developers (9 total) excited at participating in Cornestone
> > > development.  We are all ready to go :).
> > > 
> > >     
> > 
> > There have been discrepancy in the PMC about having Cornerstone as a
> > subproject without passing through incubation. Incubation was skipped
> > when the repository entered jetspeed and there has been little community
> > development since the code landed here.
> > 
> > I think incubation could be skipped if the Cornestone code base starts
> > being worked actively (be it in a branch or sandbox) WRT integration
> > with jetspeed or pluto, in the current status. It is not the same
> > creating a subproject from an active community than creating it from a
> > code base showing little to no activity (only build related commits show
> > for this part of the code base)
> > 
> > The current consensus is that Cornerstone should build community first.
> > Wether if this is done passing back through the incubator or starting
> > development activty in the current repository remains to be discussed. 
> > 
> > We can have the discussion in the dev list (general@portals or other
> > lists).
> > 
> >   
> > > Thanks for your consideration!  And thanks for the Jetspeed team for
> > > hosting Cornerstone!
> > > 
> > > Jun and Emad
> > >     
> 
-- 
Santiago Gala <sg...@hisitech.com>
High Sierra Technology, SLU