RV wrote:
> Peter Lairo wrote:
>> We are not suggesting that it would *eliminate* the need to talk to
>> real people, simply *reduce* it.
>>
>>> and that while better documentation (looking for volunteers.)
>>
>> Just copy and paste the reply you gave to Andrew on 13.08.01, edit it
>> to include all OS's and you've got yourself an excellent first page
>> for the brand new "One-Stop-Shop for people wanting to contribute
>> code" page. Just make sure to add a link to a qury with *easy2fix*
>> bugs ;)
>
>
> I might not know much (or anything?) abour computer programming but I am
> quite knowledgable about group process dynamics and development and I
> can tell you that pasting a static page with lots of pointers doesn't
> necessarily help "new" people to join the project. It actually makes it
> more intimidating. (How many poeple try to program a home device without
> reading the instructions? Most of them try to do that.)
>
> I think what Asa did, posting a personalized answer to a person who has
> shown interest in contributing code fixes, is more useful and at the
> end more efficient.
< Snip - more ponderings on something we all know: talking to people is
better than reading a manual.>
Did you even read the very FIRST sentence you quoted of me? Here it is
again: We are not suggesting that it would *eliminate* the need to talk
to real people, simply *reduce* it.
Neither extreme is the "more efficient" on its own. We need both. It
benefits noone to keep saying that personal contacts are "better" when
someone suggests to improve the structure. Currently, documentation and
structure are the weak link - let's talk about fixing it.
Obviously, we would all prefer a person who could show us the ropes. I
am merely suggesting that a well structured and concise "intro" *might*
help some people and maybe reduce "some" of the burden of those who are
experienced and could be doing other things. ...like fixing my bugs ;)
--
Regards,
Peter Lairo
