I like BernardH's idea of doing it anonymously; if nobody from Core minds, we could set up an anonymous survey to see how much interest there is.
cej38, your suggestions are very sound----personally, I would love to see curated, distilled APIs for common things a Clojure programmer needs to do from Java or JavaScript, not just I/O. However, it's ultimately a matter of what developers want to do, and what core people think should be done. So long as work leads to improvement of the Clojure language and ecosystem----which happens continually anyway----I don't think one should care where funds go. In the long term, offering bounties for specific things might be a way to spur fast progress of needed things, but I feel that should only be tried after basic community funding works. It seems like open source software development settles into a groove that isn't Pareto efficient, even if it's much better than closed source. Think about how much time we all invest in learning and developing Clojure. The more the ecosystem expands, the more our investments of learning and development come to be worth, and the less likely we are to lose them to some other technology taking over down the road. And yet the ecosystem itself only gets worked on as a second priority to other work. It's a dilemma: either you get unsharable, secret technology worked on full-time, or you get sharable technology part-time (with maintenance dependent on the vicissitudes of life). I'd like to think a generous and not overly expectatious community can transcend it. On Mar 23, 7:12 am, cej38 <junkerme...@gmail.com> wrote: > I am willing to contribute, and have in the past, but I think that > instead of just contributing some cash and hoping things that we want > will be worked on, I would propose that we structure it some. In > fact, I come up with a few projects that could be of use to the whole > community, or at least a large subset of the community. The clojure/ > core team could determine how much time that they think it will take > to finish a project (or at least make real progress), and then have a > fundraising goal for that project. It would be kinda like we are > hiring them to work on the projects that we want to see finished. > > A few ideas of topics: > clojure-in-clojure > a standard IO API that different VM implementations support > Liebke's map/reduce > fleshing out clojure.contrib libraries to bring them back to par with > contrib 1.2 (a standard API page like what was had through > clojure.contrib 1.2 would be REALLY awsome) > faster numerics -- 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
