Re[4]: [PEAR-QA] Documentation..
| From: | anatoly techtonik | Date: | Mon, 06 Dec 2004 23:50:14 +0000 |
| Subject: | Re[4]: [PEAR-QA] Documentation.. | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-2098@lists.php.net to get a copy of this message | ||
Hello Justin,
>> LS> why not just open a feature request with a link to the source ... i
>> LS> doubt any developer wouldnt be happy to add the example to the distro
>> LS> after a quick look over the source.
>>
>> Because it is not a feature request and dumb users like me are either
>> too lazy to contribute to stale closed community or don't have a proper
>> amount of imagination to draw association between Feature Request
>> and Example. It can be my only IMHO, but (RFE != Example for existing
>> feature).
JP> Stale? Closed? Are you trying to be a troll? If something hasn't been
JP> updated then point it out and it will be dealt with. QA is doing a
JP> good job trying to get maintainers for abandoned packages. *People are
JP> busy*. You have to understand that this is all done *for free*.
Stale means that there's no indication of PEAR's activity or it's
status. Stale also mean, that users can see the result of they work.
Their efforts are most of the time wasted and they can't get recognition.
Stale means that 7 voices is enough to rule another 200. Stale means,
that everybody seems to prefer to skip the problem than to solve it,
because everyb. has no time. Stale also means that there's no trust to
users. And hence no trust to developers.
Closed means, that only the person who contributed package can vote and
decide that other members can or cannot do. Users can't vote on new
features, can't propose ideas, can't share code or work on web-site
improvements. They can't work on getting PEAR better at all and those
people who can are too busy to do it themselves and the worse is that
these people do not allow others to do it. Why?
Yes, I am trolling. I'd like you to think about why am I doing this
and what signal I want to get on the output. I've got a solid POV and
I want you to make me change my mind.
But also I act like a user, who doesn't ask questions. He walks
through the site, reads what he want, downloads package and leaves.
Then he returns to the site to report something, leaves a note, which
stays for months, he hasn't got an appropriate response and he will
never return back. He is not a member of community. So far I'm here
to report something.
JP> This e-mail wasn't meant as a personal attack. Lukas suggested that
JP> you create a bug report with the example. It's the best place to put
JP> things like this. He was informing you, not criticising you.
His solution resembles a temporary stub for this "special case". It
seems like an intention to skip nuisance. I just wanted to inform, that
RFE is not a proper place for such Examples. I like critique and in
fact every my letter is it, because I can't do anything except
critisize (if you have already noted, I'm not a developer). Letters,
what can't help or doesn't contain any good ideas are spam. If any of
my letters is nonsense - point it. Even if after all my intentions are
not clear just ask me to leave and I will not return here. Perhaps
I'll post a patch or two, but this will be all I can do for yours.
Just ask and do not add me to spam filters. Again.
t
--