You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by "William A. Rowe, Jr." <wr...@rowe-clan.net> on 2007/05/24 08:56:19 UTC

[Issue] External links @ the wiki, aka pagechange wars

We have a serious issue to determine, and I've asked for a 48 hour cooldown
of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
the wiki become read-only for the conclusion of this decision.

 [  ] Our httpd wiki is open to external resources for httpd.
 [  ] External httpd resources are prohibited.

I mean this explicitly, obviously a link to MS/Sun/RedHat about their
specific platform would be genuinely useful and relevant.

I'm asking about askapache's external links, which have not been actually
contributed to the foundation.  And we've never presumed that pointers to
external links are resources under the AL.

AskApache and megaspaz decided to start a pagechange war tonight, but the
first point is to decide if such external 'helpful pages' are welcome.

If so, AskApache was in the right, if not, megaspaz is right.  Either way,
I immediately asked for infra to shutter the wiki to write access until this
was resolved as a matter of POLICY.

Once we determine a policy, I belive we owe megaspaz and AskApache a second
chance once they are informed of the definative policy.

Future wiki abuse would, of course, lead to account and IP blockage.  But
I believe at this moment both acted in best-faith without any guidance from
our project, and we need to have policies so folks can be responsible wiki
users.

This isn't the end-all of all possibilities, but let's discuss for 2 days
and reopen the wiki with a concrete policy?

Bill



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Jorge Schrauwen <jo...@gmail.com>.
William A. Rowe, Jr. wrote:
> We have a serious issue to determine, and I've asked for a 48 hour cooldown
> of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> the wiki become read-only for the conclusion of this decision.
>
>  [  ] Our httpd wiki is open to external resources for httpd.
>  [X] External httpd resources are prohibited.
>
> I mean this explicitly, obviously a link to MS/Sun/RedHat about their
> specific platform would be genuinely useful and relevant.

Not that I really have a vote but I'll still reply since my input
might be appreciated.
We don't have controle over external content...
Page can be remove, or updated etc without us knowing. So I think its
better to not link to external resources.

I'd like to ask a question concerning this also:
What about profiles? Most contributers have a little page telling
about themselfs and linking to there homepage/blog/... how would this
fit in?

-- 
~Jorge

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Vincent Bray <no...@gmail.com>.
On 24/05/07, Mads Toftum <ma...@toftum.dk> wrote:
> +1 - I don't think a single users abuse should force us into making a
> catch all policy. Part of the price of running a wiki is that you'll
> have to deal with abuse from time to time.

I also agree with all of Rich's sentiments, but I feel a policy
document would help, just to have something to point to when dealing
with this guy in particular. Without it or some recognised kind of
forum for wiki discussions (I'm not sure docs@httpd counts as that)
we're just back to this kind of commitwar.

-- 
noodl

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Vincent Bray <no...@gmail.com>.
On 24/05/07, Mads Toftum <ma...@toftum.dk> wrote:
> +1 - I don't think a single users abuse should force us into making a
> catch all policy. Part of the price of running a wiki is that you'll
> have to deal with abuse from time to time.

I also agree with all of Rich's sentiments, but I feel a policy
document would help, just to have something to point to when dealing
with this guy in particular. Without it or some recognised kind of
forum for wiki discussions (I'm not sure docs@httpd counts as that)
we're just back to this kind of commitwar.

-- 
noodl

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Mads Toftum <ma...@toftum.dk>.
On Thu, May 24, 2007 at 10:14:23AM -0400, Rich Bowen wrote:
> NOTE: NOT because external links are bad, but because the articles to  
> which he was linking were misleading, incorrect, and promoted sub- 
> optimal solutions to common problems. The implied endorsement (The  
> Apache docs link to this article, so it must be true) was  
> unfortunate, and undesirable.
> 
+1 - I don't think a single users abuse should force us into making a
catch all policy. Part of the price of running a wiki is that you'll
have to deal with abuse from time to time.

vh

Mads Toftum
-- 
http://soulfood.dk

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Mads Toftum <ma...@toftum.dk>.
On Thu, May 24, 2007 at 10:14:23AM -0400, Rich Bowen wrote:
> NOTE: NOT because external links are bad, but because the articles to  
> which he was linking were misleading, incorrect, and promoted sub- 
> optimal solutions to common problems. The implied endorsement (The  
> Apache docs link to this article, so it must be true) was  
> unfortunate, and undesirable.
> 
+1 - I don't think a single users abuse should force us into making a
catch all policy. Part of the price of running a wiki is that you'll
have to deal with abuse from time to time.

vh

Mads Toftum
-- 
http://soulfood.dk

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Jorge Schrauwen <jo...@gmail.com>.
On 5/24/07, Justin Erenkrantz <ju...@erenkrantz.com> wrote:
> On 5/24/07, Jorge Schrauwen <jo...@gmail.com> wrote:
> > Maybe one rule that states that {INSERT AUTHERIZED PEOPLE HERE} can
> > make a decision on a dispute. Example: some external link that provide
> > bad/false or not prefured information.
> > If that person/persons decide the link needs to go it should.
> > Optionally these decision can be posted to docs@httpd for comunity
> > input.
>
> That group should be the members of the HTTP Server PMC.  We don't
> need to create yet another group for wiki oversight - the current
> oversight is working well (more or less) - this is an instance of that
> oversight kicking in.
>
> (I am all for people who help with documentation to be on the PMC.
> Those PMC members who are following such activity should feel free to
> nominate worthy folks to the PMC!)  -- justin
>

I have limited knowledge* of the internal workings of the ASF,
It was my idea also that members of httpd or docs project would get that role.

* I am a observer of dev@httpd and make an occasional comment and try
to chip in on he wiki where I can.

-- 
~Jorge

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 5/24/07, Jorge Schrauwen <jo...@gmail.com> wrote:
> Maybe one rule that states that {INSERT AUTHERIZED PEOPLE HERE} can
> make a decision on a dispute. Example: some external link that provide
> bad/false or not prefured information.
> If that person/persons decide the link needs to go it should.
> Optionally these decision can be posted to docs@httpd for comunity
> input.

That group should be the members of the HTTP Server PMC.  We don't
need to create yet another group for wiki oversight - the current
oversight is working well (more or less) - this is an instance of that
oversight kicking in.

(I am all for people who help with documentation to be on the PMC.
Those PMC members who are following such activity should feel free to
nominate worthy folks to the PMC!)  -- justin

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 5/24/07, Jorge Schrauwen <jo...@gmail.com> wrote:
> Maybe one rule that states that {INSERT AUTHERIZED PEOPLE HERE} can
> make a decision on a dispute. Example: some external link that provide
> bad/false or not prefured information.
> If that person/persons decide the link needs to go it should.
> Optionally these decision can be posted to docs@httpd for comunity
> input.

That group should be the members of the HTTP Server PMC.  We don't
need to create yet another group for wiki oversight - the current
oversight is working well (more or less) - this is an instance of that
oversight kicking in.

(I am all for people who help with documentation to be on the PMC.
Those PMC members who are following such activity should feel free to
nominate worthy folks to the PMC!)  -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Jorge Schrauwen <jo...@gmail.com>.
On 5/24/07, Joshua Slive <jo...@slive.ca> wrote:
> The Apache wiki is not some democratic exercise like wikipedia where
> we need to treat everyone equally. We are a meritocracy, not a
> democracy, even on the wiki. Certain people (like Rich) have earned
> the right to make final decisions about what should be on the wiki.
> AskApache has not earned that right.
+1

Maybe one rule that states that {INSERT AUTHERIZED PEOPLE HERE} can
make a decision on a dispute. Example: some external link that provide
bad/false or not prefured information.
If that person/persons decide the link needs to go it should.
Optionally these decision can be posted to docs@httpd for comunity
input.

-- 
~Jorge

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Jorge Schrauwen <jo...@gmail.com>.
On 5/24/07, Joshua Slive <jo...@slive.ca> wrote:
> The Apache wiki is not some democratic exercise like wikipedia where
> we need to treat everyone equally. We are a meritocracy, not a
> democracy, even on the wiki. Certain people (like Rich) have earned
> the right to make final decisions about what should be on the wiki.
> AskApache has not earned that right.
+1

Maybe one rule that states that {INSERT AUTHERIZED PEOPLE HERE} can
make a decision on a dispute. Example: some external link that provide
bad/false or not prefured information.
If that person/persons decide the link needs to go it should.
Optionally these decision can be posted to docs@httpd for comunity
input.

-- 
~Jorge

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Joshua Slive <jo...@slive.ca>.
On 5/24/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> [for infra, who is bcc'ed - three * bullets below]

> * ask infra to reopen the wiki to general write access,
> * aks infra to please revoke AskApache/their ip from the httpd wiki.

+1.

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Joshua Slive <jo...@slive.ca>.
On 5/24/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> [for infra, who is bcc'ed - three * bullets below]

> * ask infra to reopen the wiki to general write access,
> * aks infra to please revoke AskApache/their ip from the httpd wiki.

+1.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
[for infra, who is bcc'ed - three * bullets below]

Joshua Slive wrote:
> 
> Although I respect Bill's desire to have this solved apache-wide, I
> actually think that this case would have been better addressed in the
> closer confines of docs@httpd. Let's just address this particular case
> and not worry about the general issue for now.

-sorry- if I've given that impression - and in fairness to all, we do want
an /httpd/ policy so that we can perform the mandatory oversight.

* I'm not suggesting we are setting policy for anything beyond wiki.a.o/httpd/

Each project has to apply whatever supervision/guidance it's PMC decides.

> The Apache wiki is not some democratic exercise like wikipedia where
> we need to treat everyone equally. We are a meritocracy, not a
> democracy, even on the wiki. Certain people (like Rich) have earned
> the right to make final decisions about what should be on the wiki.
> AskApache has not earned that right.

Well said.

> The content that he is adding is inappropriate (and violates my
> suggested policy) for many reasons. I suggest that someone email him
> and tell him that he is henceforth banned from:
> 
> 1) Making any links to his personal site; and
> 2) Reverting any change made by someone else (even if that change is a
> reversion of his change).
> 
> If he can't live with those rules, he can be banned for good.

Actually, it's pretty clear this was already asked, and answered by his
actions.  It would be good to know about off-list dialogs like this, at
least by a cc/bcc to private@h.a.o, so we know the warning is out there
and can simply swing the ban-stick when the warning is violated.  It
obviously has been since Rich already communicated these rules.  Since
Rich and others already asked AskApache on multiple occasions ...

> If you would like me to send this email (as someone who has not
> interacted with him before) I'd be fine with that (although I don't
> know his address).

This time I think Rich and others have already done so, and have gone
above and beyond to help him participate constructively.  S/he can't,
or chooses not to, so the appropriate action is to remove access now.

Once there is a clear policy, it's trivial to have #asfinfra or mail
to infrastructure@h.a.o to remove a spammer or user who can't and won't
follow policy after they have been reminded once or twice.  The fact that
we didn't have one (or inside information that these issues /were/ brought
up with -this- wikiuser) made it hard to conduct oversight.

* I thank everyone here, plus those beyond httpd, for all of the
  observations about wiki ecosystems.

We had a large number of responses today from the PMC, so I think we are
essentially on the same page and should now

* ask infra to reopen the wiki to general write access,
* aks infra to please revoke AskApache/their ip from the httpd wiki.

and this case is dispelled.  Would our docs@ folks try to codify Joshua's
comments and others into a policy page on the httpd wiki that users can
refer to?

Thanks all!

Bill

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
[for infra, who is bcc'ed - three * bullets below]

Joshua Slive wrote:
> 
> Although I respect Bill's desire to have this solved apache-wide, I
> actually think that this case would have been better addressed in the
> closer confines of docs@httpd. Let's just address this particular case
> and not worry about the general issue for now.

-sorry- if I've given that impression - and in fairness to all, we do want
an /httpd/ policy so that we can perform the mandatory oversight.

* I'm not suggesting we are setting policy for anything beyond wiki.a.o/httpd/

Each project has to apply whatever supervision/guidance it's PMC decides.

> The Apache wiki is not some democratic exercise like wikipedia where
> we need to treat everyone equally. We are a meritocracy, not a
> democracy, even on the wiki. Certain people (like Rich) have earned
> the right to make final decisions about what should be on the wiki.
> AskApache has not earned that right.

Well said.

> The content that he is adding is inappropriate (and violates my
> suggested policy) for many reasons. I suggest that someone email him
> and tell him that he is henceforth banned from:
> 
> 1) Making any links to his personal site; and
> 2) Reverting any change made by someone else (even if that change is a
> reversion of his change).
> 
> If he can't live with those rules, he can be banned for good.

Actually, it's pretty clear this was already asked, and answered by his
actions.  It would be good to know about off-list dialogs like this, at
least by a cc/bcc to private@h.a.o, so we know the warning is out there
and can simply swing the ban-stick when the warning is violated.  It
obviously has been since Rich already communicated these rules.  Since
Rich and others already asked AskApache on multiple occasions ...

> If you would like me to send this email (as someone who has not
> interacted with him before) I'd be fine with that (although I don't
> know his address).

This time I think Rich and others have already done so, and have gone
above and beyond to help him participate constructively.  S/he can't,
or chooses not to, so the appropriate action is to remove access now.

Once there is a clear policy, it's trivial to have #asfinfra or mail
to infrastructure@h.a.o to remove a spammer or user who can't and won't
follow policy after they have been reminded once or twice.  The fact that
we didn't have one (or inside information that these issues /were/ brought
up with -this- wikiuser) made it hard to conduct oversight.

* I thank everyone here, plus those beyond httpd, for all of the
  observations about wiki ecosystems.

We had a large number of responses today from the PMC, so I think we are
essentially on the same page and should now

* ask infra to reopen the wiki to general write access,
* aks infra to please revoke AskApache/their ip from the httpd wiki.

