incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <robw...@apache.org>
Subject Re: Feedback on the CMS
Date Sun, 13 May 2012 16:16:48 GMT
On Fri, May 11, 2012 at 4:23 PM, Joe Schaefer <joe_schaefer@yahoo.com> wrote:
> ----- Original Message -----
>
>> From: Rob Weir <robweir@apache.org>
>> To: ooo-dev@incubator.apache.org; Joe Schaefer <joe_schaefer@yahoo.com>
>> Cc:
>> Sent: Friday, May 11, 2012 2:32 PM
>> Subject: Re: Feedback on the CMS
>>
>> On Fri, May 11, 2012 at 2:18 PM, Joe Schaefer <joe_schaefer@yahoo.com>
>> wrote:
>>>  With 1100 builds so far the ooo-site CMS instance
>>>  is only 350 builds behind www.apache.org as the
>>>  most-used CMS tree so far.  I monitor the CMS logs
>>>  daily to evaluate usage and this project publishes
>>>  about as often as all our other projects combined,
>>>  which really makes me wonder where we'd be here if
>>>  the org had never created the CMS in the first place.
>>>
>>
>> Wow.  Impressive stats.  I know I use it nearly on a daily basis.
>>
>>>
>>>  The ooo-site is far and away the largest instance at
>>>  over 9GB total.  The reason I'm writing here is to
>>>  ask general questions about user satisfaction with
>>>  the CMS:
>>>
>>>  1) Is there any aspect of the CMS that needs immediate
>>>     improvement?
>>>
>>
>> It works for me.
>>
>>
>>>  2) Are you satisfied with the workflow, or are there areas
>>>     that could stand improvement?
>>>
>>
>> For the novice, it would be useful to have more guidance text on what
>> to do next.   So maybe a streamlined "easy" interface, and then the
>> full version.
>
> Ok, thanks.  I dunno about a steamlined interface, but more inline
> documentation is probably called for.
>

That could help.  Or even a video tutorial/walk-through of the
interface, via Feathercast.

>>
>>
>>>  3) Is there anything that should be done to encourage more
>>>     users who are not committers to use the CMS to submit patches
>>>     to the list?
>>>
>>
>> There is a live markdown preview of changes, but none given for HTML
>> pages.  Since most of the openoffice.org site is still HTML, this
>> would be very useful and help catch errors before staging.
>
> There are security implications about using a project's rendering code
> within the CMS- it complicates things well beyond my threshold for that
> sort of thing.  When all else fails the Static view will render the core
> HTML natively with many of the linkages preserved, so you'll at least get
> some idea from that how things will look on staging post-build.
>
>
>>
>>>  4) Are there any UI features you'd like to see implemented,
>>>     either in the web interface or the publication script?
>>>
>>
>> In the web interface, something that would poll the build and
>> automatically refresh to the staging server when the build is
>> complete.
>
> Perhaps- I just added a similar feature to the publication script,
> and yes I'm having a hard time convincing users to pay attention
> to the build results before trying to publish.
>
> Thanks for the responses Rob!
>

Mime
View raw message