I have no expectations for anyone. Clojars has been free to use (push/pull,individual/corp) since it started. I have no intentions of changing that. My belief is there is value to maintenance/dev, and hope that it can financed in a sustainable way. If it can be done by being spread out among people deriving that value, then even better.
I'll plan to set up something for individuals in the future, though that will wait until after I talk to businesses. As for numbers, I don't have a direct answer for you. It comes down to the value the company can get back. I'm starting with conversations with businesses that are interested, and will determine from there. On Fri, Sep 26, 2014 at 1:44 PM, Howard M. Lewis Ship <hls...@gmail.com> wrote: > There's a number of options out there for collecting small recurring > payments. I already make regular payments to Wikipedia and a couple of > others (including GitHub), and would be willing to kick in some money > towards Clojars. > > The question is: what is a reasonable amount? This is tricky; I'm > comfortable, as a self-employed, individual developer, to kick in $3-$5 per > month. What kind of numbers are you looking at for the more corporate users > of Clojars? What would you expect for an organization that simply pulls > for Clojars, vs. one that distributes code via Clojars? > > > On Friday, 26 September 2014 08:09:55 UTC-7, Nelson Morris wrote: >> >> Clojars has become a critical part of the clojure ecosystem. As a small >> sample, it hosts artifacts for: >> >> * Web development - ring, compojure, hoplon, hiccup, enlive, friend, >> immutant >> * Tooling - lein templates/plugins, cider-nrepl, clojure-complete, >> gorilla-repl >> * Clojurescript - lein-cljsbuild, austin, om, reagent, sente >> * Misc - Clojurewerkz projects, storm, incanter, clj-time, cheshire, >> clj-http, >> * Company projects - pedestal, dommy, schema >> >> Vulnerabilities like shellshock and heartbleed always require quick >> response. An insecure clojars service could lead to compromised systems in >> multiple companies, potentially any project that used an artifact from it. >> A similar situation exist for maven central, rubygems, apt, and other >> repositories. >> >> There are other administration tasks such as verifying backups, server >> updates, better response time to deletion requests, and potentially the >> need to handle unexpected downtime. Additionally, development time is >> needed for the releases repo w/ signatures, CDN deployments, additional UI >> work, and more. >> >> Currently clojars is maintained by a collaboration between 3 very spare >> time people. Vulnerabilities get attention due to the damage potential. >> However, being a spare time project many of the other tasks languish until >> required, or wait behind the queue of life's requirements. I'd love to >> change that. >> >> I've been a co-maintainer for clojars for two years. I implemented the >> https deployment, better search, and download statistics for clojars. I've >> handled most of the deletion requests over the past year. I've also got >> work in leiningen including almost everything related to dependency >> resolution and trees. >> >> I want your help. >> >> Do you work at a company that runs clojure in production? Does it have a >> financial interest in a well maintained and secure clojars service? Would >> it be interested in sponsorships, business features, or another arrangement >> that produces value? Then I request you email me. I want to create a >> sustainable path for this critical piece of the clojure ecosystem. >> >> Thanks, >> Nelson Morris >> > -- > 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. > -- 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.