and this case is dispelled.  Would our docs@ folks try to codify Joshua's
comments and others into a policy page on the httpd wiki that users can
refer to?

Thanks all!

Bill

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Tony Stevenson <to...@pc-tony.com>.

Joshua Slive wrote:
> On 5/24/07, Rich Bowen <rb...@rcbowen.com> wrote:
>>
>> On May 24, 2007, at 04:23, Tony Stevenson wrote:
>>
>>
>> >>
>> > AskApache has had several email conversations with both myself, and
>> > Rich.  In which he was asked politely, but firmly to not use links
>> > to content on his site.
>>
>> NOTE: NOT because external links are bad, but because the articles to
>> which he was linking were misleading, incorrect, and promoted sub-
>> optimal solutions to common problems. The implied endorsement (The
>> Apache docs link to this article, so it must be true) was
>> unfortunate, and undesirable.
>
> Although I respect Bill's desire to have this solved apache-wide, I
> actually think that this case would have been better addressed in the
> closer confines of docs@httpd. Let's just address this particular case
> and not worry about the general issue for now.
>
> The Apache wiki is not some democratic exercise like wikipedia where
> we need to treat everyone equally. We are a meritocracy, not a
> democracy, even on the wiki. Certain people (like Rich) have earned
> the right to make final decisions about what should be on the wiki.
> AskApache has not earned that right.
>
> The content that he is adding is inappropriate (and violates my
> suggested policy) for many reasons. I suggest that someone email him
> and tell him that he is henceforth banned from:
>
> 1) Making any links to his personal site; and
> 2) Reverting any change made by someone else (even if that change is a
> reversion of his change).
>
> If he can't live with those rules, he can be banned for good.
>
+1

Would it be possible to re-enable write access for known 'good guys' so 
we can continue the process maintaining the wiki?

> If you would like me to send this email (as someone who has not
> interacted with him before) I'd be fine with that (although I don't
> know his address).
>
Josh, I am happy to send this mail too, as I already have a history with 
him.  I am not sure he will react overly well with someone else 'wading 
in' to this.

> Joshua.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org
>

-Tony


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Tony Stevenson <to...@pc-tony.com>.

Joshua Slive wrote:
> On 5/24/07, Rich Bowen <rb...@rcbowen.com> wrote:
>>
>> On May 24, 2007, at 04:23, Tony Stevenson wrote:
>>
>>
>> >>
>> > AskApache has had several email conversations with both myself, and
>> > Rich.  In which he was asked politely, but firmly to not use links
>> > to content on his site.
>>
>> NOTE: NOT because external links are bad, but because the articles to
>> which he was linking were misleading, incorrect, and promoted sub-
>> optimal solutions to common problems. The implied endorsement (The
>> Apache docs link to this article, so it must be true) was
>> unfortunate, and undesirable.
>
> Although I respect Bill's desire to have this solved apache-wide, I
> actually think that this case would have been better addressed in the
> closer confines of docs@httpd. Let's just address this particular case
> and not worry about the general issue for now.
>
> The Apache wiki is not some democratic exercise like wikipedia where
> we need to treat everyone equally. We are a meritocracy, not a
> democracy, even on the wiki. Certain people (like Rich) have earned
> the right to make final decisions about what should be on the wiki.
> AskApache has not earned that right.
>
> The content that he is adding is inappropriate (and violates my
> suggested policy) for many reasons. I suggest that someone email him
> and tell him that he is henceforth banned from:
>
> 1) Making any links to his personal site; and
> 2) Reverting any change made by someone else (even if that change is a
> reversion of his change).
>
> If he can't live with those rules, he can be banned for good.
>
+1

Would it be possible to re-enable write access for known 'good guys' so 
we can continue the process maintaining the wiki?

> If you would like me to send this email (as someone who has not
> interacted with him before) I'd be fine with that (although I don't
> know his address).
>
Josh, I am happy to send this mail too, as I already have a history with 
him.  I am not sure he will react overly well with someone else 'wading 
in' to this.

> Joshua.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org
>

-Tony


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Joshua Slive <jo...@slive.ca>.
On 5/24/07, Rich Bowen <rb...@rcbowen.com> wrote:
>
> On May 24, 2007, at 04:23, Tony Stevenson wrote:
>
>
> >>
> > AskApache has had several email conversations with both myself, and
> > Rich.  In which he was asked politely, but firmly to not use links
> > to content on his site.
>
> NOTE: NOT because external links are bad, but because the articles to
> which he was linking were misleading, incorrect, and promoted sub-
> optimal solutions to common problems. The implied endorsement (The
> Apache docs link to this article, so it must be true) was
> unfortunate, and undesirable.

Although I respect Bill's desire to have this solved apache-wide, I
actually think that this case would have been better addressed in the
closer confines of docs@httpd. Let's just address this particular case
and not worry about the general issue for now.

The Apache wiki is not some democratic exercise like wikipedia where
we need to treat everyone equally. We are a meritocracy, not a
democracy, even on the wiki. Certain people (like Rich) have earned
the right to make final decisions about what should be on the wiki.
AskApache has not earned that right.

The content that he is adding is inappropriate (and violates my
suggested policy) for many reasons. I suggest that someone email him
and tell him that he is henceforth banned from:

1) Making any links to his personal site; and
2) Reverting any change made by someone else (even if that change is a
reversion of his change).

If he can't live with those rules, he can be banned for good.

If you would like me to send this email (as someone who has not
interacted with him before) I'd be fine with that (although I don't
know his address).

Joshua.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Joshua Slive <jo...@slive.ca>.
On 5/24/07, Rich Bowen <rb...@rcbowen.com> wrote:
>
> On May 24, 2007, at 04:23, Tony Stevenson wrote:
>
>
> >>
> > AskApache has had several email conversations with both myself, and
> > Rich.  In which he was asked politely, but firmly to not use links
> > to content on his site.
>
> NOTE: NOT because external links are bad, but because the articles to
> which he was linking were misleading, incorrect, and promoted sub-
> optimal solutions to common problems. The implied endorsement (The
> Apache docs link to this article, so it must be true) was
> unfortunate, and undesirable.

Although I respect Bill's desire to have this solved apache-wide, I
actually think that this case would have been better addressed in the
closer confines of docs@httpd. Let's just address this particular case
and not worry about the general issue for now.

The Apache wiki is not some democratic exercise like wikipedia where
we need to treat everyone equally. We are a meritocracy, not a
democracy, even on the wiki. Certain people (like Rich) have earned
the right to make final decisions about what should be on the wiki.
AskApache has not earned that right.

The content that he is adding is inappropriate (and violates my
suggested policy) for many reasons. I suggest that someone email him
and tell him that he is henceforth banned from:

1) Making any links to his personal site; and
2) Reverting any change made by someone else (even if that change is a
reversion of his change).

If he can't live with those rules, he can be banned for good.

If you would like me to send this email (as someone who has not
interacted with him before) I'd be fine with that (although I don't
know his address).

Joshua.

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Rich Bowen <rb...@rcbowen.com>.
On May 24, 2007, at 04:23, Tony Stevenson wrote:


>>
> AskApache has had several email conversations with both myself, and  
> Rich.  In which he was asked politely, but firmly to not use links  
> to content on his site.

NOTE: NOT because external links are bad, but because the articles to  
which he was linking were misleading, incorrect, and promoted sub- 
optimal solutions to common problems. The implied endorsement (The  
Apache docs link to this article, so it must be true) was  
unfortunate, and undesirable.


--
We are here and it is now.
Further than that all human knowledge is moonshine.
H.L.Mencken



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Rich Bowen <rb...@rcbowen.com>.
On May 24, 2007, at 04:23, Tony Stevenson wrote:


>>
> AskApache has had several email conversations with both myself, and  
> Rich.  In which he was asked politely, but firmly to not use links  
> to content on his site.

NOTE: NOT because external links are bad, but because the articles to  
which he was linking were misleading, incorrect, and promoted sub- 
optimal solutions to common problems. The implied endorsement (The  
Apache docs link to this article, so it must be true) was  
unfortunate, and undesirable.


--
We are here and it is now.
Further than that all human knowledge is moonshine.
H.L.Mencken



Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Tony Stevenson <to...@pc-tony.com>.

Paul Querna wrote:
> William A. Rowe, Jr. wrote:
>   
>> We have a serious issue to determine, and I've asked for a 48 hour cooldown
>> of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
>> the wiki become read-only for the conclusion of this decision.
>>
>>  [XXX] Our httpd wiki is open to external resources for httpd.
>>  [  ] External httpd resources are prohibited.
>>
>> I mean this explicitly, obviously a link to MS/Sun/RedHat about their
>> specific platform would be genuinely useful and relevant.
>>     
>
> I believe that Wikis must be able to link to external sites -- just like
> we do in the regular documentation.
>
> However, just like the the regular documentation, these links are
> generally restricted to Vendors, or other long standing and stable
> sites. (or... example.com)
>   
He has quoted the Apache wiki etiqutte guide, in his home page on the wiki.

Wiki Eitquette -- 
http://wiki.apache.org/httpd/WikiCourse/BasicIntroduction/200_Wikiquette?action=print&media=projection
His wiki Home Page -- http://wiki.apache.org/httpd/AskApache

In which he infers he is allowed to use external links to materials of 
his own choice. 
However the wiki-etiquette seems to be a standard set of pages shipped 
with MoinMoin, maybe they need reviewing for ASF application and either 
removing, or modifying accordingly.
> I believe we can look to wikipedia's linking policy as a good example of
> how to build a 'policy' that people can understand:
>
> http://en.wikipedia.org/wiki/Wikipedia:External_links
>
> In this case: AdSense covered personal blogs especially from people who
> do not contribute in other mediums doesn't seem like a good place to be
> linking to.
>
> On the revision war: I don't like it;  I do believe AskApache's link
> should be removed.  I don't blame megaspaz, he was using the tools
> available, trying to communicate with AskApache that the link was
> unacceptable.  The larger problem is that the AskApache person has
> never, AFAIK, made themselves known on the mailing list, or other
> mediums, making it impossible to communicate with them in other manners.
>   
AskApache has had several email conversations with both myself, and 
Rich.  In which he was asked politely, but firmly to not use links to 
content on his site.
Material such as his htaccess guide were at best misleading, as well the 
possibility of plagiarism.  Sadly they do get very agressive when their 
material is modified or removed from the wiki, he has thus far refused 
to openly communicate with us, claiming "... we singled him out for 
abuse ..."

Megaspaz is a commited helper in #apache and I firmly believe he was 
doing his best to keep the wiki clean, and accurate.  We have been lucky 
so far in that we have only had two spam posts, much less than was 
originally anticiapted. 

I find it very unfortunate that it has come to this, considering Rich 
and I struggled for quite some time to have the wiki created.  When we 
first started using the wiki, the intention was for it to be a staging 
post for non docs comitters to submit works that can be then moved into 
the official docs project.  It has now grown beyond my best expectations 
with lots of good content.  As mentioned in a previous email to the docs 
list, this has now become the de facto FAQ, and is growing day on day.  
In fact we were highly praised by 3 or 4 individuals in #apache for the 
content, as it was accurate and helped them solve their issues with 
little fuss and with ease.  This is testament to those of us who strive 
to make it so, and of the content in there.

I have copies of these email conversations, and I am willing to forward 
them on to the appropriate people, rather than these lists as a whole.

This gentleman has been a source of concern for sometime with some 
regulars in #apache.  Reviewing some of his material leads us to 
conclude that he may have some very valuable input to the docs project, 
but the way in which he has handled the situation has been less than 
enthusiastic.  Unfortunately there is no simple way, or for that matter 
a policy, of preventing him from accessing the wiki.  He has already 
used 3 different user accounts to circumvent measures put in place. We 
could of course block his IP and delete hsi user account, but as we all 
know these are very easily circumvented anyway.


> On a policy: My opinion doesn't fit into a hard and fast rule, and
> rather relies upon discretion.
>
> -Paul
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org
>
>   

-Tony

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Tony Stevenson <to...@pc-tony.com>.

Paul Querna wrote:
> William A. Rowe, Jr. wrote:
>   
>> We have a serious issue to determine, and I've asked for a 48 hour cooldown
>> of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
>> the wiki become read-only for the conclusion of this decision.
>>
>>  [XXX] Our httpd wiki is open to external resources for httpd.
>>  [  ] External httpd resources are prohibited.
>>
>> I mean this explicitly, obviously a link to MS/Sun/RedHat about their
>> specific platform would be genuinely useful and relevant.
>>     
>
> I believe that Wikis must be able to link to external sites -- just like
> we do in the regular documentation.
>
> However, just like the the regular documentation, these links are
> generally restricted to Vendors, or other long standing and stable
> sites. (or... example.com)
>   
He has quoted the Apache wiki etiqutte guide, in his home page on the wiki.

Wiki Eitquette -- 
http://wiki.apache.org/httpd/WikiCourse/BasicIntroduction/200_Wikiquette?action=print&media=projection
His wiki Home Page -- http://wiki.apache.org/httpd/AskApache

In which he infers he is allowed to use external links to materials of 
his own choice. 
However the wiki-etiquette seems to be a standard set of pages shipped 
with MoinMoin, maybe they need reviewing for ASF application and either 
removing, or modifying accordingly.
> I believe we can look to wikipedia's linking policy as a good example of
> how to build a 'policy' that people can understand:
>
> http://en.wikipedia.org/wiki/Wikipedia:External_links
>
> In this case: AdSense covered personal blogs especially from people who
> do not contribute in other mediums doesn't seem like a good place to be
> linking to.
>
> On the revision war: I don't like it;  I do believe AskApache's link
> should be removed.  I don't blame megaspaz, he was using the tools
> available, trying to communicate with AskApache that the link was
> unacceptable.  The larger problem is that the AskApache person has
> never, AFAIK, made themselves known on the mailing list, or other
> mediums, making it impossible to communicate with them in other manners.
>   
AskApache has had several email conversations with both myself, and 
Rich.  In which he was asked politely, but firmly to not use links to 
content on his site.
Material such as his htaccess guide were at best misleading, as well the 
possibility of plagiarism.  Sadly they do get very agressive when their 
material is modified or removed from the wiki, he has thus far refused 
to openly communicate with us, claiming "... we singled him out for 
abuse ..."

