You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Dirk Verbeeck <di...@pandora.be> on 2004/06/04 22:41:12 UTC
Re: [Wiki SPAM]
A lot of these wiki changes come from apache committers.
Do you think it is possible to tag these changes so we can skip
reviewing these for vandalism?
I don't know the inner workings of the moin wiki system but if we
could separate the changes from committers from the rest it would
certainly reduce the workload.
Something like:
1) put the "Editor:" field in the mail header
2) make sure only apache committers can create wiki accounts with an
apache email address.
- disallow creating apache.org account from the website
- provide a shell script to register a apache.org wiki account
(for users with server access)
This way we can trust the change emails from "Editor: ...@apache.org"
and put those into a separate mail folder.
If we are changing the email header, putting the URL in a mail header
would also be nice ;-)
Does this sounds realistic?
-- Dirk
Noel J. Bergman wrote:
>>Do you think it's helpfull to see an email for EVERY
>>trivial edit in Jakarta_Commons_Wiki ?
>
>
>>I think one message per 24 hours, like one sent by
>>codehaus's confluence would be sufficient.
>
>
> I'm not particularly keen to see wiki vandalism sitting untouched for 24
> hours, or longer if people don't spot it in some lengthy list of unrelated
> changes. However, should someone want to submit a patch that would change
> the wiki code, it could be considered. At the moment, however, there is no
> such option.
>
> --- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Wiki SPAM]
Posted by "matthew.hawthorne" <ma...@apache.org>.
Noel J. Bergman wrote:
>>>Or perhaps we should have a
>>>commons-wiki@jakarta.apache.org list that
>>>committers should subscribe too. Its simple
>>>and keeps these messages out of the archives.
>
>
>>that would be really cool. and CVS-SPAM too...
>
>
> See, when someone starts talking about CVS commit notices as SPAM, I know
> that there is the wrong attitude. No one who is developing Jakarta Commons,
> as opposed to developing WITH Jakarta Commons, should be considering commit
> notices as SPAM. Perhaps there are people on this list who should be on the
> user list, instead.
+1, well put.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Wiki SPAM]
Posted by "Noel J. Bergman" <no...@devtech.com>.
> > Or perhaps we should have a
> > commons-wiki@jakarta.apache.org list that
> > committers should subscribe too. Its simple
> > and keeps these messages out of the archives.
> that would be really cool. and CVS-SPAM too...
See, when someone starts talking about CVS commit notices as SPAM, I know
that there is the wrong attitude. No one who is developing Jakarta Commons,
as opposed to developing WITH Jakarta Commons, should be considering commit
notices as SPAM. Perhaps there are people on this list who should be on the
user list, instead.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Wiki SPAM]
Posted by Konstantin Priblouda <kp...@yahoo.com>.
--- Stephen Colebourne <sc...@btopenworld.com>
wrote:
> Or perhaps we should have a
> commons-wiki@jakarta.apache.org list that
> committers should subscribe too. Its simple and
> keeps these messages out of
> the archives.
that would be really cool. and CVS-SPAM too...
commons is pretty big, and it's dificult to filter
discussions and Q&A from all the automated messages...
regards,
=====
----[ Konstantin Pribluda ( ko5tik ) ]----------------
Zu Verst�rkung meines Teams suche ich ab Sofort einen
Softwareentwickler[In] f�r die Festanstellung.
Arbeitsort: Mainz
Skills: Programieren, Kentnisse in OpenSource-Bereich
----[ http://www.pribluda.de ]------------------------
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Wiki SPAM]
Posted by Stephen Colebourne <sc...@btopenworld.com>.
Or perhaps we should have a commons-wiki@jakarta.apache.org list that
committers should subscribe too. Its simple and keeps these messages out of
the archives.
Stephen
----- Original Message -----
From: "Dirk Verbeeck" <di...@pandora.be>
> A lot of these wiki changes come from apache committers.
> Do you think it is possible to tag these changes so we can skip
> reviewing these for vandalism?
>
> I don't know the inner workings of the moin wiki system but if we
> could separate the changes from committers from the rest it would
> certainly reduce the workload.
>
> Something like:
> 1) put the "Editor:" field in the mail header
> 2) make sure only apache committers can create wiki accounts with an
> apache email address.
> - disallow creating apache.org account from the website
> - provide a shell script to register a apache.org wiki account
> (for users with server access)
>
> This way we can trust the change emails from "Editor: ...@apache.org"
> and put those into a separate mail folder.
>
> If we are changing the email header, putting the URL in a mail header
> would also be nice ;-)
>
> Does this sounds realistic?
>
> -- Dirk
>
> Noel J. Bergman wrote:
> >>Do you think it's helpfull to see an email for EVERY
> >>trivial edit in Jakarta_Commons_Wiki ?
> >
> >
> >>I think one message per 24 hours, like one sent by
> >>codehaus's confluence would be sufficient.
> >
> >
> > I'm not particularly keen to see wiki vandalism sitting untouched for 24
> > hours, or longer if people don't spot it in some lengthy list of
unrelated
> > changes. However, should someone want to submit a patch that would
change
> > the wiki code, it could be considered. At the moment, however, there is
no
> > such option.
> >
> > --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Wiki SPAM]
Posted by Dirk Verbeeck <di...@pandora.be>.
If I see a wiki mail that "rdonkin@apache.org" has updated
"Logging/1.0.4ReleasePlan" then I will look at it differently then if
an unknown user does it.
I thrust Robert more and so I only look at the page at the end of the
week. If an unknown user does an update then I/we should review it asap.
When the LDAP solution is ready the wiki apache account creation
should be automated as well of course.
-- Dirk
Noel J. Bergman wrote:
>>A lot of these wiki changes come from apache committers.
>>Do you think it is possible to tag these changes so we
>>can skip reviewing these for vandalism?
>
>
> Do you skip reviewing CVS commits because they came from a fellow committer?
> I hope people are reviewing changes. And the Wiki changes don't see more
> voluminous than when someone, such as yourself, gets active in CVS.
>
>
>>I don't know the inner workings of the moin wiki system but if we
>>could separate the changes from committers from the rest it would
>>certainly reduce the workload.
>
>
> The wiki has no idea who is a Committer. It does know if someone has
> registered, and we've talked about restricting posts to people who have
> registered.
>
>
>>Something like [...]
>
>
> Please feel free to submit suggestions to the infrastructure team, e.g., by
> create a JIRA issue. I'll note that we are trying to move away from things
> that need a shell account, so creating a new need for one is probably not a
> good approach.
>
> --- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Wiki SPAM]
Posted by "Noel J. Bergman" <no...@devtech.com>.
> A lot of these wiki changes come from apache committers.
> Do you think it is possible to tag these changes so we
> can skip reviewing these for vandalism?
Do you skip reviewing CVS commits because they came from a fellow committer?
I hope people are reviewing changes. And the Wiki changes don't see more
voluminous than when someone, such as yourself, gets active in CVS.
> I don't know the inner workings of the moin wiki system but if we
> could separate the changes from committers from the rest it would
> certainly reduce the workload.
The wiki has no idea who is a Committer. It does know if someone has
registered, and we've talked about restricting posts to people who have
registered.
> Something like [...]
Please feel free to submit suggestions to the infrastructure team, e.g., by
create a JIRA issue. I'll note that we are trying to move away from things
that need a shell account, so creating a new need for one is probably not a
good approach.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Wiki SPAM]
Posted by Dirk Verbeeck <di...@pandora.be>.
That is my only point. I want to use a mail filter separating the
"trusted" changes (from apache committers) from the untrusted (unknown
users).
Both should be reviewed but with a different priority.
Just my €0.02.
-- Dirk
Martin Cooper wrote:
>
>>-----Original Message-----
>>From: Dirk Verbeeck [mailto:dirk.verbeeck@pandora.be]
>>Sent: Friday, June 04, 2004 1:41 PM
>>To: Jakarta Commons Developers List
>>Subject: Re: [Wiki SPAM]
>>
>>
>>A lot of these wiki changes come from apache committers.
>>Do you think it is possible to tag these changes so we can skip
>>reviewing these for vandalism?
>
>
> But I want to see all of the changes to the wiki. I want to see the ones
> from committers, because that's just like peer review of the code base, as
> Noel suggested. I learn from that as much as anything. And I want to see
> changes from other folks to see who's contributing what.
>
> If wiki changes didn't result in notifications, I don't know how I'd ever
> track what goes on on the wiki. It's not like I'd go surf the entire wiki
> periodically to see what new content has shown up.
>
> The only kinds of changes that I don't really want to see are from the
> people who haven't quite grokked wikis yet. They go make some stupid change,
> commit it to see if they can, and then immediately back out the change. And
> then there are some people who haven't figured out Preview yet, and so make
> a long series of minor edits after a major one. But the delete key takes
> care of those quickly enough.
>
> IMHO, what we have works just fine. Just bring the right tools (mail filters
> and the delete key) to bear, and there isn't a problem.
>
> --
> Martin Cooper
>
>
>
>>I don't know the inner workings of the moin wiki system but if we
>>could separate the changes from committers from the rest it would
>>certainly reduce the workload.
>>
>>Something like:
>>1) put the "Editor:" field in the mail header
>>2) make sure only apache committers can create wiki accounts with an
>>apache email address.
>> - disallow creating apache.org account from the website
>> - provide a shell script to register a apache.org wiki account
>> (for users with server access)
>>
>>This way we can trust the change emails from "Editor: ...@apache.org"
>>and put those into a separate mail folder.
>>
>>If we are changing the email header, putting the URL in a mail header
>>would also be nice ;-)
>>
>>Does this sounds realistic?
>>
>>-- Dirk
>>
>>Noel J. Bergman wrote:
>>
>>>>Do you think it's helpfull to see an email for EVERY
>>>>trivial edit in Jakarta_Commons_Wiki ?
>>>
>>>
>>>>I think one message per 24 hours, like one sent by
>>>>codehaus's confluence would be sufficient.
>>>
>>>
>>>I'm not particularly keen to see wiki vandalism sitting untouched for 24
>>>hours, or longer if people don't spot it in some lengthy list
>>
>>of unrelated
>>
>>>changes. However, should someone want to submit a patch that
>>
>>would change
>>
>>>the wiki code, it could be considered. At the moment, however,
>>
>>there is no
>>
>>>such option.
>>>
>>> --- Noel
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Wiki SPAM]
Posted by Martin Cooper <ma...@apache.org>.
> -----Original Message-----
> From: Dirk Verbeeck [mailto:dirk.verbeeck@pandora.be]
> Sent: Friday, June 04, 2004 1:41 PM
> To: Jakarta Commons Developers List
> Subject: Re: [Wiki SPAM]
>
>
> A lot of these wiki changes come from apache committers.
> Do you think it is possible to tag these changes so we can skip
> reviewing these for vandalism?
But I want to see all of the changes to the wiki. I want to see the ones
from committers, because that's just like peer review of the code base, as
Noel suggested. I learn from that as much as anything. And I want to see
changes from other folks to see who's contributing what.
If wiki changes didn't result in notifications, I don't know how I'd ever
track what goes on on the wiki. It's not like I'd go surf the entire wiki
periodically to see what new content has shown up.
The only kinds of changes that I don't really want to see are from the
people who haven't quite grokked wikis yet. They go make some stupid change,
commit it to see if they can, and then immediately back out the change. And
then there are some people who haven't figured out Preview yet, and so make
a long series of minor edits after a major one. But the delete key takes
care of those quickly enough.
IMHO, what we have works just fine. Just bring the right tools (mail filters
and the delete key) to bear, and there isn't a problem.
--
Martin Cooper
>
> I don't know the inner workings of the moin wiki system but if we
> could separate the changes from committers from the rest it would
> certainly reduce the workload.
>
> Something like:
> 1) put the "Editor:" field in the mail header
> 2) make sure only apache committers can create wiki accounts with an
> apache email address.
> - disallow creating apache.org account from the website
> - provide a shell script to register a apache.org wiki account
> (for users with server access)
>
> This way we can trust the change emails from "Editor: ...@apache.org"
> and put those into a separate mail folder.
>
> If we are changing the email header, putting the URL in a mail header
> would also be nice ;-)
>
> Does this sounds realistic?
>
> -- Dirk
>
> Noel J. Bergman wrote:
> >>Do you think it's helpfull to see an email for EVERY
> >>trivial edit in Jakarta_Commons_Wiki ?
> >
> >
> >>I think one message per 24 hours, like one sent by
> >>codehaus's confluence would be sufficient.
> >
> >
> > I'm not particularly keen to see wiki vandalism sitting untouched for 24
> > hours, or longer if people don't spot it in some lengthy list
> of unrelated
> > changes. However, should someone want to submit a patch that
> would change
> > the wiki code, it could be considered. At the moment, however,
> there is no
> > such option.
> >
> > --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org