You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Greg Trasuk <tr...@stratuscom.com> on 2013/03/20 17:13:43 UTC
Rivier Wiki Admin
OK, so I had word back from Infra@ on our wiki spam issues.
What their docs recommend is that we lock down the edits to authorized
users. To do that, I need two lists - First we need the Wiki names of
at least two of us who are willing to act as administrators on the
wiki. This will be the AdminGroup. I'll volunteer, we should have at
least one more, and the more the merrier. Second, we will have a list
of contributors' wiki names. These people will have authorization to
add and edit pages.
Essentially, from here on, the procedure will be that someone new who
wants to contribute to the wiki will register on the River Wiki, thus
creating a wiki name for themselves. Then they will drop a line on
dev@river.apache.org saying "Please enable me for contributions".
Obviously we could set policy on who to authorize, but basically most
projects just grant permission as soon as it's requested - it's not a
voting thing like committership. Then one of the members of the
AdminGroup goes and edits the ContributorsGroup wiki page. The
assumption is that a spammer won't ask for permission to spam. If
someone does post specious content, then we can remove them from the
ContributorsGroup.
So if you could provide your Wiki names for the AdminGroup and
ContributorsGroup, I'll get the process rolling with infra@.
Thanks,
Greg.
--
Greg Trasuk, President
StratusCom Manufacturing Systems Inc. - We use information technology to
solve business problems on your plant floor.
http://stratuscom.com
Re: Rivier Wiki Admin
Posted by Greg Trasuk <tr...@stratuscom.com>.
https://issues.apache.org/jira/browse/INFRA-6077
On Tue, 2013-03-26 at 02:33, Peter Firmstone wrote:
> Peter wrote:
> >>> OK, so I had word back from Infra@ on our wiki spam issues.
> >>>
> >>> What their docs recommend is that we lock down the edits to authorized
> >>> users. To do that, I need two lists - First we need the Wiki names of
> >>> at least two of us who are willing to act as administrators on the
> >>> wiki. This will be the AdminGroup. I'll volunteer, we should have at
> >>> least one more, and the more the merrier. Second, we will have a list
> >>> of contributors' wiki names. These people will have authorization to
> >>> add and edit pages.
> >>>
> PeterFirmstone is my wiki user name, if no one else puts up their hand,
> I'll be an admin.
>
> Regards,
>
> Peter.
>
> >>> Essentially, from here on, the procedure will be that someone new who
> >>> wants to contribute to the wiki will register on the River Wiki, thus
> >>> creating a wiki name for themselves. Then they will drop a line on
> >>> dev@river.apache.org saying "Please enable me for contributions".
> >>> Obviously we could set policy on who to authorize, but basically most
> >>> projects just grant permission as soon as it's requested - it's not a
> >>> voting thing like committership. Then one of the members of the
> >>> AdminGroup goes and edits the ContributorsGroup wiki page. The
> >>> assumption is that a spammer won't ask for permission to spam. If
> >>> someone does post specious content, then we can remove them from the
> >>> ContributorsGroup.
> >>>
> >>> So if you could provide your Wiki names for the AdminGroup and
> >>> ContributorsGroup, I'll get the process rolling with infra@.
> >>>
> >>> Thanks,
> >>>
> >>> Greg.
> >>>
> >>> --
> >>> Greg Trasuk, President
> >>> StratusCom Manufacturing Systems Inc. - We use information technology to
> >>> solve business problems on your plant floor.
> >>> http://stratuscom.com
> >>>
> >>>
> >
> >
> >
Re: Rivier Wiki Admin
Posted by Peter Firmstone <ji...@zeus.net.au>.
Peter wrote:
>>> OK, so I had word back from Infra@ on our wiki spam issues.
>>>
>>> What their docs recommend is that we lock down the edits to authorized
>>> users. To do that, I need two lists - First we need the Wiki names of
>>> at least two of us who are willing to act as administrators on the
>>> wiki. This will be the AdminGroup. I'll volunteer, we should have at
>>> least one more, and the more the merrier. Second, we will have a list
>>> of contributors' wiki names. These people will have authorization to
>>> add and edit pages.
>>>
PeterFirmstone is my wiki user name, if no one else puts up their hand,
I'll be an admin.
Regards,
Peter.
>>> Essentially, from here on, the procedure will be that someone new who
>>> wants to contribute to the wiki will register on the River Wiki, thus
>>> creating a wiki name for themselves. Then they will drop a line on
>>> dev@river.apache.org saying "Please enable me for contributions".
>>> Obviously we could set policy on who to authorize, but basically most
>>> projects just grant permission as soon as it's requested - it's not a
>>> voting thing like committership. Then one of the members of the
>>> AdminGroup goes and edits the ContributorsGroup wiki page. The
>>> assumption is that a spammer won't ask for permission to spam. If
>>> someone does post specious content, then we can remove them from the
>>> ContributorsGroup.
>>>
>>> So if you could provide your Wiki names for the AdminGroup and
>>> ContributorsGroup, I'll get the process rolling with infra@.
>>>
>>> Thanks,
>>>
>>> Greg.
>>>
>>> --
>>> Greg Trasuk, President
>>> StratusCom Manufacturing Systems Inc. - We use information technology to
>>> solve business problems on your plant floor.
>>> http://stratuscom.com
>>>
>>>
>
>
>
Re: Rivier Wiki Admin
Posted by Peter <ji...@zeus.net.au>.
Yes definitely, River's wiki's presently experiencing a moron bombardment, it's probably worth waiting until that's sorted first.
Thanks,
Peter.
----- Original message -----
> CeesDeGroot
>
> BTW - I still have a backup of the Jini wiki I ran for a while. It was
> also running on MoinMoin,
> so at least the formatting should be the same ;-).
>
> Is it useful to add that content to the River wiki?
>
> (http://web.archive.org/web/*/http://www.cdegroot.com/cgi-bin/jini - note
> that later in its lifetime, a lot of spam got added)
>
> On 2013-03-20 5:13 PM, "Greg Trasuk" <tr...@stratuscom.com> wrote:
>
> > OK, so I had word back from Infra@ on our wiki spam issues.
> >
> > What their docs recommend is that we lock down the edits to authorized
> > users. To do that, I need two lists - First we need the Wiki names of
> > at least two of us who are willing to act as administrators on the
> > wiki. This will be the AdminGroup. I'll volunteer, we should have at
> > least one more, and the more the merrier. Second, we will have a list
> > of contributors' wiki names. These people will have authorization to
> > add and edit pages.
> >
> > Essentially, from here on, the procedure will be that someone new who
> > wants to contribute to the wiki will register on the River Wiki, thus
> > creating a wiki name for themselves. Then they will drop a line on
> > dev@river.apache.org saying "Please enable me for contributions".
> > Obviously we could set policy on who to authorize, but basically most
> > projects just grant permission as soon as it's requested - it's not a
> > voting thing like committership. Then one of the members of the
> > AdminGroup goes and edits the ContributorsGroup wiki page. The
> > assumption is that a spammer won't ask for permission to spam. If
> > someone does post specious content, then we can remove them from the
> > ContributorsGroup.
> >
> > So if you could provide your Wiki names for the AdminGroup and
> > ContributorsGroup, I'll get the process rolling with infra@.
> >
> > Thanks,
> >
> > Greg.
> >
> > --
> > Greg Trasuk, President
> > StratusCom Manufacturing Systems Inc. - We use information technology to
> > solve business problems on your plant floor.
> > http://stratuscom.com
> >
>
Re: Rivier Wiki Admin
Posted by "De Groot, Cees" <cd...@marktplaats.nl>.
CeesDeGroot
BTW - I still have a backup of the Jini wiki I ran for a while. It was
also running on MoinMoin,
so at least the formatting should be the same ;-).
Is it useful to add that content to the River wiki?
(http://web.archive.org/web/*/http://www.cdegroot.com/cgi-bin/jini - note
that later in its lifetime, a lot of spam got added)
On 2013-03-20 5:13 PM, "Greg Trasuk" <tr...@stratuscom.com> wrote:
>OK, so I had word back from Infra@ on our wiki spam issues.
>
>What their docs recommend is that we lock down the edits to authorized
>users. To do that, I need two lists - First we need the Wiki names of
>at least two of us who are willing to act as administrators on the
>wiki. This will be the AdminGroup. I'll volunteer, we should have at
>least one more, and the more the merrier. Second, we will have a list
>of contributors' wiki names. These people will have authorization to
>add and edit pages.
>
>Essentially, from here on, the procedure will be that someone new who
>wants to contribute to the wiki will register on the River Wiki, thus
>creating a wiki name for themselves. Then they will drop a line on
>dev@river.apache.org saying "Please enable me for contributions".
>Obviously we could set policy on who to authorize, but basically most
>projects just grant permission as soon as it's requested - it's not a
>voting thing like committership. Then one of the members of the
>AdminGroup goes and edits the ContributorsGroup wiki page. The
>assumption is that a spammer won't ask for permission to spam. If
>someone does post specious content, then we can remove them from the
>ContributorsGroup.
>
>So if you could provide your Wiki names for the AdminGroup and
>ContributorsGroup, I'll get the process rolling with infra@.
>
>Thanks,
>
>Greg.
>
>--
>Greg Trasuk, President
>StratusCom Manufacturing Systems Inc. - We use information technology to
>solve business problems on your plant floor.
>http://stratuscom.com
>