Megaspaz is a commited helper in #apache and I firmly believe he was 
doing his best to keep the wiki clean, and accurate.  We have been lucky 
so far in that we have only had two spam posts, much less than was 
originally anticiapted. 

I find it very unfortunate that it has come to this, considering Rich 
and I struggled for quite some time to have the wiki created.  When we 
first started using the wiki, the intention was for it to be a staging 
post for non docs comitters to submit works that can be then moved into 
the official docs project.  It has now grown beyond my best expectations 
with lots of good content.  As mentioned in a previous email to the docs 
list, this has now become the de facto FAQ, and is growing day on day.  
In fact we were highly praised by 3 or 4 individuals in #apache for the 
content, as it was accurate and helped them solve their issues with 
little fuss and with ease.  This is testament to those of us who strive 
to make it so, and of the content in there.

I have copies of these email conversations, and I am willing to forward 
them on to the appropriate people, rather than these lists as a whole.

This gentleman has been a source of concern for sometime with some 
regulars in #apache.  Reviewing some of his material leads us to 
conclude that he may have some very valuable input to the docs project, 
but the way in which he has handled the situation has been less than 
enthusiastic.  Unfortunately there is no simple way, or for that matter 
a policy, of preventing him from accessing the wiki.  He has already 
used 3 different user accounts to circumvent measures put in place. We 
could of course block his IP and delete hsi user account, but as we all 
know these are very easily circumvented anyway.


> On a policy: My opinion doesn't fit into a hard and fast rule, and
> rather relies upon discretion.
>
> -Paul
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org
>
>   

-Tony

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Paul Querna <ch...@force-elite.com>.
William A. Rowe, Jr. wrote:
> We have a serious issue to determine, and I've asked for a 48 hour cooldown
> of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> the wiki become read-only for the conclusion of this decision.
> 
>  [XX] Our httpd wiki is open to external resources for httpd.
>  [  ] External httpd resources are prohibited.
> 
> I mean this explicitly, obviously a link to MS/Sun/RedHat about their
> specific platform would be genuinely useful and relevant.

I believe that Wikis must be able to link to external sites -- just like
we do in the regular documentation.

However, just like the the regular documentation, these links are
generally restricted to Vendors, or other long standing and stable
sites. (or... example.com)

I believe we can look to wikipedia's linking policy as a good example of
how to build a 'policy' that people can understand:

http://en.wikipedia.org/wiki/Wikipedia:External_links

In this case: AdSense covered personal blogs especially from people who
do not contribute in other mediums doesn't seem like a good place to be
linking to.

On the revision war: I don't like it;  I do believe AskApache's link
should be removed.  I don't blame megaspaz, he was using the tools
available, trying to communicate with AskApache that the link was
unacceptable.  The larger problem is that the AskApache person has
never, AFAIK, made themselves known on the mailing list, or other
mediums, making it impossible to communicate with them in other manners.

On a policy: My opinion doesn't fit into a hard and fast rule, and
rather relies upon discretion.

-Paul


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Noirin Plunkett <no...@apache.org>.
On Thu, May 24, 2007 at 01:56:19AM -0500, William A. Rowe, Jr. wrote:
> We have a serious issue to determine, and I've asked for a 48 hour cooldown
> of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> the wiki become read-only for the conclusion of this decision.
> 
>  [ ] Our httpd wiki is open to external resources for httpd.
>  [X] External httpd resources are prohibited.
>
> I mean this explicitly, obviously a link to MS/Sun/RedHat about their
> specific platform would be genuinely useful and relevant.

Including that caveat, I'm in favour of keeping external httpd resources
out. 

> I'm asking about askapache's external links, which have not been actually
> contributed to the foundation.  And we've never presumed that pointers to
> external links are resources under the AL.

If AskApache would like to contribute content - BRILLIANT! If they'd
like to have their content on the wiki, but aren't sure how to wikify
them, please, just license them right, and there are a bunch of active
contributors who'll help get them up there.

If AskApache just want extra traffic, I don't see that that's helpful or
beneficial to us, or our users.

> Once we determine a policy, I belive we owe megaspaz and AskApache a second
> chance once they are informed of the definative policy.
> 
> Future wiki abuse would, of course, lead to account and IP blockage.  But
> I believe at this moment both acted in best-faith without any guidance from
> our project, and we need to have policies so folks can be responsible wiki
> users.

+1

> This isn't the end-all of all possibilities, but let's discuss for 2 days
> and reopen the wiki with a concrete policy?
> 
> Bill
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Eric Covener <co...@gmail.com>.
On 5/24/07, Craig McClanahan <cr...@apache.org> wrote:
> If a Wiki isn't open to community input ( where "community" here means
> *users*, not the typical Apache definition of "community" meaning the
> *committers*), then what is it for?

The wiki is for community input.  Not recognizing the difference
between contributed wiki content and external links to an ad-driven
site may influence your feelings on the matter.

-- 
Eric Covener
covener@gmail.com

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Vincent Bray <no...@gmail.com>.
> Craig McClanahan <cr...@apache.org> said:
> In the Apache projects I'm involved with, the only thing we kick off
> of the wiki pages is spam.  It's a wiki ... it's user contributed
> content, and not necessarily reflective of the opinions of the
> project's developers.  But it is *incredibly* useful to the users of
> the software we build.  Deal with that reality ... or close it down
> ... your choice.

But this is spam, FSVO spam. His contributions are of dubious merit
and seem mainly self-serving.

I'm with Paul and Noirin. The ASF is as much about community as about
code or other contributions. If AskApache genuinely wants to
contribute, he should license his docs to the ASF where they can (and
would) be reviewed. Linking to external sites should be limitted to
specs or vendor specific details (the distros page links to the gentoo
build docs page, for example).

-- 
noodl

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Henrik Nordstrom <he...@henriknordstrom.net>.
ons 2007-05-30 klockan 21:39 +0100 skrev Nick Kew:

> It then proceeds to list HTTP status codes, and gives an errordocument
> for each one.  Unfortunately a number of them are bogus gibberish.

It's the gibberish Apache emits if you shoot yourself in the foot using
Redirect. Garbage in, garbage out.

Regards
Henrik

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Henrik Nordstrom <he...@henriknordstrom.net>.
ons 2007-05-30 klockan 21:39 +0100 skrev Nick Kew:

> It then proceeds to list HTTP status codes, and gives an errordocument
> for each one.  Unfortunately a number of them are bogus gibberish.

It's the gibberish Apache emits if you shoot yourself in the foot using
Redirect. Garbage in, garbage out.

Regards
Henrik

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Nick Kew <ni...@webthing.com>.
On Thu, 24 May 2007 15:15:56 -0500
"Webmaster" <we...@askapache.com> wrote:

> Hello,  
> 
> I've never used this list so bear with me, I couldn't get docs-help
> to send me help.    Its nice to know Apache has so many helpful
> people willing to discuss this situation, but why do I get the
> feeling that none of you have actually read the page in question?
> Here is the link that is causing all the commotion:
> http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.h
> tml I encourage you to read it and then you can understand my
> position.

OK, I just looked.  And to be brutal ...

WTF????

The first error is to call them "Apache Status Codes".
That's a nasty one to perpetrate on innocent newbies, because
it obscures what they really are, and misleads the reader.

First sentence: "There are a total of 57 HTTP Status Codes recognized
by the Apache Web Server."   Sorry, that's plain nonsense -
though at least it describes them correctly.

The article then suggests using any or all of them with Apache's
Redirect.  It does so without any attempt to explain the meaning
of any of the status codes, so it cannot be said to add anything
to Apache's default behaviour or the mod_alias documentation.
Rather it confuses the issue for readers who don't have sufficient
grasp of HTTP to see that it's gibberish.  The fact that Apache enables
you to shoot yourself in the foot is not a good reason to do so.

It then proceeds to list HTTP status codes, and gives an errordocument
for each one.  Unfortunately a number of them are bogus gibberish.

> After you read the article, how could you possibly say that it is
> spam? That is perhaps the most relevant article I've ever seen about
> Apache ErrorDocuments and more specifically, HTTP Status Codes.

Spam is not the right word.  But it's far too ill-informed and
misleading to give the implied endorsement of a link from an
official or semi-official Apache site.

I'm sure you could make a useful contribution if you want to.
But you're not ready to go solo.  So why not put your contents
(rather than links to it) on the wiki, where some of the regulars 
can help improve it for everyone?

-- 
Nick Kew

Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Colm MacCarthaigh <co...@stdlib.net>.
On Thu, May 24, 2007 at 09:04:43PM +0100, Noirin Plunkett wrote:
> > 4. Its a not-for-profit site.
> 
> I don't really care. It's a not-for-sharing, not-community-editable
> site.

And to further illustratre that we really *don't* care; you can actually
take the entire official Apache httpd documentation tree, and publish a
copy on your site.  You can surround it with as many ads as you like and
you can make as much money as you can, and it's all permitted by the
license.

Any use you can make of the content in the wiki is less clear, but the
ethos of the ASF is as above, and with some small effort (if neccessary)
I certainly believe the same could be made the case for it. 

It is also not as if by contributing content to the wiki, the content
on your site would cease to exist :-)

-- 
Colm MacCárthaigh                        Public Key: colm+pgp@stdlib.net

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Noirin Plunkett <no...@apache.org>.
On Thu, May 24, 2007 at 03:15:56PM -0500, Webmaster wrote:
> Hello,  
> 
> After you read the article, how could you possibly say that it is spam?

I don't think it's spam - I think linking to it from the wiki is not
helpful.

Firstly, I don't think it's well written. I know that many brilliant
technical people aren't great writers, and that's fine - I'm not an ace
coder. But at Apache, we work together. And that means allowing other
people to change your work.

> That is perhaps the most relevant article I've ever seen about Apache
> ErrorDocuments and more specifically, HTTP Status Codes.  Its the single,
> only place on the entire Internet where each of Apache's 57 Status Codes are
> listed.  Its the only place on the Net where you can find the headers of
> each Apache ErrorDocument.  Its the only article anywhere to have every
> single returned errordocument.  I know because I did the work, I filled in
> the blanks on the Common_HTTPStatusCodes, I wrote it, and I published my
> findings to support open-source and Apache, and for the benefit of the
> entire net community.

I have to disagree with you here. It's not the only place to have the
HTTP status codes - and if what we want is those, I think w3c is a much
better reference. AskApache may be well researched, stable, anything you
like, but w3c actually define the standards (roughly). Also, it doesn't
have every single returned ErrorDocument. I know, because I translated
all of them into Irish, and the Irish translations aren't there =) The
headers will be different depending on exactly what ErrorDocument is
returned - language negotiation, or custom ErrorDocuments will change
these things. Not by much, but it's still a change. You also don't
mention - again, just for example - that there are no required header
codes for 1xx status codes.

