2011/4/19 Rich Hickey <richhic...@gmail.com>: > > On Apr 18, 2011, at 2:49 PM, Konrad Hinsen wrote: > >> On 18 Apr 2011, at 17:47, Laurent PETIT wrote: >> >>> The -?> and -?>> macros are currently inside "old", "soon to be >>> deprecated" clojure contrib. >> >> I must confess that I don't even know what those macros do, so I have no >> opinion. >> >> However, I think the question of "what will happen to module >> clojure.contrib.XXX" is of wider interest. Only very few >> modules/sublibraries have made it into the "new contrib". OK, many of the >> old ones (including some of mine) are experiments and probably not used by >> anyone any more. But there's a lot in between: useful and used code that for >> whatever reason does not satisfy the stricter criteria (whatever they are) >> of "new contrib". >> >> Concerning my own modules in old contrib, there are three that I use >> myself and that I am planning to maintain, independently of where they will >> end up: >> - clojure.contrib.monads >> - clojure.contrib.macro-utils >> - clojure.contrib.generic >> >> If nothing else is decided collectively, I'll maintain them as private >> projects on Google Codes or Bitbucket. >> >> > > The only criterion for migrating into new contrib is someone willing to do > the work of moving, and, subsequently, maintaining. > > This processes is emphatically not about deprecating the contrib libs, nor > pushing anything out. We had to work out the kinks in the new build/deploy > method, and that was done first for: > > Some brand new libs (e.g. unify, nrepl and finger trees) > Some of the most common others, as need arose and time permitted for the > core team. > > We *are* deprecating the old build process and packaging, but I would hope > anyone with any interest in any of the other contrib libs would please step > up and move them over. The only ones that will be left behind will be those > that die of neglect or disinterest. > > Stuart Sierra has documented the process here: > > http://dev.clojure.org/display/design/How+to+Create+New+Contrib+Projects > > and I'm sure will be willing to help out anyone with the desire to move a > lib. > > What you should not do is wait for someone else to move your favorite lib. > We've moved the ones we have time to do, and expect the community to do the > rest, with our help.
Hello Rich, thanks for the clarification. For sure, my email was a first step towards this direction : find in the general ml whether there is enough interest in he -?> and -?>> macros, before suggesting their migration either to clojure itself, or to a new clojure contrib. It seems to me that they've gotten the minimal community support, so now I'm officially volunteer to help get them out of clojure.contrib.core and into .... ? > > Special thanks to Stuart Sierra and Chas Emerick, who did a ton of work to > set this up. > > I hope that clarifies things, > > Rich > > -- > 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 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
