The apache CMS page (http://www.staging.apache.org/dev/cms.html) indicates that the future plans include phasing out Confluence as a CMS. Makes me wonder if it's a good idea to move the new website to something that's already known to suck ( by Howard's account ) and that is known to soon be obsoleted (based on the CMS article).
Regards, Alex K On Wed, Oct 13, 2010 at 7:41 AM, Ulrich Stärk <[email protected]> wrote: > - everything we generate ourselves (docbook, apt, markdown, whatever) plus > maybe svnpubsub (infra service to automatically checkout things from svn we > checked in, like generated websites) > - the new infra CMS http://www.staging.apache.org/dev/cms.html > - confluence+autoexport (just to list all the possibilities) > - static html > - a vm where we run our own CMS > > On 13.10.2010 11:00, Andreas Andreou wrote: > >> So, realistically and within apache, what are the alternatives? >> >> On Wed, Oct 13, 2010 at 11:55, Ulrich Stärk<[email protected]> wrote: >> >>> How much further do we have to go with this before we switch to a >>>> different paradigm? I was very enthusiastic about using Confluence, >>>> but my enthusiasm is waning because it's been very, very clunky in >>>> practice, and the exporting stuff is often very broken. >>>> >>>> >>> As was I. But once I evaluated Confluence I changed my mind and told you >>> so. >>> We still have other options. We can stop right now and switch to >>> something >>> else. The already created contents can be exported and converted to some >>> other format, that's not the problem. What we need to do though is >>> finally >>> agree on what we want and only decide once we have evaluated the >>> available >>> solutions. >>> >>> Uli >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