If you truly want to support Apache, put this information under an
Apache license, put it straight on to the wiki (not a link, because I
can't edit the content on your pages, for example), and we'll work
together.

> I actually did research on the external linking of sources or references on
> the Apache wiki, asf, many other apache wikis, and the link to my article is
> 100% compliant with the policies, but besides that it is a really fantastic
> article with 100% relevancy. 

The httpd project isn't Derby, or Jakarta, or the ASF. It's the httpd
project, and while it's part of the ASF, it's also different to other
parts. The ASF works as a meritocracy. When you prove that you're a good
contributor, AND that you play well with others (even if you think
they're not playing well with you), you earn respect and a certain right
to be heard.

> 1. There is no copyright issue.

Great! Then put this content on the wiki, and let us tweak it. Not a
link, to somewhere we don't have edit access. The content, as it is.

> 2. Its 100% relevant to the wiki article.

Again, the content please.

> 3. Its the ONLY place on the NET with that information. It is the
> authoritative link because its the original source.

w3c is the authoritative source for information about HTTP status codes,
the Apache source code is the authoritative source for information about
ErrorDocuments that ship with Apache, a user's hard drive is the
authoritative source for the ErrorDocuments their version of Apache is
actually sending.

> 4. Its a not-for-profit site.

I don't really care. It's a not-for-sharing, not-community-editable
site.

> 5. The source that I used to fill in the many blanks on the Status Code
> table was my article, and since the article is incredibly lengthy a link to
> the original source is 100% warranted.  

Bzzt, no. Firstly, the *original* source is the Apache httpd - that's
what served your requests, after all. More importantly, if I write up
stuff about mod_memcache - again, just for example, because this really
happened - for a paper that's to be presented, and then later, that same
stuff gets added to the actual Apache httpd docs, there isn't a link
anywhere to the original paper! And it's not warranted. Finally, the
wiki article looks good just as it is - thank you for the work you've
put in; but I really don't think a link will improve it. All that's
needed is already there.

> 6. AskApache.com is registered for another 7 years, so these links are
> stable.

I really don't care much about 'stable' - httpd 1.3 docs are 'stable',
it's not changing much these days. That doesn't mean they're always
right, or useful, or not in need of communal oversight and editing.

> 7. Have you even read the article?

Yes. Repeatedly. I found the English passable at best, and I'm a
linguistics student. I'm happy to work *with* you - but as long as this
stuff is outside the editorial purview of the ASF or the httpd project,
I can't do that. And even if you were to give me personally access,
there's still Rich, and Kess, and Bill, and Nick, and Paul, and all the
other people who work on our docs, as a team.

> I once again find myself in a wiki battle of reverts, but I just don't have
> the patience or the time to be harassed every time I contribute to the wiki.
> Its supposed to be a place where new ideas and drafts can flourish, shutting
> people down who want to contribute is not cool.  Calling me a spammer and
> calling my policy-compliant link "spam" is disingenuous and that rudeness
> and immaturity is NOT following the guidelines and policies of apache and
> asf.  

Drafts, great. Ideas, great. Links, not so useful. CONTENT, please.

> I have probably spent over 30 hours trying to contribute to the wiki, which
> I understood to be the trial area for working out new documentation.  A
> "work-in-progress" where the point was shared collaboration.  Unfortunately
> pctony and megaspaz have refused to let me post anything on the wiki.. It
> seems that every tip and suggestion I contribute immediately gets shot down
> as either being plagiarised, misleading and incorrect, or they just don't
> give me an excuse.  I have literally spent hours writing a new wiki article
> in the ScratchPad area, and a few minutes after I posted it was immediately
> deleted. 

I haven't followed most of your stuff, and I don't think your
ErrorDocuments page is awfully misleading. I think it's slightly
misleading, but adding a link to it rather than just the content smells
a lot of self-promotion and unwillingness to play nice with others. That
said, Rich has - very literally - written the book(s) on Apache, and if
he says the stuff you're suggesting is less-than-best-practise, you'd do
well to listen to him, and revise YOUR site - not get into an edit war
on the wiki.

> My stuff isn't discussed or improved upon or checked out, its just
> completely deleted.  My email address is on my username page on the wiki,
> and I have emailed both pctony and megaspaz several times to try and get
> them to understand we are on the same team and the wiki isn't their personal
> feifdom.  Look at my site, askapache.com.  Its almost entirely dedicated to
> Apache httpd tips, tricks, etc..  I challenge pctony and megaspaz to stop
> deleting all my posts and instead show me how its wrong.  Anyone who knows
> anything about Apache will immediately recognize my posts for being
> original, creative, and incredible resources for the whole web to enjoy for
> free.  My billing is currently $125/hr, I am NOT trying to make any kind of
> profit from askapache.com, and to suggest my articles are spam is complete
> ludicrous.  Anyone can shout slogans,  I put the code up on the NET for
> everyone to discuss and improve.   

This project is a meritocracy. We listen to and respect people who've
proven themselves, by consistent effort, AND by willingness to play
nice with others. If you want to play with us, throw your ball into the
ring, and we'll play. Don't stand at the side, waving your ball, and
yelling "Nyah-nyah! You can look, but you can't touch! My ball!"

"Show me what I'm doing wrong" also doesn't fly here, unless you're
terribly polite about it. One of my very first commits was reverted
because I made a small boo-boo, and rather than whining about it, I
looked at their change, went over what I had done again, figured out
where I'd gone wrong, and sent a mail to say "Doh! Sorry, my bad."
Things like that earn you respect - and the next time I fluffed up, I
got an email saying "Did you mean to do that?", and got to fix my own
mistakes.

I don't disagree that some of your tips and tricks work; but the guys
here are as smart as they come, when it comes to Apache. And if they say
"that's really not best practise", you should learn from them. Hang out
on #apache, see how we work, what's regarded as cheap and hackish, and
what the latest-greatest ways of doing things are. There have been a lot
of changes over the lifetime of the Apache httpd server, and (almost!)
all of them have been for good reasons. Learn what's changed and why,
and you'll benefit your users and ours.

> We are all like-minded here when it comes to Apache, so I hope we can rise
> above the emotional aspects of this issue and instead focus on making the
> wiki a more productive and friendly place for everyone who has ideas and is
> willing to donate their time and effort.

I do hope you'll rise above the emotions too, and look forward to
playing ball with you in the future!

Noirin

> 

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Nick Kew <ni...@webthing.com>.
On Thu, 24 May 2007 15:15:56 -0500
"Webmaster" <we...@askapache.com> wrote:

> Hello,  
> 
> I've never used this list so bear with me, I couldn't get docs-help
> to send me help.    Its nice to know Apache has so many helpful
> people willing to discuss this situation, but why do I get the
> feeling that none of you have actually read the page in question?
> Here is the link that is causing all the commotion:
> http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.h
> tml I encourage you to read it and then you can understand my
> position.

OK, I just looked.  And to be brutal ...

WTF????

The first error is to call them "Apache Status Codes".
That's a nasty one to perpetrate on innocent newbies, because
it obscures what they really are, and misleads the reader.

First sentence: "There are a total of 57 HTTP Status Codes recognized
by the Apache Web Server."   Sorry, that's plain nonsense -
though at least it describes them correctly.

The article then suggests using any or all of them with Apache's
Redirect.  It does so without any attempt to explain the meaning
of any of the status codes, so it cannot be said to add anything
to Apache's default behaviour or the mod_alias documentation.
Rather it confuses the issue for readers who don't have sufficient
grasp of HTTP to see that it's gibberish.  The fact that Apache enables
you to shoot yourself in the foot is not a good reason to do so.

It then proceeds to list HTTP status codes, and gives an errordocument
for each one.  Unfortunately a number of them are bogus gibberish.

> After you read the article, how could you possibly say that it is
> spam? That is perhaps the most relevant article I've ever seen about
> Apache ErrorDocuments and more specifically, HTTP Status Codes.

Spam is not the right word.  But it's far too ill-informed and
misleading to give the implied endorsement of a link from an
official or semi-official Apache site.

I'm sure you could make a useful contribution if you want to.
But you're not ready to go solo.  So why not put your contents
(rather than links to it) on the wiki, where some of the regulars 
can help improve it for everyone?

-- 
Nick Kew

Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Colm MacCarthaigh <co...@stdlib.net>.
On Thu, May 24, 2007 at 06:55:07PM -0500, Webmaster wrote:
> Actually if you compare the RFC spec to the list on the wiki, you will
> notice the wiki contains a lot more Status Codes than the spec.  I admit
> that this information may be totally boring and pointless for 99.999% of
> people, but this is fascinating to me and I think it would be a shame to
> delete the most complete list of HTTP Status Codes anywhere on the net.  

It is not within our power to delete it, nor are we. At question is 
its value in link-form on our wiki.

-- 
Colm MacCárthaigh                        Public Key: colm+pgp@stdlib.net

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Ruediger Pluem <rp...@apache.org>.

On 05/25/2007 01:55 AM, Webmaster wrote:

> 
> Actually if you compare the RFC spec to the list on the wiki, you will
> notice the wiki contains a lot more Status Codes than the spec.  I admit
> that this information may be totally boring and pointless for 99.999% of
> people, but this is fascinating to me and I think it would be a shame to
> delete the most complete list of HTTP Status Codes anywhere on the net.  The
> link is to the RFC because if someone wants to learn more information they
> can go there.  The RFC is too long for the wiki and THAT would be redundant.
> Likewise the article I linked to
> http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.h
> tml and the other article I linked to
> http://en.wikipedia.org/wiki/List_of_HTTP_status_codes also contain
> additional information.  Especially my article, which is the only published
> reference of the actual headers and data sent by apache for all 57 HTTP
> Status Codes.  How many does the RFC talk about? 40?  So I guess I am

RFC2616 talks about 41, where one of them is reserved, but not used (306).
There are only 50 in total and not 57 because there are gaps.

The remaining 9:

426 belongs to RFC2817 (1)
102, 207, 422, 423, 424, 507 belong to RFC2518 (6)
506 belongs to RFC2295 (1)
510 belongs to RFC2774 (1)

So I guess it would make sense to have links to all five RFC's above.

Regards

Rüdiger


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


RE: [Issue] External links @ the wiki, aka pagechange wars

Posted by Webmaster <we...@askapache.com>.
> The whole Common_HTTPStatusCodes page is redundant in my 
> opinion. It duplicates (with a lot less information) the 
> content of the HTTP spec.
> In fact, I plan to delete this page unless I hear objections 
> on this list.
> 
> Joshua.


Actually if you compare the RFC spec to the list on the wiki, you will
notice the wiki contains a lot more Status Codes than the spec.  I admit
that this information may be totally boring and pointless for 99.999% of
people, but this is fascinating to me and I think it would be a shame to
delete the most complete list of HTTP Status Codes anywhere on the net.  The
link is to the RFC because if someone wants to learn more information they
can go there.  The RFC is too long for the wiki and THAT would be redundant.
Likewise the article I linked to
http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.h
tml and the other article I linked to
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes also contain
additional information.  Especially my article, which is the only published
reference of the actual headers and data sent by apache for all 57 HTTP
Status Codes.  How many does the RFC talk about? 40?  So I guess I am
objecting, and I hope someone understands why.  Or am I just missing
something?

AskApache

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.467 / Virus Database: 269.7.7/816 - Release Date: 5/23/2007
3:59 PM
 


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Ruediger Pluem <rp...@apache.org>.

On 05/25/2007 12:16 AM, Joshua Slive wrote:

> On the specific case at hand, I have one major thing to contribute:
> The whole Common_HTTPStatusCodes page is redundant in my opinion. It
> duplicates (with a lot less information) the content of the HTTP spec.
> In fact, I plan to delete this page unless I hear objections on this

+1 to this. Though it might make sense to leave the link at the top of
the page. Although there are many locations to find RFC2616 on the
net it is convenient for the interested and not frequent RFC reader
to have a direct link on chapter 10 of RFC2616.

Regards

Rüdiger


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Webmaster wrote:
> 
> Wow.  I'm not willing to participate in a community that publically says
> they don't want me.  I really resent being treated like an outlaw or some
> blackhat.  Its shocking how different my view of Apache is now compared to
> the previous 10 years.  

10 years ago we were busy telling an organization that WebTen for the classic
MacOS could not be branded the "Apache Server" as that infringed on our mark,
and their patches had not become part of the "Apache Server".

In the subsequent 10 years, we have revisited this issue often and defend
the Apache mark as fairly as possible to avoid confusion.  I was impressed,
visiting your site, that you disclaimed any association with the ASF on
your askapache.con main page.  As much as your choice of domain names
irritates me, I Thank You for this clarity.

That said, there is no such disclaimer using such a name on our wiki, so
you must be kidding if you think we are treating you differently, or in
any way specially.  On an almost weekly basis, one PMC or another at the
ASF has to ask some helpful third party site to desist from infringing on
the ASF's marks.  He requested that you choose another name, seemed like
a reasonable idea to me.

You had been asked on several occasions to take specific actions that would
help users from falling into configuration traps and errors, and you choose
not to.  You persisted in irritating virtually every long standing contributor
to the Apache httpd docs.  And you engaged them in wiki edit wars with our
most consistent contributors.  He asked that you summarize in a really
short paragraph the policies that you would follow to prevent any future
misunderstanding, seemed like a reasonable idea to me.

And yet - they offered a trivial way for you to redeem yourself and have
a fresh start.  I give them credit for entertaining the thought.

> I hope in the future you realize its in your best interests to be polite and
> friendly.  You won't be hearing from me again.

Considering how forgiving folks are, it's sad you didn't recognize that
they were offering you an olive branch to make peace.

In our best interests though?  There are some who would say that your
contribution was far from the httpd project's interests, never mind the
end users following your advise.  We are all continually learning what
is rational and what is not so advisable in the Apache configuration and
it's code.

I've been beaten up by security analysts over flaws created by my own code
contributions.  We all are continually learning, from what I have read
in this thread, you weren't terribly open to learning the flaws in your
recommendations.  At this project, contribution is a two way street, and
those who only talk, and rarely listen, rarely have contributions we value.

They had tried to steer you in the right direction, and you never budged.
This became a significant time sink and probably was a net loss.  And yet
they persisted in helping you become part of the community.  Shame on you
for not taking Joshua up on his hospitality.


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


RE: [Issue] External links @ the wiki, aka pagechange wars

Posted by Webmaster <we...@askapache.com>.
> The fact that you need to ask that makes me even more 
> doubtful that you understand our community well enough to 
> contribute meaningfully.
> Quite frankly, I think your time might be better spent someplace else.
> But I am always willing to give somebody another chance. I 
> don't speak for the PMC as a whole, but let me be very 
> explicit about what I would like to see before you contribute 
> further to the wiki:
> 
> 1. An explicit statement of at least one paragraph 
> summarizing the wiki guidelines and confirming explicitly 
> that you understand them and will abide by them.
> 
> 2. A choice of a new userid for the wiki. The AskApache id 
> likely implies to some readers that you are an official 
> Apache spokesperson and hence leads to confusion. Please tell 
> us what userid you choose before you create it. I suggest 
> FirstnameLastname, which is the moinmoin wiki standard.
> 
> Joshua.

Wow.  I'm not willing to participate in a community that publically says
they don't want me.  I really resent being treated like an outlaw or some
blackhat.  Its shocking how different my view of Apache is now compared to
the previous 10 years.  

I hope in the future you realize its in your best interests to be polite and
friendly.  You won't be hearing from me again.

 I only wanted to contribute.

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.8.1/822 - Release Date: 5/28/2007
11:40 AM
 


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Joshua Slive <jo...@slive.ca>.
On 5/29/07, Webmaster <we...@askapache.com> wrote:
> Cool, so how do I go about doing that?
>
> -AskApache
>
> > Yes, your account was disabled. If you want it re-enabled,
> > you'd need to convince us (the Apache HTTP Server Project
> > Management Committee) that you will abide by the guidelines here:
> > http://wiki.apache.org/httpd/Contributing

The fact that you need to ask that makes me even more doubtful that
you understand our community well enough to contribute meaningfully.
Quite frankly, I think your time might be better spent someplace else.
But I am always willing to give somebody another chance. I don't speak
for the PMC as a whole, but let me be very explicit about what I would
like to see before you contribute further to the wiki:

1. An explicit statement of at least one paragraph summarizing the
wiki guidelines and confirming explicitly that you understand them and
will abide by them.

2. A choice of a new userid for the wiki. The AskApache id likely
implies to some readers that you are an official Apache spokesperson
and hence leads to confusion. Please tell us what userid you choose
before you create it. I suggest FirstnameLastname, which is the
moinmoin wiki standard.

Joshua.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


RE: [Issue] External links @ the wiki, aka pagechange wars

Posted by Webmaster <we...@askapache.com>.
Cool, so how do I go about doing that?

-AskApache

> Yes, your account was disabled. If you want it re-enabled, 
> you'd need to convince us (the Apache HTTP Server Project 
> Management Committee) that you will abide by the guidelines here:
> http://wiki.apache.org/httpd/Contributing
> 
> Joshua.

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.8.1/822 - Release Date: 5/28/2007
11:40 AM
 


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Joshua Slive <jo...@slive.ca>.
On 5/29/07, Webmaster <we...@askapache.com> wrote:
> Was my wiki account (AskApache) deleted?  I can't login or get the wiki to
> mail me my account data.

