You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrunit.apache.org by Jim Donofrio <do...@gmail.com> on 2012/03/28 13:29:39 UTC
apache cms
What are the thoughts on going over to the Apache CMS for the website.
From reading the docs it sounds as this is the recommended way to go
for a website. There is also a easy editor that you access right through
your browser which would make the wiki unnecessary which I think is a
good thing to avoid having docs in too many places.
http://www.apache.org/dev/cmsref.html#svn
Unless there is any dissent, I was going to follow the above info on
setting up a place in our svn for the site and putting the INFRA JIRA in
to request them to set us up a staging area.
Re: apache cms
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
I would be +1 for the CMS. It's supported by infra@ so there is always help there
and we can still use our favorite content formats (e.g., Markdown, whatever) to
edit the site.
Cheers,
Chris
On Mar 28, 2012, at 4:29 AM, Jim Donofrio wrote:
> What are the thoughts on going over to the Apache CMS for the website.
> From reading the docs it sounds as this is the recommended way to go
> for a website. There is also a easy editor that you access right through
> your browser which would make the wiki unnecessary which I think is a
> good thing to avoid having docs in too many places.
>
> http://www.apache.org/dev/cmsref.html#svn
> Unless there is any dissent, I was going to follow the above info on
> setting up a place in our svn for the site and putting the INFRA JIRA in
> to request them to set us up a staging area.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: apache cms
Posted by Brock Noland <br...@cloudera.com>.
Yeah I forgot about that. +1
On Wed, Mar 28, 2012 at 6:36 AM, Jarek Jarcec Cecho <ja...@apache.org> wrote:
> +1
>
> I'm definitely in favour of such idea.
>
> Jarcec
>
> On Wed, Mar 28, 2012 at 07:29:39AM -0400, Jim Donofrio wrote:
>> What are the thoughts on going over to the Apache CMS for the
>> website. From reading the docs it sounds as this is the recommended
>> way to go for a website. There is also a easy editor that you access
>> right through your browser which would make the wiki unnecessary
>> which I think is a good thing to avoid having docs in too many
>> places.
>>
>> http://www.apache.org/dev/cmsref.html#svn
>> Unless there is any dissent, I was going to follow the above info on
>> setting up a place in our svn for the site and putting the INFRA
>> JIRA in to request them to set us up a staging area.
--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
Re: apache cms
Posted by Jarek Jarcec Cecho <ja...@apache.org>.
+1
I'm definitely in favour of such idea.
Jarcec
On Wed, Mar 28, 2012 at 07:29:39AM -0400, Jim Donofrio wrote:
> What are the thoughts on going over to the Apache CMS for the
> website. From reading the docs it sounds as this is the recommended
> way to go for a website. There is also a easy editor that you access
> right through your browser which would make the wiki unnecessary
> which I think is a good thing to avoid having docs in too many
> places.
>
> http://www.apache.org/dev/cmsref.html#svn
> Unless there is any dissent, I was going to follow the above info on
> setting up a place in our svn for the site and putting the INFRA
> JIRA in to request them to set us up a staging area.