Reconsider moving to Apache CMS only? [Was: Confluence Wiki SPAM and new restrictions in place.]

[Isabel Drost-Fromm <is...@apache.org>]

Hi,

this topic popped up a couple of times in the past - given the current spam 
incident in the Apache confluence wikis, a few more restrictions were put into 
place for editing pages in the wiki:

> removed any editing access for the confluence-users group. From now on, if
> someone wants to edit your wiki, you have to whitelist them specifically. You
> can do this if they are a committer by listing them in the 'Individual
> Users' section of the Space Permissions area, or by asking that they be
> added to the special 'asf-cla' wiki group - we will check that they have a
> iCLA on file before adding them.

Given the need to whitelist everyone who wants to do changes to the wiki pages 
I wonder whether it makes sense to move most of our docs over to Apache CMS 
(except maybe for the most volatile pages, if there are any). 

The obvious disadvantage would be a higher barrier of entry for people 
providing docs (though prior to being whitelisted one would have to express 
the intent to provide improvments on the mailing list anyway). The advantage 
could be a clearer path towards committership for those not working on code 
but on technical writing.

The only question concerning the move to Apache CMS I have: How easy is it to 
provide documentation for individtual released versions? Would it be possible 
to e.g. bundle the then current docs with the release?


Isabel

Re: Reconsider moving to Apache CMS only? [Was: Confluence Wiki SPAM and new restrictions in place.]

[Ted Dunning <te...@gmail.com>]

There has been quite a bit of talk about wiki spam and I think that they
serious locked down access.




On Tue, Oct 8, 2013 at 12:55 PM, Dmitriy Lyubimov <dl...@gmail.com> wrote:

> So the white listing is already in effect? i seem to have lost wiki editing
> privilege.
>
>
> On Fri, Oct 4, 2013 at 1:52 AM, Isabel Drost-Fromm <isabel@apache.org
> >wrote:
>
> > On Thursday, October 03, 2013 03:30:26 PM Grant Ingersoll wrote:
> > > I like what we do over in Solr land, an official reference guide that
> is
> > > maintained by committers + patches and then a wiki which allows free
> > > editing (for the most part).  Things generally move from the wiki to
> the
> > > Ref guide.
> >
> > +1 - sounds like a very good concept.
> >
> > > > The only question concerning the move to Apache CMS I have: How easy
> > is it
> > > > to provide documentation for individtual released versions? Would it
> be
> > > > possible to e.g. bundle the then current docs with the release?
> > >
> > > It's all in SVN and is usually markdown.  Tag it and ship it!
> >
> >
> > Awesome!
> >
> >
> > Isabel
> >
> >
>

Re: Reconsider moving to Apache CMS only? [Was: Confluence Wiki SPAM and new restrictions in place.]

[Dmitriy Lyubimov <dl...@gmail.com>]

So the white listing is already in effect? i seem to have lost wiki editing
privilege.


On Fri, Oct 4, 2013 at 1:52 AM, Isabel Drost-Fromm <is...@apache.org>wrote:

> On Thursday, October 03, 2013 03:30:26 PM Grant Ingersoll wrote:
> > I like what we do over in Solr land, an official reference guide that is
> > maintained by committers + patches and then a wiki which allows free
> > editing (for the most part).  Things generally move from the wiki to the
> > Ref guide.
>
> +1 - sounds like a very good concept.
>
> > > The only question concerning the move to Apache CMS I have: How easy
> is it
> > > to provide documentation for individtual released versions? Would it be
> > > possible to e.g. bundle the then current docs with the release?
> >
> > It's all in SVN and is usually markdown.  Tag it and ship it!
>
>
> Awesome!
>
>
> Isabel
>
>

Re: Reconsider moving to Apache CMS only? [Was: Confluence Wiki SPAM and new restrictions in place.]

[Isabel Drost-Fromm <is...@apache.org>]

On Thursday, October 03, 2013 03:30:26 PM Grant Ingersoll wrote:
> I like what we do over in Solr land, an official reference guide that is
> maintained by committers + patches and then a wiki which allows free
> editing (for the most part).  Things generally move from the wiki to the
> Ref guide.

+1 - sounds like a very good concept. 

> > The only question concerning the move to Apache CMS I have: How easy is it
> > to provide documentation for individtual released versions? Would it be
> > possible to e.g. bundle the then current docs with the release?
> 
> It's all in SVN and is usually markdown.  Tag it and ship it!


Awesome!


Isabel

Re: Reconsider moving to Apache CMS only? [Was: Confluence Wiki SPAM and new restrictions in place.]

[Grant Ingersoll <gs...@apache.org>]

On Oct 2, 2013, at 7:36 AM, Isabel Drost-Fromm <is...@apache.org> wrote:

> 
> Hi,
> 
> this topic popped up a couple of times in the past - given the current spam 
> incident in the Apache confluence wikis, a few more restrictions were put into 
> place for editing pages in the wiki:
> 
>> removed any editing access for the confluence-users group. From now on, if
>> someone wants to edit your wiki, you have to whitelist them specifically. You
>> can do this if they are a committer by listing them in the 'Individual
>> Users' section of the Space Permissions area, or by asking that they be
>> added to the special 'asf-cla' wiki group - we will check that they have a
>> iCLA on file before adding them.
> 
> Given the need to whitelist everyone who wants to do changes to the wiki pages 
> I wonder whether it makes sense to move most of our docs over to Apache CMS 
> (except maybe for the most volatile pages, if there are any). 

I think it does make sense.

> 
> The obvious disadvantage would be a higher barrier of entry for people 
> providing docs (though prior to being whitelisted one would have to express 
> the intent to provide improvments on the mailing list anyway). The advantage 
> could be a clearer path towards committership for those not working on code 
> but on technical writing.

I like what we do over in Solr land, an official reference guide that is maintained by committers + patches and then a wiki which allows free editing (for the most part).  Things generally move from the wiki to the Ref guide.

> 
> The only question concerning the move to Apache CMS I have: How easy is it to 
> provide documentation for individtual released versions? Would it be possible 
> to e.g. bundle the then current docs with the release?

It's all in SVN and is usually markdown.  Tag it and ship it!