Yes, your account was disabled. If you want it re-enabled, you'd need
to convince us (the Apache HTTP Server Project Management Committee)
that you will abide by the guidelines here:
http://wiki.apache.org/httpd/Contributing

Joshua.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


RE: [Issue] External links @ the wiki, aka pagechange wars

Posted by Webmaster <we...@askapache.com>.
Was my wiki account (AskApache) deleted?  I can't login or get the wiki to
mail me my account data.

:(

-AskApache

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.8.1/822 - Release Date: 5/28/2007
11:40 AM
 


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Ruediger Pluem <rp...@apache.org>.

On 05/25/2007 05:25 PM, Joshua Slive wrote:
> On 5/25/07, Jorge Schrauwen <jo...@gmail.com> wrote:
> 
>> Personally i was very happy with the form it had on revision 7.
>> If you remove it thats fine but I'd rather see it go back to revision 7.
> 
> 
> I've combined Jorge and Ruediger's suggestions to leave just a few of
> the most common status codes and links to the specs for all the rest.

Great. Thanks for doing.

Regards

Rüdiger


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Jorge Schrauwen <jo...@gmail.com>.
On 5/25/07, Joshua Slive <jo...@slive.ca> wrote:
> On 5/25/07, Jorge Schrauwen <jo...@gmail.com> wrote:
>
> > Personally i was very happy with the form it had on revision 7.
> > If you remove it thats fine but I'd rather see it go back to revision 7.
>
> I've combined Jorge and Ruediger's suggestions to leave just a few of
> the most common status codes and links to the specs for all the rest.
>

Ah now it looks like what I intended it to be :)
thanks


-- 
~Jorge

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Joshua Slive <jo...@slive.ca>.
On 5/25/07, Jorge Schrauwen <jo...@gmail.com> wrote:

> Personally i was very happy with the form it had on revision 7.
> If you remove it thats fine but I'd rather see it go back to revision 7.

I've combined Jorge and Ruediger's suggestions to leave just a few of
the most common status codes and links to the specs for all the rest.

Joshua.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Jorge Schrauwen <jo...@gmail.com>.
On 5/25/07, Vincent Bray <no...@gmail.com> wrote:
> On 24/05/07, Joshua Slive <jo...@slive.ca> wrote:
> > On the specific case at hand, I have one major thing to contribute:
> > The whole Common_HTTPStatusCodes page is redundant in my opinion. It
> > duplicates (with a lot less information) the content of the HTTP spec.
> > In fact, I plan to delete this page unless I hear objections on this
> > list.
>
> +1 (I'm not a committer, but this is the wiki so I guess I can vote.)
>
> I don't see any merit in this page over the standard and the source.
>

I started that page, it was never my intend to cover the full RFC,
Just the most common codes for a quick reference. (as was reflected in the url)

A link to the RFC with the full spec would ofcource be usefull for
people who want more informatiom.

Personally i was very happy with the form it had on revision 7.
If you remove it thats fine but I'd rather see it go back to revision 7.



-- 
~Jorge

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Vincent Bray <no...@gmail.com>.
On 24/05/07, Joshua Slive <jo...@slive.ca> wrote:
> On the specific case at hand, I have one major thing to contribute:
> The whole Common_HTTPStatusCodes page is redundant in my opinion. It
> duplicates (with a lot less information) the content of the HTTP spec.
> In fact, I plan to delete this page unless I hear objections on this
> list.

+1 (I'm not a committer, but this is the wiki so I guess I can vote.)

I don't see any merit in this page over the standard and the source.

-- 
noodl

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Joshua Slive <jo...@slive.ca>.
On 5/24/07, Webmaster <we...@askapache.com> wrote:
> Hello,
>
> I've never used this list so bear with me,

The main point here is that you need to be ready to accept and act on
feedback from more-experienced contributors. If you aren't, then you
aren't welcome as a contributor.

Perhaps part of the problem is that the feedback channel in the wiki
is not wide enough. One line commit messages don't give much room for
conversation. When I get a chance, I'll expand the information in the
wiki on how to contribute, and specifically suggest coming to this
list to discuss any conflict.

Beyond that, links to your own site are not welcome on the wiki. On
the modern internet, where links are like currency, there is too much
room for conflicts of interest. If you agree to abide by our rules,
you are welcome to contribute. But links to your site are not welcome,
no matter how relevant. You are, of course, welcome and encouraged to
maintain your site to benefit apache users. (Although your site name
is misleading and possibly a trademark violation; haven't you been
contacted by a member of our Public Relations Committee about that?)

On the specific case at hand, I have one major thing to contribute:
The whole Common_HTTPStatusCodes page is redundant in my opinion. It
duplicates (with a lot less information) the content of the HTTP spec.
In fact, I plan to delete this page unless I hear objections on this
list.

Joshua.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


RE: [Issue] External links @ the wiki, aka pagechange wars

Posted by Webmaster <we...@askapache.com>.
Hello,  

I've never used this list so bear with me, I couldn't get docs-help to send
me help.    Its nice to know Apache has so many helpful people willing to
discuss this situation, but why do I get the feeling that none of you have
actually read the page in question?  Here is the link that is causing all
the commotion:
http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.h
tml I encourage you to read it and then you can understand my position.

After you read the article, how could you possibly say that it is spam?
That is perhaps the most relevant article I've ever seen about Apache
ErrorDocuments and more specifically, HTTP Status Codes.  Its the single,
only place on the entire Internet where each of Apache's 57 Status Codes are
listed.  Its the only place on the Net where you can find the headers of
each Apache ErrorDocument.  Its the only article anywhere to have every
single returned errordocument.  I know because I did the work, I filled in
the blanks on the Common_HTTPStatusCodes, I wrote it, and I published my
findings to support open-source and Apache, and for the benefit of the
entire net community.
 
I actually did research on the external linking of sources or references on
the Apache wiki, asf, many other apache wikis, and the link to my article is
100% compliant with the policies, but besides that it is a really fantastic
article with 100% relevancy. 
 
1. There is no copyright issue.
2. Its 100% relevant to the wiki article.
3. Its the ONLY place on the NET with that information. It is the
authoritative link because its the original source.
4. Its a not-for-profit site.
5. The source that I used to fill in the many blanks on the Status Code
table was my article, and since the article is incredibly lengthy a link to
the original source is 100% warranted.  
6. AskApache.com is registered for another 7 years, so these links are
stable.
7. Have you even read the article?
 
I once again find myself in a wiki battle of reverts, but I just don't have
the patience or the time to be harassed every time I contribute to the wiki.
Its supposed to be a place where new ideas and drafts can flourish, shutting
people down who want to contribute is not cool.  Calling me a spammer and
calling my policy-compliant link "spam" is disingenuous and that rudeness
and immaturity is NOT following the guidelines and policies of apache and
asf.  

I have probably spent over 30 hours trying to contribute to the wiki, which
I understood to be the trial area for working out new documentation.  A
"work-in-progress" where the point was shared collaboration.  Unfortunately
pctony and megaspaz have refused to let me post anything on the wiki.. It
seems that every tip and suggestion I contribute immediately gets shot down
as either being plagiarised, misleading and incorrect, or they just don't
give me an excuse.  I have literally spent hours writing a new wiki article
in the ScratchPad area, and a few minutes after I posted it was immediately
deleted. 

My stuff isn't discussed or improved upon or checked out, its just
completely deleted.  My email address is on my username page on the wiki,
and I have emailed both pctony and megaspaz several times to try and get
them to understand we are on the same team and the wiki isn't their personal
feifdom.  Look at my site, askapache.com.  Its almost entirely dedicated to
Apache httpd tips, tricks, etc..  I challenge pctony and megaspaz to stop
deleting all my posts and instead show me how its wrong.  Anyone who knows
anything about Apache will immediately recognize my posts for being
original, creative, and incredible resources for the whole web to enjoy for
free.  My billing is currently $125/hr, I am NOT trying to make any kind of
profit from askapache.com, and to suggest my articles are spam is complete
ludicrous.  Anyone can shout slogans,  I put the code up on the NET for
everyone to discuss and improve.   

We are all like-minded here when it comes to Apache, so I hope we can rise
above the emotional aspects of this issue and instead focus on making the
wiki a more productive and friendly place for everyone who has ideas and is
willing to donate their time and effort.

-AskApache

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.467 / Virus Database: 269.7.7/816 - Release Date: 5/23/2007
3:59 PM
 


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


RE: [Issue] External links @ the wiki, aka pagechange wars

Posted by Webmaster <we...@askapache.com>.
Hello,  

I've never used this list so bear with me, I couldn't get docs-help to send
me help.    Its nice to know Apache has so many helpful people willing to
discuss this situation, but why do I get the feeling that none of you have
actually read the page in question?  Here is the link that is causing all
the commotion:
http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.h
tml I encourage you to read it and then you can understand my position.

After you read the article, how could you possibly say that it is spam?
That is perhaps the most relevant article I've ever seen about Apache
ErrorDocuments and more specifically, HTTP Status Codes.  Its the single,
only place on the entire Internet where each of Apache's 57 Status Codes are
listed.  Its the only place on the Net where you can find the headers of
each Apache ErrorDocument.  Its the only article anywhere to have every
single returned errordocument.  I know because I did the work, I filled in
the blanks on the Common_HTTPStatusCodes, I wrote it, and I published my
findings to support open-source and Apache, and for the benefit of the
entire net community.
 
I actually did research on the external linking of sources or references on
the Apache wiki, asf, many other apache wikis, and the link to my article is
100% compliant with the policies, but besides that it is a really fantastic
article with 100% relevancy. 
 
1. There is no copyright issue.
2. Its 100% relevant to the wiki article.
3. Its the ONLY place on the NET with that information. It is the
authoritative link because its the original source.
4. Its a not-for-profit site.
5. The source that I used to fill in the many blanks on the Status Code
table was my article, and since the article is incredibly lengthy a link to
the original source is 100% warranted.  
6. AskApache.com is registered for another 7 years, so these links are
stable.
7. Have you even read the article?
 
I once again find myself in a wiki battle of reverts, but I just don't have
the patience or the time to be harassed every time I contribute to the wiki.
Its supposed to be a place where new ideas and drafts can flourish, shutting
people down who want to contribute is not cool.  Calling me a spammer and
calling my policy-compliant link "spam" is disingenuous and that rudeness
and immaturity is NOT following the guidelines and policies of apache and
asf.  

I have probably spent over 30 hours trying to contribute to the wiki, which
I understood to be the trial area for working out new documentation.  A
"work-in-progress" where the point was shared collaboration.  Unfortunately
pctony and megaspaz have refused to let me post anything on the wiki.. It
seems that every tip and suggestion I contribute immediately gets shot down
as either being plagiarised, misleading and incorrect, or they just don't
give me an excuse.  I have literally spent hours writing a new wiki article
in the ScratchPad area, and a few minutes after I posted it was immediately
deleted. 

My stuff isn't discussed or improved upon or checked out, its just
completely deleted.  My email address is on my username page on the wiki,
and I have emailed both pctony and megaspaz several times to try and get
them to understand we are on the same team and the wiki isn't their personal
feifdom.  Look at my site, askapache.com.  Its almost entirely dedicated to
Apache httpd tips, tricks, etc..  I challenge pctony and megaspaz to stop
deleting all my posts and instead show me how its wrong.  Anyone who knows
anything about Apache will immediately recognize my posts for being
original, creative, and incredible resources for the whole web to enjoy for
free.  My billing is currently $125/hr, I am NOT trying to make any kind of
profit from askapache.com, and to suggest my articles are spam is complete
ludicrous.  Anyone can shout slogans,  I put the code up on the NET for
everyone to discuss and improve.   

We are all like-minded here when it comes to Apache, so I hope we can rise
above the emotional aspects of this issue and instead focus on making the
wiki a more productive and friendly place for everyone who has ideas and is
willing to donate their time and effort.

-AskApache

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.467 / Virus Database: 269.7.7/816 - Release Date: 5/23/2007
3:59 PM
 


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Jorge Schrauwen <jo...@gmail.com>.
On 5/24/07, Rich Bowen <rb...@rcbowen.com> wrote:
>
> On May 24, 2007, at 08:50, Colm MacCarthaigh wrote:
>
> > On Thu, May 24, 2007 at 08:05:30AM -0400, Joshua Slive wrote:
> >> External links are encouraged where they add substantial value, but
> >> you may not link to your own pages or otherwise seek private benefits
> >> from external links.
> >
> > I like the elegance of this rule, because if it's your page and you
> > words, well you can just add the content to the wiki anyway. But at
> > the
> > same time it may invite even more awkward and inappropriate behaviour,
> > e.g. paying someone else to add the links on your behalf.
> >
> > I think this problem is always going to fall into the "We know abuse
> > when we see it" category, it requires a vague kind of rule-making
> > which
> > only humans can apply.
> >
> > I'm in favour of banning these links in this instance, though not all
> > external links.
>
> The trouble in this particular case is that the contributor in
> question writes articles that are misleading or completely wrong, and
> appears to be unaware of the fact that he is being misleading and
> wrong. I'm not sure if he's genuinely trying to be helpful, or merely
> trying to inflate his google ranking by creating pages that link back
> to his site. Either way, the content that he produces does not add
> substantial value, nor do the pages to which he links, and often his
> content actively promotes practices that are discouraged as being
> less-than-best-practice.
>
> Added to this is his refusal to accept correction, so that when his
> articles are modified to reflect best practice and reality, he gets
> offended and changes it back.
>
> Behind the scenes there are angry and insulting email messages being
> exchanged, which I'm occasionally copied on, in which he defends his
> articles as being the best things ever written, and accusing us of
> singling him out for abuse. It's all very juvenile and time consuming.
>
> However, one of the side effects of having this kind of public Wiki
> is that we have to do this kind of policing and maintenance, and some
> people are going to feel singled out.
>
> --
> If you miss this moment
> You miss your life
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org
>
>

+1
-- 
~Jorge

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Colm MacCarthaigh <co...@stdlib.net>.
On Thu, May 24, 2007 at 06:47:49PM -0500, Webmaster wrote:
> Say whatever you want, I'm not going to argue when the evidence is online
> for everyone to examine.  Go look at the wiki at my posting history, you
> will see how unfairly I have been treated. 

I've done just that today, never having looked at it before. In my
opinion, you have been treated fairly and have been given substantial
leeway.

> Why not respond like you are supposed to and actually SHOW me what is wrong,
> misleading, or poorly written? 

You do not allow us to do so in the most efficient, convenient,
accessible and collaborative manner - to edit them directly with
comments. The people here are not free consultation for your personal
website.

> Isn't that what the wiki is for?  How can we
> improve content when it just gets deleted right away?  I don't have time to
> try to make a couple people like me.. thats silly, I go to the wiki to
> contribute, share ideas, and learn about my favorite software.

So why do you post so much "content" only in the form of links? you
are mis-representing the problem here.

-- 
Colm MacCárthaigh                        Public Key: colm+pgp@stdlib.net

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Colm MacCarthaigh <co...@stdlib.net>.
On Thu, May 24, 2007 at 06:47:49PM -0500, Webmaster wrote:
> Say whatever you want, I'm not going to argue when the evidence is online
> for everyone to examine.  Go look at the wiki at my posting history, you
> will see how unfairly I have been treated. 

I've done just that today, never having looked at it before. In my
opinion, you have been treated fairly and have been given substantial
leeway.

> Why not respond like you are supposed to and actually SHOW me what is wrong,
> misleading, or poorly written? 

You do not allow us to do so in the most efficient, convenient,
accessible and collaborative manner - to edit them directly with
comments. The people here are not free consultation for your personal
website.

> Isn't that what the wiki is for?  How can we
> improve content when it just gets deleted right away?  I don't have time to
> try to make a couple people like me.. thats silly, I go to the wiki to
> contribute, share ideas, and learn about my favorite software.

So why do you post so much "content" only in the form of links? you
are mis-representing the problem here.

-- 
Colm MacCárthaigh                        Public Key: colm+pgp@stdlib.net

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Tony Stevenson <to...@pc-tony.com>.
See my inline comments below, but I feel that these are the points that 
have been raised today.

Issues:
1)  We don't want you to link to your materials from the wiki. 
2)  We feel that some of the content could do with tweaking to support 
well established best-practices

