I had a great discussion with Sean Corfield about this at ClojureWest, and had my own visions for CloJARS. It'd be great to collaborate.
I like the idea of a full-fledged Maven repo. The convenience of something like Grails BuildConfig.groovy to declare dependencies in one place, then have Ivy or a similar tool resolve all transitive dependencies<http://grails.org/doc/latest/guide/conf.html#ivy>, would be a mega win. There might be even easier wins too. - Integrated Twitter/Google account login to allow people to +1/-1 and comment on plugins. This would liven up the CloJARs environment to help discover what the most popular (useful?) plugins are, and give visibility to the ones that were 0.0.1, never updated, and are fundamentally broken - Tagging of plugins with keywords such as functionality descriptors can help users filter and identify to answer questions like "what plugins are available for user authentication in this ecosystem?" (with the ability to then review them based on scores and feedback from the last bullet) - It looks like there are problems with old plugins that no longer work with new versions of Clojure. An automated script that pulls every project down, runs it through Lein, and stores meta data about failure to be displayed in a table would be useful Signing is a useful requirement. When you design the signing requirement for submission to Clojars piece, try to design it to be extensible. Make signing one of a series of things that's checked. Another, to be developed in the future and "plugged into the system" (without re-writing it) could be adherence to Clojure coding conventions<http://en.wikibooks.org/wiki/Learning_Clojure/Coding_Conventions>. I'd go one step further, which may get flack from some people: if it doesn't have *tests*--which serve as a pseudo record of requirements, some evidence that thought has gone into dealing with special cases, and when leveraged correctly can greatly influence and improve design--it's not professional code. Personally, I'm perfectly fine with someone saying, "Hey guys! I made this cool whats-it-do and put it on my site: check it out! http://www.does-it-work-or-not-download-it-and-spend-a-day-trying-it-to-see.com"; I just think that when such a project is submitted to a community repository, a candidate to be depended on by others, some evidence of Care About Your Craft<http://pragprog.com/the-pragmatic-programmer/extracts/tips>and thinking about special cases (capturing them in automated, one command repeatable tests) is perfectly reasonable to be expected. It's about the community deciding it has higher standards than patchy, rushed, under-thought code as standards of its best products. So, obviously, a later plugin I would advocate is a pull from source, run lein test, reject if there are no/empty/failing tests. Seems like evolution of Clojars is a big win for the community. Good ideas on the proposal! On Sat, Apr 7, 2012 at 11:21 AM, Andrew Kondratovich < andrew.kondratov...@gmail.com> wrote: > Hello. > > My name is Andrew and I'm a student from Minsk (Belarus). > I've decided to participate in this year's GSoC. > > I want to contribute in Clojars system. I've talked to Phil > (technomancy) about plans of Clojars future development. With his > help, i've wrote a proposal and posted it to google-melange - > > http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/sparrow/5002 > . > > I would like to hear what other community members think about it, > listen to advice and answer the questions. > > Thanks. > > -- > 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
