www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Wechner <michael.wech...@wyona.com>
Subject Re: collecting CMS requirements
Date Mon, 13 Sep 2010 07:31:27 GMT
Joe Schaefer wrote:
> I've asked Gav to set up cms.apache.org for us to use for this
> purpose.  I'm happy to arrange for access to that host for anyone
> who is interested in helping administer it. 

thanks, I would like to have access

>  This should only be
> necessary for people who want to deal with the software or admin
> aspects, not people willing to write content or just test and
> provide feedback to what we're doing.
>
> I'd like to have a mockup ready for use by Apachecon, something
> that has most of the basic features and is capable of generating
> a staged version of the apache.org homepage and a few other select
> pages.  Keep in mind tho that intstant publication is a non-goal
> for this project: if we can cut the time from editing to publication
> from 1-2 hours currently to a few minutes I'll consider that a
> success.  All the work on the prototype will be done at
>
> https://svn.apache.org/repos/infra/infrastructure/trunk/projects/cms
>   

checkout worked for me.

Is this prototype working yet? If so, how can it be deployed/installed/used?

Thanks

Michael
> and anyone who wants to pitch in is welcome to.  If you don't have
> access yet just holler.
>
>
>
>
> ----- Original Message ----
>   
>> From: Joe Schaefer <joe_schaefer@yahoo.com>
>> To: site-dev@apache.org
>> Sent: Fri, September 10, 2010 12:58:09 AM
>> Subject: Re: collecting CMS requirements
>>
>> ----- Original Message ----
>>
>>     
>>> From: Henri Yandell <bayard@apache.org>
>>> To: site-dev@apache.org
>>> Sent: Fri,  September 3, 2010 12:47:55 AM
>>> Subject: Re: collecting CMS  requirements
>>>
>>> Main thoughts:
>>>
>>> * Need to replace  'svn diff' so it's easy to see what's  changed and do
>>> a review.  While it's annoying to have the nav affect lots of  pages,
>>> it's  very easy to make sure the modification is restricted to the  nav
>>>  change. Also 'svn status' to show the summary of the change.
>>>       
>> By using  markdown for most content svn diff becomes useful again.
>>
>>     
>>> *  Support  local development of the website; shouldn't need to  connect
>>> to some server to  work on changes.
>>>       
>> Covered.   Everything will be in a subversion tree to whittle on.
>>
>>     
>>> * Ideally  still support the command-line world where a  scripts, perl
>>> -pi,  grep and other goodness can still allow for large change  work.
>>>  This raises questions on the notion that a site gen wouldn't   happen
>>> until after commit.
>>>       
>> Two things.  First large changes  should probably happen in a branch,
>> which will get automatically built and  staged somewhere for inspection.
>> Second, the site generation utils will of  course be apache licensed scripts,
>> so if you want to do a build of the site  *before* checking in your work,
>> and your cpan fu is up to the task, it should  be doable.  It's just no
>> longer going to be a requirement.
>>
>>     
>>> *  Bear in mind the solution should be reusable  for other sites; the
>>>  anakia approach is also used on other Apache sites  (Attic is an
>>>  example where it even pulls in the anakia system from the main   site
>>> via svn externals).
>>>       
>> Covered.  Any templating language  that has a perl port should be
>> available.
>>
>>     
>>> Obvious, but  not listed yet:
>>>
>>> * Full  audit history of who changed  what.
>>> * Notifications of changes.
>>> * Be  prepared for  complaints if existing editors have to move from one
>>> templating   system to another. For templating, I'd suggest a
>>> sub-requirements  be  investigated. What's bad with the current
>>> templating system,  what is desired  but not implemented (or impossible
>>> to  implement).
>>>
>>> Hen
>>>
>>> On Thu,  Sep 2, 2010 at  5:03 AM, Joe Schaefer <joe_schaefer@yahoo.com>
  
>>>       
>> wrote:
>>     
>>>> As mentioned elsewhere we're looking for
>>>>  requirements for  an Apache CMS capable of
>>>> replacing our  confluence usage.  I've  collected
>>>> a few ideas  here:
>>>>
>>>>
>>>>         
> https://svn.apache.org/repos/infra/infrastructure/trunk/projects/cms/README
>   
>>>  >
>>>       
>>>>  Please comment here with your ideas or commit
>>>>         
>>>  > away to the above  file.
>>>       
>>>>         
>>>  >
>>>       
>>       
>>
>>     
>
>
>       
>   


Mime
View raw message