Next Steps:
1)  If you are willing to place your material in the wiki, published 
under the Apache license then please do so, where it will be reviewed 
(see further down)
2)  Stop linking to material on your site, rather add it to the wiki (as 
above)
3)  We can all move on, and improve the wiki as a whole, but best of all 
we can stop this already exhaustive thread  :)



Webmaster wrote:
>> The trouble in this particular case is that the contributor 
>> in question writes articles that are misleading or completely 
>> wrong, and appears to be unaware of the fact that he is being 
>> misleading and wrong. I'm not sure if he's genuinely trying 
>> to be helpful, or merely trying to inflate his google ranking 
>> by creating pages that link back to his site. 
>>     
>
> If I am misleading or wrong in any way shape or form than it is absolutely
> accidental.   Instead of repeatedly telling me how bad my contributions are,
> and deleting anything I try to contribute, why not just point out WHERE I am
> wrong, WHERE I am misleading, that way we can work together and add valuable
> content to the wiki.  Not to mention I can revise the articles on my blog,
> which means your feedback will be helping thousands of newbie Apache users.
>
>
>
>   
>> Either way, the 
>> content that he produces does not add substantial value, nor 
>> do the pages to which he links, and often his content 
>> actively promotes practices that are discouraged as being 
>> less-than-best-practice.
>>     
>
> I don't care if you are the top Apache Guru on the planet, the fact is that
> thousands of people DO think that my articles add substantial value, and if
> you really feel my stuff is that bad its your problem, not the content.
> Otherwise I would encourage you to make suggestions, point out errors,
> highlight alternatives, illustrate best-practices, instead of just talking
> about how bad my contributions are.
>   
It's not that the content is bad particularly, it is that they don't 
follow established best practices.  This can then be misleading for 
people who do not have in-depth knowledge of the issues that these 
articles may lead too. We would love you to put your content on the 
wiki, and not link to it from the wiki.  This was it can be reviewed in 
the standard way all Apache (HTTPd specifically) documentation is, via 
your peers.  The meritocracy system that the ASF work within is there so 
that established comitters can do just that, commit good quality work to 
the official docs for the project.
>
>   
>> Added to this is his refusal to accept correction, so that 
>> when his articles are modified to reflect best practice and 
>> reality, he gets offended and changes it back.
>>     
>
> Say whatever you want, I'm not going to argue when the evidence is online
> for everyone to examine.  Go look at the wiki at my posting history, you
> will see how unfairly I have been treated. 
>
>   
>> Behind the scenes there are angry and insulting email 
>> messages being exchanged, which I'm occasionally copied on, 
>> in which he defends his articles as being the best things 
>> ever written, and accusing us of singling him out for abuse. 
>> It's all very juvenile and time consuming.
>>     
>
> I believe I've written 3 people a total of 5 emails in the past 4 months.  I
> saved everything so I don't have to argue or use sweeping generalizations,
> facts speak for themselves.   I just don't understand all the unfriendliness
> and pettiness from 2 individuals since day 1 (look at my wiki history).  In
> fact, one of the people actually went to my blog and left this kindhearted
> public comment.  "This is the most idiotic ‘tip’ I’ve ever read on the web
> since 1990....  I am curious as to how you manage to generate technological
> content, you must be copying and pasting from different sources." Pleasant
> no?
>
>   
I know I have asked you to join us in #apache, on more than one occasion 
so that we can initiate an open and frank discussion about the materials 
in question here.  These seems to have fallen on deaf ears, and as a 
result this is where we have ended up.  If we can discuss this openly I 
can't help but feel you might see what we have been trying to tell you, 
as a result you may find out why we feel so strongly about some of your 
material.

> I feel like just because I posted some radical, new, and alternative ideas
> and solutions that might not have been discussed elsewhere before, people
> get a little competitive and want me to fall in line or something.  I can
> already here the response: "your stuff wasn't new or radical, it didn't
> solve anything, it was wrong, poorly written, and definately misleading."
> Why not respond like you are supposed to and actually SHOW me what is wrong,
> misleading, or poorly written?  Isn't that what the wiki is for?  How can we
> improve content when it just gets deleted right away?  I don't have time to
> try to make a couple people like me.. thats silly, I go to the wiki to
> contribute, share ideas, and learn about my favorite software.
>   
It's not the fact your material is radical, if that were the only 
deciding factor Apache HTTPd would not be where it is today, you only 
have to look at the extensive list of modules to see the evidence of 
this.  It has progressed as people have found new and better ways to use 
their Apache server.
> I am only interested in being able to help and contribute to the wiki
> without immediately being deleted, reverted, and publically dissed both
> personally and academically.  I understand how it could have gotten to this
> point, drama is always exciting, but the past is the past and I am just
> wanting to contribute.  I've been trying for several months now, with month
> long breaks in-between, but I feel like if the people with grudges can't let
> it go, then I will never be able to contribute.  Isn't there a policy or a
> guideline or someone with rank that can point the way to put this behind us?
>
>   
If you are willing to post your material on the wiki, under the Apache 
license, and not use links back to your site then I am sure your 
material will receive peer review, with a lot of positive, and 
constructive feedback.  If you then want to update your site as a 
consequence of that, then so be it, that is your choice.

> "Teamwork makes the Dream Work"
>
> No virus found in this outgoing message.
> Checked by AVG Free Edition. 
> Version: 7.5.467 / Virus Database: 269.7.7/816 - Release Date: 5/23/2007
> 3:59 PM
>  
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org
>
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


RE: [Issue] External links @ the wiki, aka pagechange wars

Posted by Webmaster <we...@askapache.com>.
> The trouble in this particular case is that the contributor 
> in question writes articles that are misleading or completely 
> wrong, and appears to be unaware of the fact that he is being 
> misleading and wrong. I'm not sure if he's genuinely trying 
> to be helpful, or merely trying to inflate his google ranking 
> by creating pages that link back to his site. 

If I am misleading or wrong in any way shape or form than it is absolutely
accidental.   Instead of repeatedly telling me how bad my contributions are,
and deleting anything I try to contribute, why not just point out WHERE I am
wrong, WHERE I am misleading, that way we can work together and add valuable
content to the wiki.  Not to mention I can revise the articles on my blog,
which means your feedback will be helping thousands of newbie Apache users.



> Either way, the 
> content that he produces does not add substantial value, nor 
> do the pages to which he links, and often his content 
> actively promotes practices that are discouraged as being 
> less-than-best-practice.

I don't care if you are the top Apache Guru on the planet, the fact is that
thousands of people DO think that my articles add substantial value, and if
you really feel my stuff is that bad its your problem, not the content.
Otherwise I would encourage you to make suggestions, point out errors,
highlight alternatives, illustrate best-practices, instead of just talking
about how bad my contributions are.


> Added to this is his refusal to accept correction, so that 
> when his articles are modified to reflect best practice and 
> reality, he gets offended and changes it back.

Say whatever you want, I'm not going to argue when the evidence is online
for everyone to examine.  Go look at the wiki at my posting history, you
will see how unfairly I have been treated. 

> Behind the scenes there are angry and insulting email 
> messages being exchanged, which I'm occasionally copied on, 
> in which he defends his articles as being the best things 
> ever written, and accusing us of singling him out for abuse. 
> It's all very juvenile and time consuming.

I believe I've written 3 people a total of 5 emails in the past 4 months.  I
saved everything so I don't have to argue or use sweeping generalizations,
facts speak for themselves.   I just don't understand all the unfriendliness
and pettiness from 2 individuals since day 1 (look at my wiki history).  In
fact, one of the people actually went to my blog and left this kindhearted
public comment.  "This is the most idiotic ‘tip’ I’ve ever read on the web
since 1990....  I am curious as to how you manage to generate technological
content, you must be copying and pasting from different sources." Pleasant
no?

I feel like just because I posted some radical, new, and alternative ideas
and solutions that might not have been discussed elsewhere before, people
get a little competitive and want me to fall in line or something.  I can
already here the response: "your stuff wasn't new or radical, it didn't
solve anything, it was wrong, poorly written, and definately misleading."
Why not respond like you are supposed to and actually SHOW me what is wrong,
misleading, or poorly written?  Isn't that what the wiki is for?  How can we
improve content when it just gets deleted right away?  I don't have time to
try to make a couple people like me.. thats silly, I go to the wiki to
contribute, share ideas, and learn about my favorite software.

I am only interested in being able to help and contribute to the wiki
without immediately being deleted, reverted, and publically dissed both
personally and academically.  I understand how it could have gotten to this
point, drama is always exciting, but the past is the past and I am just
wanting to contribute.  I've been trying for several months now, with month
long breaks in-between, but I feel like if the people with grudges can't let
it go, then I will never be able to contribute.  Isn't there a policy or a
guideline or someone with rank that can point the way to put this behind us?

"Teamwork makes the Dream Work"

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.467 / Virus Database: 269.7.7/816 - Release Date: 5/23/2007
3:59 PM
 


RE: [Issue] External links @ the wiki, aka pagechange wars

Posted by Webmaster <we...@askapache.com>.
> The trouble in this particular case is that the contributor 
> in question writes articles that are misleading or completely 
> wrong, and appears to be unaware of the fact that he is being 
> misleading and wrong. I'm not sure if he's genuinely trying 
> to be helpful, or merely trying to inflate his google ranking 
> by creating pages that link back to his site. 

If I am misleading or wrong in any way shape or form than it is absolutely
accidental.   Instead of repeatedly telling me how bad my contributions are,
and deleting anything I try to contribute, why not just point out WHERE I am
wrong, WHERE I am misleading, that way we can work together and add valuable
content to the wiki.  Not to mention I can revise the articles on my blog,
which means your feedback will be helping thousands of newbie Apache users.



> Either way, the 
> content that he produces does not add substantial value, nor 
> do the pages to which he links, and often his content 
> actively promotes practices that are discouraged as being 
> less-than-best-practice.

I don't care if you are the top Apache Guru on the planet, the fact is that
thousands of people DO think that my articles add substantial value, and if
you really feel my stuff is that bad its your problem, not the content.
Otherwise I would encourage you to make suggestions, point out errors,
highlight alternatives, illustrate best-practices, instead of just talking
about how bad my contributions are.


