axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <andreas.veit...@gmail.com>
Subject Re: Moving to website to the new CMS?
Date Tue, 02 Nov 2010 09:16:17 GMT
I followed the discussion that gave birth to that CMS. I think it
represents a progress for non-project sites (such as www and
community, but I'm not convinced that it is a good solution for
project sites. The main points are:

* It's SVN based. In contrast to Confluence, this means that
non-committers can't contribute directly.
* It uses an obscure markup called markdown. That means yet another
markup to learn, while most developers are familiar with XDoc and/or
APT, and Confluence has the necessary features (help and preview) that
makes it easy to learn its markup.
* Its GUI is... minimalist to say the least.

To summarize, switching to that solution would further reduce the
number of people able to contribute to the site, namely to committers
who are willing to familiarize themselves with a CMS specific to the
ASF.

Andreas

On Tue, Nov 2, 2010 at 03:20, Sanjiva Weerawarana <sanjiva@opensource.lk> wrote:
> Now that we're soooo late in having any Website at all how about moving to
> the new CMS instead of Confluence and various other weird contortions?
>
> Sanjiva.
>
> ---------- Forwarded message ----------
> From: Nick Burch <nick.burch@alfresco.com>
> Date: Tue, Nov 2, 2010 at 1:55 AM
> Subject: Moving to website to the new CMS?
> To: dev@community.apache.org
>
>
> Hi All
>
> At the moment our main website is edited through confluence, auto-exported
> (when the plugin isn't broken...) before going onto the website. However, we
> don't have an easy way to know when changes happen, edits can only occur via
> confluence, and whenever the auto-export plugin sulks we can't edit for a
> bit...
>
> I'd like to suggest that we instead move to the new Apache CMS:
> http://journal.paul.querna.org/articles/2010/10/22/evolution-of-apaches-websites/
>
> This would give us a number of things, including:
> * Instant publish (no more waiting 2 hours)
> * Email notifications of changes
> * Website can be edited both via a friendly CMS, as well as in a text
>  editor
> * More options for site layout and formatting for the future
>
> I've asked a few people here at ApacheCon and got a generally positive
> response to the idea of the change. So, assuming no objections are raised,
> I'll go ahead and do the work to switch us over (getting things setup with
> infra, switching the conflence markup to markdown etc). Please shout if you
> don't want this to go ahead by lazy consensus!
>
> Thanks
> Nick
>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Director & Chief Scientist; Lanka Software Foundation;
> http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2; http://wso2.com/
> Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Member; Sahana Software Foundation; http://www.sahanafoundation.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message