As many of you know, the use of confluence as an Apache service is
being deprecated in favor of a new house-supported web content
management system (CMS). I can vouch for its ease of use compared to
other systems that require editing xml or html, updating an svn site,
and pushing changes. The CMS was designed specifically to enable
people who aren't tech savvy to be able to edit and push site changes.
There's no rush, but OpenJPA should start planning to migrate
openjpa.apache.org off the confluence service and onto the CMS.
This is a pretty major task and I'm looking for a volunteer to drive
it. There's a lot of attention being paid to the CMS by infrastructure
so there's lots of help available.
Any takers?
Thanks,
Craig
P.S. there are several changes needed to openjpa.apache.org that could
be done in conjunction with the CMS change that would have to be done
separately if we don't have a credible CMS migration plan in the near
future...
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
