Re: Community update
"Bob Jacoby" <[email protected]> Wed, 25 Aug 2004 08:25:11 -0500
| Newsgroups | gmane.linux.redhat.ccm.general |
|---|---|
| Message-ID | <[email protected]> |
This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --===============0964719189== Content-Type: multipart/alternative; boundary="=_B999D92F.13729E38" This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_B999D92F.13729E38 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Thanks for all the responses. I guess I'm still a little confused on the = difference between APLAWS and APLAWS+. Your and Richard's statements seem = to have subtle differences, but this may be due to the APLAWS vs APLAWS+ = thing. Richard: "Patches to APLAWS+ that affect CCM should (and generally do) = find their way upstream." Daniel: "APLAWS & CCM are one & the same codebase ..." Let me express my understanding so you can correct me... APLAWS was a fork from the original CCM codebase. It provided additional = features (and perhaps bug fixes) that were not supported within CCM. = APLAWS+ is separate from APLAWS and bundles together various applications = and components. APLAWS+ pieces were written to be based on the APLAWS fork = of the CCM and would not work against CCM itself. The APLAWS fork has, for = the most part, been merged back in to the CCM codebase and for all = intensive purposes doesn't exist anymore. APLAWS+ can therefore work = against the CCM codebase, with the exception of a few pieces that still = require the APLAWS fork (I assume due to some functionality in APLAWS that = wasn't merged in to the CCM codebase).=20 Is this accurate? If so,=20 What pieces of APLAWS+ can not work against the CCM codebase? Are there = plans to modify these pieces to eliminate the dependancy? >From Richard's statement I infer that APLAWS+ still makes modifications to = code that exists within the CCM codebase so another fork exists - just at = a higher level. With the move to ObjectWeb do APLAWS+ developers intend to = stop introducing these core changes in to APLAWS+ and put them in CCM from = the beginning? Thanks, Bob >>> "Daniel P. Berrange" <[email protected]> 08/24/04 04:49AM >>> On Mon, Aug 23, 2004 at 02:17:19PM -0400, Richard Li wrote: > APLAWS+ is built directly on top of CCM. Historically it has forked=20 > WAF/CMS but with the 6.1.0 release we worked hard to merge all of the=20 > forks into the mainline in a supportable way. Yes, following on from what Richard said, we merged everything we needed from the previous APLAWS fork, into WAF/CMS 6.10, so we are running APLAWS+ on the official supported mainline codebase. We have no intention of forking again, since its not in anybody's interest. So as it standards now, APLAWS+ is bst considered as a layer of additional applications ontop of the stanard WAF + CMS. Only one or two of these applications are in any way APLAWS specific, so if desired you can pick and choose which additional apps you'd like to install. For those who are not familiar with APLAWS+ it bundles together * WAF - formerly CCM-Core * CMS - the CMS itself * Importer - content import tool * Exporter - contnet export tool * Forum - discussion forums * Portals - collaborative workspaces * Terms - controlled category list importer & management * Shortcuts - URL shortcuts * Search - public facing search & remote SOAP search service * Rss - RSS syndication of content * Themes - manage XSL themes for styling * Subsite - name based virtual hosting from single CMS * navigation - general purpose content navigation=20 * A-Z - autogenerated A-Z of contnetn & categories * Auth - integration with HTTP authentication, eg Basic Auth, NTLM There are also a bunch of extra content types ontop of the 9 or so we previously contributed back to the general CMS app. Since APLAWS+ now lets you pick & choose amongst these apps, rather than having hem as a single unit, I'd say we're in a very good situation for community involvement. We finally have a single code base for all projects, and a large set of applications & content types. Not to mention the large technical imporvments we made in the 6.1 release cycle to kill off some of the more qustionable code & move us in the direction of a more J2EE facing implementation.=20 > > The problem is I don't have Aplaws; I have CCM. While it's great = that=20 > > there is an apparent strong community for a line of CCM, unless = you're=20 > > supporting the base codeline as opposed to a sibling or cousin it=20 > > really doesn't assuage my concerns for support. I'll admit I'm not=20 > > familiar with Aplaws - not a lick. Have you changed the core CCM = code=20 > > or do you just provide extensions and then submit any required core=20 > > modifications to Red Hat? I hope the above overview helped your understanding of how APLAWS fits in with CCM. APLAWS & CCM are one & the same codebase - its merely a=20 bundle of re-usable CCM applications with an integration layer added on top to provide some government focused pieces. Dan. --=20 |=3D- Red Hat, 338 Euston Road, London, NW1 3BT. +44 (0)7977 267 243 = -=3D| |=3D- Perl modules: http://search.cpan.org/~danberr/ = -=3D| |=3D- Projects: http://freshmeat.net/~danielpb/ = -=3D| |=3D- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 = -=3D|=20 --=20 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/ --=_B999D92F.13729E38 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Description: HTML <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"= > <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD> <BODY style=3D"MARGIN-TOP: 2px; FONT: 10pt Arial; MARGIN-LEFT: 2px"> <DIV>Thanks for all the responses. I guess I'm still a little confused on = the=20 difference between APLAWS and APLAWS+. Your and Richard's statements s= eem=20 to have subtle differences, but this may be due to the APLAWS vs APLAWS+=20= thing.</DIV> <DIV> </DIV> <DIV>Richard: "Patches to APLAWS+ that affect CCM should (and generally = do) find=20 their way upstream."</DIV> <DIV>Daniel: "APLAWS & CCM are one & the same codebase ..."</DIV> <DIV> </DIV> <DIV>Let me express my understanding so you can correct me...</DIV> <DIV> </DIV> <DIV>APLAWS was a fork from the original CCM codebase. It provided = additional=20 features (and perhaps bug fixes) that were not supported within=20 CCM. APLAWS+ is separate from APLAWS and bundles together = various=20 applications and components. APLAWS+ pieces were written to be based = on the=20 APLAWS fork of the CCM and would not work against CCM itself. The = APLAWS=20 fork has, for the most part, been merged back in to the CCM = codebase=20 and for all intensive purposes doesn't exist anymore. APLAWS+ can = therefore work=20 against the CCM codebase, with the exception of a few pieces that still = require=20 the APLAWS fork (I assume due to some functionality in APLAWS that wasn't = merged=20 in to the CCM codebase). </DIV> <DIV> </DIV> <DIV>Is this accurate? If so, </DIV> <DIV> </DIV> <DIV>What pieces of APLAWS+ can not work against the CCM codebase? Are = there=20 plans to modify these pieces to eliminate the dependancy?</DIV> <DIV> </DIV> <DIV>From Richard's statement I infer that APLAWS+ still makes modification= s to=20 code that exists within the CCM codebase so another fork exists - just at = a=20 higher level. With the move to ObjectWeb do APLAWS+ developers intend = to=20 stop introducing these core changes in to APLAWS+ and put them in CCM from = the=20 beginning?</DIV> <DIV> </DIV> <DIV>Thanks,<BR>Bob</DIV> <DIV><BR>>>> "Daniel P. Berrange" <[email protected]> = 08/24/04=20 04:49AM >>><BR>On Mon, Aug 23, 2004 at 02:17:19PM -0400, Richard = Li=20 wrote:<BR>> APLAWS+ is built directly on top of CCM. Historically it = has=20 forked <BR>> WAF/CMS but with the 6.1.0 release we worked hard to merge = all=20 of the <BR>> forks into the mainline in a supportable way.<BR><BR>Yes,= =20 following on from what Richard said, we merged everything we<BR>needed = from the=20 previous APLAWS fork, into WAF/CMS 6.10, so we are<BR>running APLAWS+ on = the=20 official supported mainline codebase. We have<BR>no intention of forking = again,=20 since its not in anybody's interest.<BR><BR>So as it standards now, = APLAWS+ is=20 bst considered as a layer of additional<BR>applications ontop of the = stanard WAF=20 + CMS. Only one or two of these<BR>applications are in any way = APLAWS=20 specific, so if desired you can pick<BR>and choose which additional apps = you'd=20 like to install. For those who<BR>are not familiar with APLAWS+ it = bundles=20 together<BR><BR> * WAF - formerly CCM-Core<BR> * CMS - the = CMS=20 itself<BR> * Importer - content import tool<BR> * Exporter - = contnet=20 export tool<BR> * Forum - discussion forums<BR> * Portals -=20 collaborative workspaces<BR> * Terms - controlled category list = importer=20 & management<BR> * Shortcuts - URL shortcuts<BR> * Search = -=20 public facing search & remote SOAP search service<BR> * Rss - = RSS=20 syndication of content<BR> * Themes - manage XSL themes for=20 styling<BR> * Subsite - name based virtual hosting from single=20 CMS<BR> * navigation - general purpose content navigation <BR> = * A-Z=20 - autogenerated A-Z of contnetn & categories<BR> * Auth - = integration=20 with HTTP authentication, eg Basic Auth, NTLM<BR><BR>There are also a = bunch of=20 extra content types ontop of the 9 or<BR>so we previously contributed back = to=20 the general CMS app. Since APLAWS+<BR>now lets you pick & choose = amongst=20 these apps, rather than having hem<BR>as a single unit, I'd say we're in a = very=20 good situation for community<BR>involvement. We finally have a single code = base=20 for all projects, and<BR>a large set of applications & content types. = Not to=20 mention the large<BR>technical imporvments we made in the 6.1 release = cycle to=20 kill off<BR>some of the more qustionable code & move us in the = direction of=20 a<BR>more J2EE facing implementation. <BR><BR>> > The problem is I = don't=20 have Aplaws; I have CCM. While it's great that <BR>> > there is = an=20 apparent strong community for a line of CCM, unless you're <BR>> = >=20 supporting the base codeline as opposed to a sibling or cousin it <BR>> = >=20 really doesn't assuage my concerns for support. I'll admit I'm not = <BR>> >=20 familiar with Aplaws - not a lick. Have you changed the core CCM code = <BR>>=20 > or do you just provide extensions and then submit any required = core=20 <BR>> > modifications to Red Hat?<BR><BR>I hope the above overview = helped=20 your understanding of how APLAWS fits<BR>in with CCM. APLAWS & CCM are = one=20 & the same codebase - its merely a <BR>bundle of re-usable CCM = applications=20 with an integration layer added<BR>on top to provide some government = focused=20 pieces.<BR><BR>Dan.<BR>-- <BR>|=3D- Red Hat, 338 Euston Road, = London,=20 NW1 3BT. +44 (0)7977 267 243 =20 -=3D|<BR>|=3D- Perl = modules: <A=20 href=3D"http://search.cpan.org/~danberr/  = ; ">http://search.cpan.org/~danber= r/ &= nbsp;</A>=20 -=3D|<BR>|=3D- &= nbsp; =20 Projects: <A=20 href=3D"http://freshmeat.net/~danielpb/ = ">http://freshmeat.net/~dan= ielpb/ &nb= sp; </A>=20 -=3D|<BR>|=3D- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 = B3DF F742=20 7D3B 9505 -=3D| <BR><BR><BR>-- <BR>Redhat-ccm-list mailing=20 list<BR>[email protected]<BR><A=20 href=3D"https://www.redhat.com/mailman/listinfo/redhat-ccm-list">https://ww= w.redhat.com/mailman/listinfo/redhat-ccm-list</A><BR>Archives:=20 <A=20 href=3D"https://www.redhat.com/pipermail/redhat-ccm-list/">https://www.redh= at.com/pipermail/redhat-ccm-list/</A><BR><BR></DIV></BODY></HTML> --=_B999D92F.13729E38-- --===============0964719189== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- 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/ --===============0964719189==--