Re: Community update

> While I like open-source applications and use them when practical I 
> like to make sure there is a readily available mechanism to support 
> them (through community or paid support) before I use them for 
> critical purposes. For the larger projects like linux, apache, etc it 
> exists. To my knowledge such a strong level of community 
> support doesn't exist for CCM so I question the viability of CCM as a 
> true open source,

I agree that the level of community support for Apache, Linux, and so 
forth far exceeds that of CCM. One of the main goals of our effort is to 
work to build a more vibrant community around CCM.

> 1. What does this mean to those of us who have maintenance and support 
> contracts with Red Hat for CCM? 

There is no change.

> <>2. Will Red Hat still provide maintenance and support contracts for 
> CCM after it's moved to Object Web? 

Red Hat will not provide packaged maintenance and support for CCM, but 
will continue to provide custom consulting services.

> 3. Will Red Hat employees work on CCM development as part of their Red 
> Hat duties or solely on their own time? You mentioned that the CCM 
> engineering team will no longer be dedicated to CCM development. What 
> percentage of their time will be spent on CCM development? How many 
> resources are you removing from CCM development and support that would 
> need to be replaced by ObjectWeb and the community to maintain the 
> current level of CCM development?

Red Hat (nor does any other company, to my knowledge) publically 
disclose resource allocations among product lines. Moreover, resource 
allocation numbers don't make a lot of sense without a full context that 
I'm not at liberty to provide.

>  <>4. What does the short-term development for CCM look like? 
> For example, is the latest 6.1 release the last that will come out of 
> Red Hat or will there be an interim release while ObjectWeb takes the 
> reins?

Hopefully the community can play a role in determing the release 
process. We haven't any reports of critical bugs of 6.1.0 that have 
necessitated an immediate errata release. We have also been extending 
the release cycle of CCM, so it's possible that the complete switchover 
to OW might provide a good point for release.

> <>5. What long-term support does Red Hat intend to provide for CCM 
> development? 

We've been working diligently over the past few releases to shrink the 
footprint of CCM by adopting more open source software. (A lot of CCM, 
and WAF in particular, was designed when there were no open source 
equivalents available.) I'd like to see that continue.

The advent of Red Hat Application Server gives us an opportunity to 
invest in developing a more standards-based platform. We're looking at 
what pieces of WAF can be merged into RHAPS (and componentized, so you 
won't be forced to run RHAPS if you don't want to). So, expect the 
footprint of CCM to continue to shrink.

For the moment, we are focused more on building out some of those 
infrastructure pieces (for example, supporting JDO in persistence) than 
on retrofitting CCM. This is a necessary step for the future vision of 
CCM. I think all of this is necessary; if CCM remains monolithic, no one 
will want to use it.

>  <>6. And, on a more minor note, but something that caused problems 
> for us while we were developing our first release... What will happen 
> to this mailing list and archives? Will they be ported to ObjectWeb? 
> If so, will this list stay up until a new one is available on ObjectWeb?

It will stay.

Richard


-- 
Redhat-ccm-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/redhat-ccm-list
Archives: https://www.redhat.com/pipermail/redhat-ccm-list/