Hi Guilherme,

I am not a Clojure developer (I only use it), so maybe I'm speaking
out of line. I would first like to thank you for the initiative; as an
industry, I believe we direly need more quantitative, scientific
studies of our practices, so I'm really happy to see this.

There is of course a lot of social dynamics that cannot be captured
from code commits alone. For example, if Rich was to step down (for
whatever reason), I would be much more worried about the direction of
the project than about the technical skills required to understand and
grow the code base: to my somewhat external eyes, Rich's role of
refusing contributions and setting a clear direction for the language
is at least as important as any code he writes himself. I love Clojure
because it's clear, from usage, that there is a single, strong,
unified vision behind it. I'm not saying nobody shares Rich's
aesthetics, but at the very least it would take time for any
replacement to earn the social authority that Rich has (it is, after
all, his language).

As for the truck factor computation, have you considered weighing the
relative importance of different files in a project? Something like
the inverse of churn, or taking into account the last modification
date? If a file has not been touched in two years, does it really
matter who wrote it? Even the author will probably need to read it
very carefully should there ever be a need to change it.

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to