> Added to this is his refusal to accept correction, so that 
> when his articles are modified to reflect best practice and 
> reality, he gets offended and changes it back.

Say whatever you want, I'm not going to argue when the evidence is online
for everyone to examine.  Go look at the wiki at my posting history, you
will see how unfairly I have been treated. 

> Behind the scenes there are angry and insulting email 
> messages being exchanged, which I'm occasionally copied on, 
> in which he defends his articles as being the best things 
> ever written, and accusing us of singling him out for abuse. 
> It's all very juvenile and time consuming.

I believe I've written 3 people a total of 5 emails in the past 4 months.  I
saved everything so I don't have to argue or use sweeping generalizations,
facts speak for themselves.   I just don't understand all the unfriendliness
and pettiness from 2 individuals since day 1 (look at my wiki history).  In
fact, one of the people actually went to my blog and left this kindhearted
public comment.  "This is the most idiotic ‘tip’ I’ve ever read on the web
since 1990....  I am curious as to how you manage to generate technological
content, you must be copying and pasting from different sources." Pleasant
no?

I feel like just because I posted some radical, new, and alternative ideas
and solutions that might not have been discussed elsewhere before, people
get a little competitive and want me to fall in line or something.  I can
already here the response: "your stuff wasn't new or radical, it didn't
solve anything, it was wrong, poorly written, and definately misleading."
Why not respond like you are supposed to and actually SHOW me what is wrong,
misleading, or poorly written?  Isn't that what the wiki is for?  How can we
improve content when it just gets deleted right away?  I don't have time to
try to make a couple people like me.. thats silly, I go to the wiki to
contribute, share ideas, and learn about my favorite software.

I am only interested in being able to help and contribute to the wiki
without immediately being deleted, reverted, and publically dissed both
personally and academically.  I understand how it could have gotten to this
point, drama is always exciting, but the past is the past and I am just
wanting to contribute.  I've been trying for several months now, with month
long breaks in-between, but I feel like if the people with grudges can't let
it go, then I will never be able to contribute.  Isn't there a policy or a
guideline or someone with rank that can point the way to put this behind us?

"Teamwork makes the Dream Work"

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.467 / Virus Database: 269.7.7/816 - Release Date: 5/23/2007
3:59 PM
 


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


RE: [Issue] External links @ the wiki, aka pagechange wars

Posted by "Noel J. Bergman" <no...@devtech.com>.
Rich Bowen wrote:

> The trouble in this particular case is that the contributor in
> question writes articles that are misleading or completely wrong, and
> appears to be unaware of the fact that he is being misleading and
> wrong.

Then if AskApache will not correct the error of its ways, I suggest that you
link to its pages -- with documentation correcting all of its false
statements, as a warning to anyone who should fall upon them by accident.

After all, I might accidentally come across them by a Google search, and you
owe it to your users to ensure that such well-known falsehoods are corrected
so that we do not follow them.  That may not be a notoriety that it wants,
but too bad.

> when his articles are modified to reflect best practice and reality,
> he gets offended and changes it back.

Too bad.  If it tries that on the Wiki, ban it.

	--- Noel



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


RE: [Issue] External links @ the wiki, aka pagechange wars

Posted by "Noel J. Bergman" <no...@devtech.com>.
Rich Bowen wrote:

> The trouble in this particular case is that the contributor in
> question writes articles that are misleading or completely wrong, and
> appears to be unaware of the fact that he is being misleading and
> wrong.

Then if AskApache will not correct the error of its ways, I suggest that you
link to its pages -- with documentation correcting all of its false
statements, as a warning to anyone who should fall upon them by accident.

After all, I might accidentally come across them by a Google search, and you
owe it to your users to ensure that such well-known falsehoods are corrected
so that we do not follow them.  That may not be a notoriety that it wants,
but too bad.

> when his articles are modified to reflect best practice and reality,
> he gets offended and changes it back.

Too bad.  If it tries that on the Wiki, ban it.

	--- Noel



Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Rich Bowen <rb...@rcbowen.com>.
On May 24, 2007, at 08:50, Colm MacCarthaigh wrote:

> On Thu, May 24, 2007 at 08:05:30AM -0400, Joshua Slive wrote:
>> External links are encouraged where they add substantial value, but
>> you may not link to your own pages or otherwise seek private benefits
>> from external links.
>
> I like the elegance of this rule, because if it's your page and you
> words, well you can just add the content to the wiki anyway. But at  
> the
> same time it may invite even more awkward and inappropriate behaviour,
> e.g. paying someone else to add the links on your behalf.
>
> I think this problem is always going to fall into the "We know abuse
> when we see it" category, it requires a vague kind of rule-making  
> which
> only humans can apply.
>
> I'm in favour of banning these links in this instance, though not all
> external links.

The trouble in this particular case is that the contributor in  
question writes articles that are misleading or completely wrong, and  
appears to be unaware of the fact that he is being misleading and  
wrong. I'm not sure if he's genuinely trying to be helpful, or merely  
trying to inflate his google ranking by creating pages that link back  
to his site. Either way, the content that he produces does not add  
substantial value, nor do the pages to which he links, and often his  
content actively promotes practices that are discouraged as being  
less-than-best-practice.

Added to this is his refusal to accept correction, so that when his  
articles are modified to reflect best practice and reality, he gets  
offended and changes it back.

Behind the scenes there are angry and insulting email messages being  
exchanged, which I'm occasionally copied on, in which he defends his  
articles as being the best things ever written, and accusing us of  
singling him out for abuse. It's all very juvenile and time consuming.

However, one of the side effects of having this kind of public Wiki  
is that we have to do this kind of policing and maintenance, and some  
people are going to feel singled out.

--
If you miss this moment
You miss your life




Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 5/24/07, Jim Jagielski <ji...@jagunet.com> wrote:
>
> On May 24, 2007, at 8:50 AM, Colm MacCarthaigh wrote:
>
> > On Thu, May 24, 2007 at 08:05:30AM -0400, Joshua Slive wrote:
> >> External links are encouraged where they add substantial value, but
> >> you may not link to your own pages or otherwise seek private benefits
> >> from external links.
> >
> > I like the elegance of this rule, because if it's your page and you
> > words, well you can just add the content to the wiki anyway. But at
> > the
> > same time it may invite even more awkward and inappropriate behaviour,
> > e.g. paying someone else to add the links on your behalf.
> >
> > I think this problem is always going to fall into the "We know abuse
> > when we see it" category, it requires a vague kind of rule-making
> > which
> > only humans can apply.
> >
> > I'm in favour of banning these links in this instance, though not all
> > external links.
> >
>
> +1

<aol />  -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 5/24/07, Jim Jagielski <ji...@jagunet.com> wrote:
>
> On May 24, 2007, at 8:50 AM, Colm MacCarthaigh wrote:
>
> > On Thu, May 24, 2007 at 08:05:30AM -0400, Joshua Slive wrote:
> >> External links are encouraged where they add substantial value, but
> >> you may not link to your own pages or otherwise seek private benefits
> >> from external links.
> >
> > I like the elegance of this rule, because if it's your page and you
> > words, well you can just add the content to the wiki anyway. But at
> > the
> > same time it may invite even more awkward and inappropriate behaviour,
> > e.g. paying someone else to add the links on your behalf.
> >
> > I think this problem is always going to fall into the "We know abuse
> > when we see it" category, it requires a vague kind of rule-making
> > which
> > only humans can apply.
> >
> > I'm in favour of banning these links in this instance, though not all
> > external links.
> >
>
> +1

<aol />  -- justin

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Jim Jagielski <ji...@jaguNET.com>.
On May 24, 2007, at 8:50 AM, Colm MacCarthaigh wrote:

> On Thu, May 24, 2007 at 08:05:30AM -0400, Joshua Slive wrote:
>> External links are encouraged where they add substantial value, but
>> you may not link to your own pages or otherwise seek private benefits
>> from external links.
>
> I like the elegance of this rule, because if it's your page and you
> words, well you can just add the content to the wiki anyway. But at  
> the
> same time it may invite even more awkward and inappropriate behaviour,
> e.g. paying someone else to add the links on your behalf.
>
> I think this problem is always going to fall into the "We know abuse
> when we see it" category, it requires a vague kind of rule-making  
> which
> only humans can apply.
>
> I'm in favour of banning these links in this instance, though not all
> external links.
>

+1


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Jim Jagielski <ji...@jaguNET.com>.
On May 24, 2007, at 8:50 AM, Colm MacCarthaigh wrote:

> On Thu, May 24, 2007 at 08:05:30AM -0400, Joshua Slive wrote:
>> External links are encouraged where they add substantial value, but
>> you may not link to your own pages or otherwise seek private benefits
>> from external links.
>
> I like the elegance of this rule, because if it's your page and you
> words, well you can just add the content to the wiki anyway. But at  
> the
> same time it may invite even more awkward and inappropriate behaviour,
> e.g. paying someone else to add the links on your behalf.
>
> I think this problem is always going to fall into the "We know abuse
> when we see it" category, it requires a vague kind of rule-making  
> which
> only humans can apply.
>
> I'm in favour of banning these links in this instance, though not all
> external links.
>

+1


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Rich Bowen <rb...@rcbowen.com>.
On May 24, 2007, at 08:50, Colm MacCarthaigh wrote:

> On Thu, May 24, 2007 at 08:05:30AM -0400, Joshua Slive wrote:
>> External links are encouraged where they add substantial value, but
>> you may not link to your own pages or otherwise seek private benefits
>> from external links.
>
> I like the elegance of this rule, because if it's your page and you
> words, well you can just add the content to the wiki anyway. But at  
> the
> same time it may invite even more awkward and inappropriate behaviour,
> e.g. paying someone else to add the links on your behalf.
>
> I think this problem is always going to fall into the "We know abuse
> when we see it" category, it requires a vague kind of rule-making  
> which
> only humans can apply.
>
> I'm in favour of banning these links in this instance, though not all
> external links.

The trouble in this particular case is that the contributor in  
question writes articles that are misleading or completely wrong, and  
appears to be unaware of the fact that he is being misleading and  
wrong. I'm not sure if he's genuinely trying to be helpful, or merely  
trying to inflate his google ranking by creating pages that link back  
to his site. Either way, the content that he produces does not add  
substantial value, nor do the pages to which he links, and often his  
content actively promotes practices that are discouraged as being  
less-than-best-practice.

Added to this is his refusal to accept correction, so that when his  
articles are modified to reflect best practice and reality, he gets  
offended and changes it back.

Behind the scenes there are angry and insulting email messages being  
exchanged, which I'm occasionally copied on, in which he defends his  
articles as being the best things ever written, and accusing us of  
singling him out for abuse. It's all very juvenile and time consuming.

However, one of the side effects of having this kind of public Wiki  
is that we have to do this kind of policing and maintenance, and some  
people are going to feel singled out.

--
If you miss this moment
You miss your life




---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Colm MacCarthaigh <co...@stdlib.net>.
On Thu, May 24, 2007 at 08:05:30AM -0400, Joshua Slive wrote:
> External links are encouraged where they add substantial value, but
> you may not link to your own pages or otherwise seek private benefits
> from external links.

I like the elegance of this rule, because if it's your page and you
words, well you can just add the content to the wiki anyway. But at the
same time it may invite even more awkward and inappropriate behaviour,
e.g. paying someone else to add the links on your behalf.

I think this problem is always going to fall into the "We know abuse
when we see it" category, it requires a vague kind of rule-making which
only humans can apply. 

I'm in favour of banning these links in this instance, though not all
external links.

-- 
Colm MacCárthaigh                        Public Key: colm+pgp@stdlib.net

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Colm MacCarthaigh <co...@stdlib.net>.
On Thu, May 24, 2007 at 08:05:30AM -0400, Joshua Slive wrote:
> External links are encouraged where they add substantial value, but
> you may not link to your own pages or otherwise seek private benefits
> from external links.

I like the elegance of this rule, because if it's your page and you
words, well you can just add the content to the wiki anyway. But at the
same time it may invite even more awkward and inappropriate behaviour,
e.g. paying someone else to add the links on your behalf.

I think this problem is always going to fall into the "We know abuse
when we see it" category, it requires a vague kind of rule-making which
only humans can apply. 

I'm in favour of banning these links in this instance, though not all
external links.

-- 
Colm MacCárthaigh                        Public Key: colm+pgp@stdlib.net

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Joshua Slive wrote:
> I think there is a clear and reasonable middle ground:
> 
> External links are encouraged where they add substantial value, but
> you may not link to your own pages or otherwise seek private benefits
> from external links.
> 
> This has been the unwritten rule in the apache httpd docs for as long
> as I remember. I have personally added many external links to the
> regular docs to things written by apache contributors, but not to my
> own pages.

Like most everyone, I like the way you put this.  Sadly, I guess this
can't be simply unwritten - and should be updated on the main httpd
wiki page.  It might be worth citing pagerank or ad hit farming is
expressly banned.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Joshua Slive <jo...@slive.ca>.
On 5/24/07, Yoav Shapira <yo...@apache.org> wrote:
> Hi,
>
> On 5/24/07, Craig McClanahan <cr...@apache.org> wrote:
> > On 5/23/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> > > We have a serious issue to determine, and I've asked for a 48 hour cooldown
> > > of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> > > the wiki become read-only for the conclusion of this decision.
> > >
> > >  [ X  ] Our httpd wiki is open to external resources for httpd.
> > >  [  ] External httpd resources are prohibited.
> <snip />
> > If a Wiki isn't open to community input ( where "community" here means
> > *users*, not the typical Apache definition of "community" meaning the
> > *committers*), then what is it for?  Committers can already post to
>
> I Agree with Craig.

I think there is a clear and reasonable middle ground:

