On Mon, Nov 23, 2009 at 11:25 AM, Andreas Schweigstill
<andreas_at_schweigstill.de> wrote:
> Hello!
>
> Ciprian Dorin, Craciun schrieb:
>> I agree with this (that a pointer to the documentation is the best
>> solution). But the way someone says it makes the difference between
>> "this is where your question is answered", and "you should have known
>> better". (And this usually makes a difference for a newbie.)
>
> Especially on this mailing list there are lots of people who say: "This
> project is highly important for my company and me, so I *won't* RTFM and
> prepare myself but instead require the best support for free from the
> community. The community should be proud to be allowed to support me!"
Initially I didn't want to continue anymore with this thread, but
it seems I'm too weak... :)
So, nowhere in my posts I've implied <<project is highly important
for my company and me, so I *won't* RTFM and [...]>>. But instead if
you read more closely my post above you'll see: <<[...] it makes the
difference between "this is where your question is answered", and "you
should have known better>>.
>> Agree again. But a mailing list usually provides a quicker
>> solution, and saves wasted time (for the user).
>
> So what? There are no service level agreements between a normal user
> and a community mailing list.
>
>> Agree again. But quick answers are usually more useful than an
>> hour spend reading a documentation.
>
> So why not make a contract with a paid consultant?
And that's why no-one is obliged to reply to posts...
>> This I don't agree with. For example I'm subscribed to about 50
>> mailing lists, and I usually only read the subject, and if it matches
>> with my interest then I look closer. Thus no great overhead.
>
> But that means that about thousand people have to spend one second just
> to read the subject. This is more than a quarter of an hour. So this
> creates costs of about 20$ to the community.
So then it means that your reply and my new one just costed the
entire community another 40$... :(
>> As I said previously I've read the book once a few years ago, but
>> forgot the small details. Thus I didn't see any point in rereading the
>> documentation every year, just to keep up with the "fine prints"...
>
> It is not neccessary to read the book once a year but prior to write
> questions to the mailing list.
>
>> If the same issue keeps popping up every once in a while, then it
>> means that the problem in question raises from counter-intuitive
>> behavior of the tool. So maybe the tool should be enhanced so that if
>> a user uses a `@` in the file name and there is an error, a suggestion
>> should be printed.
>
> Subversion is used in lots of shell scripts and makefiles, so it would
> be highly risky to change it's behaviour.
Here I agree with you. I didn't proposed to update the behavior,
but just maybe to show a notice to the user in case an error happens
and the file name contains a '@'.
> Regards
> Andreas Schweigstill
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2423264
Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-11-23 11:14:21 CET