From: Vincenzo Ciancia <vincenzo_mlRE.MOVE@yahoo.it>
To: caml-list@inria.fr
Subject: The madness of ignoring people
Date: Sat, 20 Nov 2004 23:43:22 +0100 [thread overview]
Message-ID: <200411202343.22273.vincenzo_mlRE.MOVE@yahoo.it> (raw)
In-Reply-To: <Pine.LNX.4.61.0411202210230.1123@home.oyster.ru>
On Saturday 20 November 2004 20:17, malc wrote:
> I had hoped that this will
> result in some reaction, if not from Inria developers then from OCaml
> users, alas this was not the case.
I don't understand why academic environments producing free software
often tend to deliberately ignore people contributions. Maybe it is
normal that your feature has no users (yet), and so there is no people
interested, but it's absolutely NOT normal that people at inria just
ignore it - just like it's not normal that they sometimes don't answer
at all nontrivial technical questions about ocaml that _only them_ can
answer.
I know, compilers and mailing lists are for free, but there is not a
wide support network for ocaml, as there is, for example, for many
software projects such as gcc, or the GNU operating system and so on,
so the only place where somebody can ask for help about ocaml is here.
And to get back on your issue about the patch, I see it's frustrating to
be just ignored, and it's a pity to force people, who might have worked
hard, and for free, in _their_ free time, to stop contributing, because
they get frustrated by being ignored, without at least explaining the
reason. I've seen this on other mailing lists in the past, and in case
someone is going to ask, no, it's not about contributions I made (there
is no such thing :) ) - but of course I asked unanswered non-trivial
technical question which I think is the other side of the same coin
(wondering if this phrase makes sense in english, translated in italian
it does).
V.
next prev parent reply other threads:[~2004-11-20 22:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 10:18 Native executable symtable Alex Baretta
2004-11-11 10:39 ` [Caml-list] " Nicolas Cannasse
2004-11-11 11:09 ` Luca Pascali
2004-11-11 11:55 ` Keith Wansbrough
2004-11-11 12:09 ` Luca Pascali
2004-11-11 12:28 ` Keith Wansbrough
2004-11-11 12:42 ` Luca Pascali
2004-11-11 16:09 ` Richard Jones
2004-11-20 15:44 ` Luca Pascali
2004-11-20 16:03 ` malc
2004-11-20 18:01 ` Alex Baretta
2004-11-20 18:06 ` malc
2004-11-20 18:53 ` Alex Baretta
2004-11-20 19:17 ` malc
2004-11-20 20:07 ` Ritesh Kumar
2004-11-20 22:43 ` Vincenzo Ciancia [this message]
2004-11-20 23:10 ` [Caml-list] The madness of ignoring people malc
2004-11-20 23:25 ` Vincenzo Ciancia
2004-11-21 12:51 ` skaller
2004-11-21 14:14 ` Vincenzo Ciancia
2004-11-21 14:30 ` malc
2004-11-21 3:37 ` [Caml-list] Native executable symtable skaller
2004-11-21 15:59 ` Richard Jones
2004-11-21 20:29 ` skaller
2004-11-21 20:39 ` malc
2004-11-21 23:30 ` Richard W.M. Jones
2004-11-22 3:25 ` skaller
2004-11-21 20:42 ` Jean-Marie Gaillourdet
2004-11-21 18:31 ` Ritesh Kumar
2004-11-21 23:33 ` Richard Jones
2004-11-21 21:15 ` skaller
2004-11-11 16:23 ` David Brown
2004-11-11 17:27 ` Xavier Leroy
2004-11-11 18:48 ` Alex Baretta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200411202343.22273.vincenzo_mlRE.MOVE@yahoo.it \
--to=vincenzo_mlre.move@yahoo.it \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox