You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by Ross Gardler <rg...@apache.org> on 2010/06/18 11:33:30 UTC
Can't use an open CWIKI for our site
In looking for some hints so that someone can find the cycles to fix the
problem Scott reports with the CWiki export I discovered that our CWiki
is open to any registered user to edit.
This is against ASF policy since we are auto-exporting the CWiki site.
We have a few options:
a) leave the wiki fully open but stop auto exporting it (i.e. maintain a
separate main site using version control and patches to manage it)
b) close off the wiki and continue to use it to manage the main site
c) get CLAs from everyone who wants to edit the docs (ugghh!!!)
d) create a seperate CWiki space that is closed off and used for the
main site whilst leaving another site open to anyone
e) ???
Thoughts?
--
TransferSummit/UK - Open Innovation, Development, Collaboration
Oxford 24-25 June 2010 - Register now! http://www.transfersummit.com
Re: Can't use an open CWIKI for our site
Posted by Ross Gardler <rg...@apache.org>.
On 18/06/2010 10:56, Scott Wilson wrote:
>
> On 18 Jun 2010, at 10:50, Ross Gardler wrote:
>
>> On 18/06/2010 10:38, Gav... wrote:
...
>>>> b) close off the wiki and continue to use it to manage the main site
...
>>> For now I would say b) is the best option.
>>>
>>> Hopefully sometime this year we may get another CMS style option to try out.
>>
>> For what it is worth, I agree. The amount of user generated docs is likely to be low while we have very few active users.
>
> Agreed +1
>
I've done that - it can be quickly reversed if necessary.
Ross
Re: Can't use an open CWIKI for our site
Posted by Scott Wilson <sc...@gmail.com>.
On 18 Jun 2010, at 10:50, Ross Gardler wrote:
> On 18/06/2010 10:38, Gav... wrote:
>>
>>
>>> -----Original Message-----
>>> From: Ross Gardler [mailto:rgardler@apache.org]
>>> Sent: Friday, 18 June 2010 7:34 PM
>>> To: wookie-dev@incubator.apache.org
>>> Subject: Can't use an open CWIKI for our site
>>>
>>> In looking for some hints so that someone can find the cycles to fix
>>> the
>>> problem Scott reports with the CWiki export I discovered that our CWiki
>>> is open to any registered user to edit.
>>>
>>> This is against ASF policy since we are auto-exporting the CWiki site.
>>>
>>> We have a few options:
>>>
>>> a) leave the wiki fully open but stop auto exporting it (i.e. maintain
>>> a
>>> separate main site using version control and patches to manage it)
>>>
>>> b) close off the wiki and continue to use it to manage the main site
>>>
>>> c) get CLAs from everyone who wants to edit the docs (ugghh!!!)
>>>
>>> d) create a seperate CWiki space that is closed off and used for the
>>> main site whilst leaving another site open to anyone
>>>
>>> e) ???
>>>
>>> Thoughts?
>>
>> For now I would say b) is the best option.
>>
>> Hopefully sometime this year we may get another CMS style option to try out.
>
> For what it is worth, I agree. The amount of user generated docs is likely to be low while we have very few active users.
Agreed +1
>
> I'm assuming we can leave comments on and not have them in the export, users can comment.
>
> Role on the Apache CMS it is well overdue (not a complaint, an observation)
>
> Ross
Re: Can't use an open CWIKI for our site
Posted by Ross Gardler <rg...@apache.org>.
On 18/06/2010 10:38, Gav... wrote:
>
>
>> -----Original Message-----
>> From: Ross Gardler [mailto:rgardler@apache.org]
>> Sent: Friday, 18 June 2010 7:34 PM
>> To: wookie-dev@incubator.apache.org
>> Subject: Can't use an open CWIKI for our site
>>
>> In looking for some hints so that someone can find the cycles to fix
>> the
>> problem Scott reports with the CWiki export I discovered that our CWiki
>> is open to any registered user to edit.
>>
>> This is against ASF policy since we are auto-exporting the CWiki site.
>>
>> We have a few options:
>>
>> a) leave the wiki fully open but stop auto exporting it (i.e. maintain
>> a
>> separate main site using version control and patches to manage it)
>>
>> b) close off the wiki and continue to use it to manage the main site
>>
>> c) get CLAs from everyone who wants to edit the docs (ugghh!!!)
>>
>> d) create a seperate CWiki space that is closed off and used for the
>> main site whilst leaving another site open to anyone
>>
>> e) ???
>>
>> Thoughts?
>
> For now I would say b) is the best option.
>
> Hopefully sometime this year we may get another CMS style option to try out.
For what it is worth, I agree. The amount of user generated docs is
likely to be low while we have very few active users.
I'm assuming we can leave comments on and not have them in the export,
users can comment.
Role on the Apache CMS it is well overdue (not a complaint, an observation)
Ross
RE: Can't use an open CWIKI for our site
Posted by "Gav..." <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Ross Gardler [mailto:rgardler@apache.org]
> Sent: Friday, 18 June 2010 7:34 PM
> To: wookie-dev@incubator.apache.org
> Subject: Can't use an open CWIKI for our site
>
> In looking for some hints so that someone can find the cycles to fix
> the
> problem Scott reports with the CWiki export I discovered that our CWiki
> is open to any registered user to edit.
>
> This is against ASF policy since we are auto-exporting the CWiki site.
>
> We have a few options:
>
> a) leave the wiki fully open but stop auto exporting it (i.e. maintain
> a
> separate main site using version control and patches to manage it)
>
> b) close off the wiki and continue to use it to manage the main site
>
> c) get CLAs from everyone who wants to edit the docs (ugghh!!!)
>
> d) create a seperate CWiki space that is closed off and used for the
> main site whilst leaving another site open to anyone
>
> e) ???
>
> Thoughts?
For now I would say b) is the best option.
Hopefully sometime this year we may get another CMS style option to try out.
Gav...
>
> --
> TransferSummit/UK - Open Innovation, Development, Collaboration
> Oxford 24-25 June 2010 - Register now! http://www.transfersummit.com