[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion file name restriction

From: Stefan Sperling <stsp_at_elego.de>
Date: Sat, 21 Nov 2009 14:47:34 +0100

On Sat, Nov 21, 2009 at 02:44:52PM +0200, Ciprian Dorin, Craciun wrote:
> On Sat, Nov 21, 2009 at 1:58 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> > [...]
> > It helps to read the book....
> >
> Thank you for your feedback. I shall try that.

I hope that you will enjoy reading and learning from the Subversion book.

> But on the other side, I want to make a small remark. The most
> important element of open source projects are their community. If
> there is no community, it means that there are no developers, and
> there are no users. Also from the community it stems something else:
> mutual non-profit help. By this I mean that if someone has a question
> (even the most silliest one), and he sends an email to the community
> mailing list, the usual outcome (depending on the community) is:
> * someone gives a polite answer correcting him, or pointing him to
> the correct place (like one of the repliers to this email has done);

I pointed you to the correct place in the documentation.
I did it because the other poster pointed you to the bug tracker,
and the bug tracker is not the place to get documentation.

> * he is ignored (usually happens with projects governed by
> elitists, which have forgotten that their were once newbies (I've seen
> a lot of these kind)); (and eventually the user will end-up RTFM, but
> mumbling because he has to loose a couple of hours reading the
> "Advanced" part of the (RT)FM just to clarify a very simple issue...)

Posts can also be ignored because no one has the time to read
them or answer to them, without any malicious intent.

> * or seldom someone just sends him to RTFM... (which is even worse
> than ignoring him in the first place, because now he's indirectly
> called an ignorant)...

I don't agree, at all, that sending an RTFM response is bad.
It is 101% good, provided the user gets pointed to the correct
place in the documentation.

If the answer to the question which was asked is in the documentation
already, then why not point people there instead of writing the
documentation again on the mailing list, duplicating efforts?

Writing good documentation takes a lot of time.
The authors of the book wrote the book so that they won't have to spend
time again and again answering questions they already answered.

Pointers to where people can find the most current documentation are
better than mailing list posts that can never be updated.
The documentation is being maintained, mailing list posts are simply
archived.

The official documentation tends to be more complete and well-written,
and is more suitable as learning material than mailing list posts,
because documentation can incrementally introduce concepts that build
on one another.

Pointing people to the documentation helps people help themselves,
because they might discover that the documentation contains a lot
of information, more than they need right now. But they may need more
information on other topics later and now know where to go to get it.

Locating information in the documentation is quicker than sending a
question to the mailing list and waiting for replies. It saves time.
Because sending a question to a huge list like this means that a couple
of hundred people will spend some of their time processing the question.
This makes the list a huge and valuable resource of expertise that we
all can tap into, but it should not be abused to get answers to questions
that are already answered by the documentation.

Of course, such questions pop up here, and that's fine since people are
free to ask anything. But they will most likely end up getting redirected
to the documentation, by people who have already read the documentation
and know where in the documentation the answer is located.

This is why I said "reading the book helps" -- I meant to suggest that
you should try to locate information there first, because it will save
you and everyone else time, and because it will give you a better
learning experience. This really is the "mutual help" you mentioned above,
and mutual implies effort on your part, too.
I could have worded it in a less grumpy way, but it was well intended.

> So my two cents opinion: rather than using an awesome tool, I
> would prefer to use a sh...ty tool, but with an awesome community...

I didn't mean to offend, sorry.

I tend to give quick RTFM responses to questions that pop up repeatedly,
and which are covered in the documentation (e.g. the "@" in filename
question comes up quite often and is documented).
If a question shows that something in the book is missing, I make changes
to the book either instead or in addition to answering the question on the
mailing list. This wasn't the case with your question, so you got the RTFM
response.

Stefan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2422781

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-21 14:48:31 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.