Everyone seems to like this. I see no reason for a formal vote.

If people would be so kind to update or create confluence content,
when we have a critical mass I can organize the switcheroo.

On Sat, Oct 16, 2010 at 7:45 AM, Colm O hEigeartaigh
<[email protected]> wrote:
> Another +1 from me. What about the webpages of the constituent
> projects? For example, WSS4J has its own Forrest generated webpage.
> Maybe this should be merged with the new WS confluence page as well?
>
> Colm.
>
> On Fri, Oct 15, 2010 at 8:25 PM, Andreas Veithen
> <[email protected]> wrote:
>> +1 for Confluence.
>>
>> I know more or less how the Confluence auto-export stuff works, but
>> there are two technical questions that are not clear to me:
>>
>> 1. Where and how are the export templates maintained?
>> 2. How is the exported content (https://cwiki.apache.org/WS) going to
>> be published to http://ws.apache.org and how will we manage the fact
>> that some subprojects continue to use generated (Maven) sites?
>>
>> Andreas
>>
>> On Fri, Oct 15, 2010 at 17:03, Daniel Kulp <[email protected]> wrote:
>>>
>>> I'm definitely +1.   Forrest sucks.   :-)
>>>
>>> On Friday 15 October 2010 11:00:32 am Benson Margulies wrote:
>>>> We've got 1.5 web sites here.
>>>>
>>>> There's
>>>>
>>>> http://ws.apache.org
>>>>
>>>> which is very stale, and 'maintained' using Apache Forrest, which
>>>> isn't, well, maintained, and has no release that works with Java 1.6.
>>>>
>>>> Then we've got:
>>>>
>>>> https://cwiki.apache.org/confluence/display/WS/Index
>>>>
>>>> which is more up to date, but needs to be exported (in place of the
>>>> above) to be useful.
>>>
>>> Well, it's already being exported:
>>>
>>> https://cwiki.apache.org/WS
>>>
>>> but the template definitely needs a lot of work. As does the content.    But
>>> the content needs work in the forest site as well and I think editing the
>>> Confluence content is much easier.
>>>
>>> Dan
>>>
>>>
>>>
>>>> I'll give this idea a day or two for discussion, and, barring giant
>>>> problems, put it to a vote.
>>>
>>> --
>>> Daniel Kulp
>>> [email protected]
>>> http://dankulp.com/blog
>>>
>>
>

Reply via email to