External links are encouraged where they add substantial value, but
you may not link to your own pages or otherwise seek private benefits
from external links.

This has been the unwritten rule in the apache httpd docs for as long
as I remember. I have personally added many external links to the
regular docs to things written by apache contributors, but not to my
own pages.

Joshua.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Yoav Shapira wrote:

> Hi,
>
> On 5/24/07, Craig McClanahan <cr...@apache.org> wrote:
>
>> On 5/23/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
>> > We have a serious issue to determine, and I've asked for a 48 hour
>> cooldown
>> > of wiki.apache.org/httpd/ to make a decision, and in the meantime
>> asked that
>> > the wiki become read-only for the conclusion of this decision.
>> >
>> >  [ X  ] Our httpd wiki is open to external resources for httpd.
>> >  [  ] External httpd resources are prohibited.
>
> <snip />
>
>> If a Wiki isn't open to community input ( where "community" here means
>> *users*, not the typical Apache definition of "community" meaning the
>> *committers*), then what is it for?  Committers can already post to
>
> I Agree with Craig.

ditto. Derby has a "Uses of Derby" wiki page [1] and an
articles/tutorials/tips page [2]  that we encourage users to update.
It's fine for somebody to post a link to his/her own article (they are
the ones who are likely to know about it in the first place).

but methinks we should add a disclaimer to each page that says the derby
project doesn't verify/endorse the information or products provided at
any of those links.

 -jean

[1] http://wiki.apache.org/db-derby/UsesOfDerby
[2] http://wiki.apache.org/db-derby/WorkingWithDerby

> Yoav



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Joshua Slive <jo...@slive.ca>.
On 5/24/07, Yoav Shapira <yo...@apache.org> wrote:
> Hi,
>
> On 5/24/07, Craig McClanahan <cr...@apache.org> wrote:
> > On 5/23/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> > > We have a serious issue to determine, and I've asked for a 48 hour cooldown
> > > of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> > > the wiki become read-only for the conclusion of this decision.
> > >
> > >  [ X  ] Our httpd wiki is open to external resources for httpd.
> > >  [  ] External httpd resources are prohibited.
> <snip />
> > If a Wiki isn't open to community input ( where "community" here means
> > *users*, not the typical Apache definition of "community" meaning the
> > *committers*), then what is it for?  Committers can already post to
>
> I Agree with Craig.

I think there is a clear and reasonable middle ground:

External links are encouraged where they add substantial value, but
you may not link to your own pages or otherwise seek private benefits
from external links.

This has been the unwritten rule in the apache httpd docs for as long
as I remember. I have personally added many external links to the
regular docs to things written by apache contributors, but not to my
own pages.

Joshua.

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Yoav Shapira wrote:

> Hi,
>
> On 5/24/07, Craig McClanahan <cr...@apache.org> wrote:
>
>> On 5/23/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
>> > We have a serious issue to determine, and I've asked for a 48 hour
>> cooldown
>> > of wiki.apache.org/httpd/ to make a decision, and in the meantime
>> asked that
>> > the wiki become read-only for the conclusion of this decision.
>> >
>> >  [ X  ] Our httpd wiki is open to external resources for httpd.
>> >  [  ] External httpd resources are prohibited.
>
> <snip />
>
>> If a Wiki isn't open to community input ( where "community" here means
>> *users*, not the typical Apache definition of "community" meaning the
>> *committers*), then what is it for?  Committers can already post to
>
> I Agree with Craig.

ditto. Derby has a "Uses of Derby" wiki page [1] and an
articles/tutorials/tips page [2]  that we encourage users to update.
It's fine for somebody to post a link to his/her own article (they are
the ones who are likely to know about it in the first place).

but methinks we should add a disclaimer to each page that says the derby
project doesn't verify/endorse the information or products provided at
any of those links.

 -jean

[1] http://wiki.apache.org/db-derby/UsesOfDerby
[2] http://wiki.apache.org/db-derby/WorkingWithDerby

> Yoav



Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Yoav Shapira <yo...@apache.org>.
Hi,

On 5/24/07, Craig McClanahan <cr...@apache.org> wrote:
> On 5/23/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> > We have a serious issue to determine, and I've asked for a 48 hour cooldown
> > of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> > the wiki become read-only for the conclusion of this decision.
> >
> >  [ X  ] Our httpd wiki is open to external resources for httpd.
> >  [  ] External httpd resources are prohibited.
<snip />
> If a Wiki isn't open to community input ( where "community" here means
> *users*, not the typical Apache definition of "community" meaning the
> *committers*), then what is it for?  Committers can already post to

I Agree with Craig.

Yoav

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Yoav Shapira <yo...@apache.org>.
Hi,

On 5/24/07, Craig McClanahan <cr...@apache.org> wrote:
> On 5/23/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> > We have a serious issue to determine, and I've asked for a 48 hour cooldown
> > of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> > the wiki become read-only for the conclusion of this decision.
> >
> >  [ X  ] Our httpd wiki is open to external resources for httpd.
> >  [  ] External httpd resources are prohibited.
<snip />
> If a Wiki isn't open to community input ( where "community" here means
> *users*, not the typical Apache definition of "community" meaning the
> *committers*), then what is it for?  Committers can already post to

I Agree with Craig.

Yoav

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Eric Covener <co...@gmail.com>.
On 5/24/07, Craig McClanahan <cr...@apache.org> wrote:
> If a Wiki isn't open to community input ( where "community" here means
> *users*, not the typical Apache definition of "community" meaning the
> *committers*), then what is it for?

The wiki is for community input.  Not recognizing the difference
between contributed wiki content and external links to an ad-driven
site may influence your feelings on the matter.

-- 
Eric Covener
covener@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Craig McClanahan <cr...@apache.org>.
On 5/23/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> We have a serious issue to determine, and I've asked for a 48 hour cooldown
> of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> the wiki become read-only for the conclusion of this decision.
>
>  [  ] Our httpd wiki is open to external resources for httpd.
>  [  ] External httpd resources are prohibited.
>
> I mean this explicitly, obviously a link to MS/Sun/RedHat about their
> specific platform would be genuinely useful and relevant.
>
> I'm asking about askapache's external links, which have not been actually
> contributed to the foundation.  And we've never presumed that pointers to
> external links are resources under the AL.
>
> AskApache and megaspaz decided to start a pagechange war tonight, but the
> first point is to decide if such external 'helpful pages' are welcome.
>
> If so, AskApache was in the right, if not, megaspaz is right.  Either way,
> I immediately asked for infra to shutter the wiki to write access until this
> was resolved as a matter of POLICY.
>
> Once we determine a policy, I belive we owe megaspaz and AskApache a second
> chance once they are informed of the definative policy.
>
> Future wiki abuse would, of course, lead to account and IP blockage.  But
> I believe at this moment both acted in best-faith without any guidance from
> our project, and we need to have policies so folks can be responsible wiki
> users.
>
> This isn't the end-all of all possibilities, but let's discuss for 2 days
> and reopen the wiki with a concrete policy?
>



On 5/23/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> We have a serious issue to determine, and I've asked for a 48 hour cooldown
> of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> the wiki become read-only for the conclusion of this decision.
>
>  [  ] Our httpd wiki is open to external resources for httpd.
>  [  ] External httpd resources are prohibited.
>
> I mean this explicitly, obviously a link to MS/Sun/RedHat about their
> specific platform would be genuinely useful and relevant.
>
> I'm asking about askapache's external links, which have not been actually
> contributed to the foundation.  And we've never presumed that pointers to
> external links are resources under the AL.
>
> AskApache and megaspaz decided to start a pagechange war tonight, but the
> first point is to decide if such external 'helpful pages' are welcome.
>
> If so, AskApache was in the right, if not, megaspaz is right.  Either way,
> I immediately asked for infra to shutter the wiki to write access until this
> was resolved as a matter of POLICY.
>
> Once we determine a policy, I belive we owe megaspaz and AskApache a second
> chance once they are informed of the definative policy.
>
> Future wiki abuse would, of course, lead to account and IP blockage.  But
> I believe at this moment both acted in best-faith without any guidance from
> our project, and we need to have policies so folks can be responsible wiki
> users.
>
> This isn't the end-all of all possibilities, but let's discuss for 2 days
> and reopen the wiki with a concrete policy?
>

If a Wiki isn't open to community input ( where "community" here means
*users*, not the typical Apache definition of "community" meaning the
*committers*), then what is it for?  Committers can already post to
the project website itself, so they do not need any extra mechanism to
describe things that might be interesting.  Content from users, on the
other hand, can be either solicited (in which case external links are
perfectly ok) or censored (in which case nobody need bother ... they
can publish their own links on their own blogs, and let Google help
information seekers instead of the ASF helping them).

In the Apache projects I'm involved with, the only thing we kick off
of the wiki pages is spam.  It's a wiki ... it's user contributed
content, and not necessarily reflective of the opinions of the
project's developers.  But it is *incredibly* useful to the users of
the software we build.  Deal with that reality ... or close it down
... your choice.


> Bill
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Craig McClanahan <cr...@apache.org>.
On 5/23/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> We have a serious issue to determine, and I've asked for a 48 hour cooldown
> of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> the wiki become read-only for the conclusion of this decision.
>
>  [  ] Our httpd wiki is open to external resources for httpd.
>  [  ] External httpd resources are prohibited.
>
> I mean this explicitly, obviously a link to MS/Sun/RedHat about their
> specific platform would be genuinely useful and relevant.
>
> I'm asking about askapache's external links, which have not been actually
> contributed to the foundation.  And we've never presumed that pointers to
> external links are resources under the AL.
>
> AskApache and megaspaz decided to start a pagechange war tonight, but the
> first point is to decide if such external 'helpful pages' are welcome.
>
> If so, AskApache was in the right, if not, megaspaz is right.  Either way,
> I immediately asked for infra to shutter the wiki to write access until this
> was resolved as a matter of POLICY.
>
> Once we determine a policy, I belive we owe megaspaz and AskApache a second
> chance once they are informed of the definative policy.
>
> Future wiki abuse would, of course, lead to account and IP blockage.  But
> I believe at this moment both acted in best-faith without any guidance from
> our project, and we need to have policies so folks can be responsible wiki
> users.
>
> This isn't the end-all of all possibilities, but let's discuss for 2 days
> and reopen the wiki with a concrete policy?
>



On 5/23/07, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> We have a serious issue to determine, and I've asked for a 48 hour cooldown
> of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> the wiki become read-only for the conclusion of this decision.
>
>  [  ] Our httpd wiki is open to external resources for httpd.
>  [  ] External httpd resources are prohibited.
>
> I mean this explicitly, obviously a link to MS/Sun/RedHat about their
> specific platform would be genuinely useful and relevant.
>
> I'm asking about askapache's external links, which have not been actually
> contributed to the foundation.  And we've never presumed that pointers to
> external links are resources under the AL.
>
> AskApache and megaspaz decided to start a pagechange war tonight, but the
> first point is to decide if such external 'helpful pages' are welcome.
>
> If so, AskApache was in the right, if not, megaspaz is right.  Either way,
> I immediately asked for infra to shutter the wiki to write access until this
> was resolved as a matter of POLICY.
>
> Once we determine a policy, I belive we owe megaspaz and AskApache a second
> chance once they are informed of the definative policy.
>
> Future wiki abuse would, of course, lead to account and IP blockage.  But
> I believe at this moment both acted in best-faith without any guidance from
> our project, and we need to have policies so folks can be responsible wiki
> users.
>
> This isn't the end-all of all possibilities, but let's discuss for 2 days
> and reopen the wiki with a concrete policy?
>

If a Wiki isn't open to community input ( where "community" here means
*users*, not the typical Apache definition of "community" meaning the
*committers*), then what is it for?  Committers can already post to
the project website itself, so they do not need any extra mechanism to
describe things that might be interesting.  Content from users, on the
other hand, can be either solicited (in which case external links are
perfectly ok) or censored (in which case nobody need bother ... they
can publish their own links on their own blogs, and let Google help
information seekers instead of the ASF helping them).

In the Apache projects I'm involved with, the only thing we kick off
of the wiki pages is spam.  It's a wiki ... it's user contributed
content, and not necessarily reflective of the opinions of the
project's developers.  But it is *incredibly* useful to the users of
the software we build.  Deal with that reality ... or close it down
... your choice.


> Bill
>
>
>

Re: [Issue] External links @ the wiki, aka pagechange wars

Posted by Paul Querna <ch...@force-elite.com>.
William A. Rowe, Jr. wrote:
> We have a serious issue to determine, and I've asked for a 48 hour cooldown
> of wiki.apache.org/httpd/ to make a decision, and in the meantime asked that
> the wiki become read-only for the conclusion of this decision.
> 
>  [XX] Our httpd wiki is open to external resources for httpd.
>  [  ] External httpd resources are prohibited.
> 
> I mean this explicitly, obviously a link to MS/Sun/RedHat about their
> specific platform would be genuinely useful and relevant.

I believe that Wikis must be able to link to external sites -- just like
we do in the regular documentation.

However, just like the the regular documentation, these links are
generally restricted to Vendors, or other long standing and stable
sites. (or... example.com)

I believe we can look to wikipedia's linking policy as a good example of
how to build a 'policy' that people can understand:

http://en.wikipedia.org/wiki/Wikipedia:External_links

In this case: AdSense covered personal blogs especially from people who
do not contribute in other mediums doesn't seem like a good place to be
linking to.

On the revision war: I don't like it;  I do believe AskApache's link
should be removed.  I don't blame megaspaz, he was using the tools
available, trying to communicate with AskApache that the link was
unacceptable.  The larger problem is that the AskApache person has
never, AFAIK, made themselves known on the mailing list, or other
mediums, making it impossible to communicate with them in other manners.

On a policy: My opinion doesn't fit into a hard and fast rule, and
rather relies upon discretion.

-Paul