On Apr 15, 5:07 pm, Stuart Sierra <the.stuart.sie...@gmail.com> wrote:
> On Apr 15, 2:10 pm, "rzeze...@gmail.com" <rzeze...@gmail.com> wrote:
>
> > P.S. I don't want to get off-track, but I also don't understand why
> > ClojureCLR or clojurescript are included in Contrib. I also don't
> > understand why test files are not under their own top level dir? I
> > think that is a good convention and allows for easier tooling.
>
> The answer to all these questions is that: contrib has grown
> organically, without anyone imposing structure. Rich Hickey has taken
> a largely hands-off approach, allowing us to use contrib as a sandbox
> to share useful clojure code.
>
> I think it's valuable to have contrib as a sandbox. But this
> discussion shows it's also valuable to have Clojure libraries with
> their own external dependencies.
>
> Contrib right now is just an SVN repo, so it's pretty limited in terms
> of what it can do. If we want to handle multiple projects, with
> different dependencies, we need a more sophisticated system. We can
> try to piggyback on an existing Java system like Maven or Ivy, or
> start from scratch. But someone(s) will then have to take
> responsibility for maintaining that repository.
>
> -Stuart Sierra
I understand that Contrib is "by the people" but I still find it's
structure awkward at times. Almost every project I come across puts
the test related code and resources under a top level "test"
directory. I guess it could be argued as a "cargo cult" convention,
but I still think it makes the most sense and is easier for dev tools.
That aside, I agree Contrib is a sandbox, but how big of a sandbox is
it? That's the question I pose. I think it's irrational to put every
Clojure library/framework that comes along into Contrib, because it
becomes a Tower of Babel and ultimately fails. If someone wants to
publish a Clojure library, then it's simple enough to post it up on
GitHub, or what have you, and send a link to the Google group.
Along with the Core incubator idea, I could also picture Contrib as
something similar to Haskell with Batteries. A top selection of user
contributed libraries that add major value to the core. I feel duck-
streams is one such example.
I just hope, whatever is decided upon, that Contrib stays *TRULY*
simple and elegant. What may seem fine to us could look like a
disaster to a Clojure/Java newcomer. If we want the language to grow,
it needs to be, above all, accessible. I think the Clojure in a Box
(did I get that right?) is a perfect example of what I mean.
Sorry if I'm getting too theoretical. I'll let the pragmatics get to
work now.
--~--~---------~--~----~------------~-------~--~----~
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
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
-~----------~----~----~----~------~----~------~--~---
