bump clojure version and correct spec ns's #2
Conversation
|
Can you review and merge this one please? |
|
@dball Any love for this PR? |
|
Hi Mike - thanks for sharing this. We've been remiss caring for our open source libraries. I know it's frustrating, and I'm sorry. We're trying to turn over a new leaf though! But our lawyers want to take a minute and make sure there's nothing the company should worry about accepting third-party contributions. It's a bit silly IMO for something this trivial but that's one of the growing pains when you're no longer a "5 people in a garage" sized startup. My hope is that next week, or the week after, we'll have clear guidance on what, if anything we need to do (and in this case, I sure hope that's "just merge it"). Thanks for your patience and hopefully we'll get unstuck soon!
|
|
He just bumped the version from 1.9.0-alpha10 to 1.9.0 ... it would've taken you less time to just make the same fix yourself, and merge it, than to write that essay 😛 |
|
2019 bump |
|
Does someone want to just officially fork this project and deploy their own builds to Clojars? I'm currently using @kjothen's fork, on top of which I have another critical fix: kjothen/useful-specs@kjothen:master...WhittlesJr:master I don't think EPL-1.0 prevents deploying forked versions to Clojars, does it? I know @jffry has said (a year ago) that they're waiting for their lawyers, but if @SparkFund can't even take care of something as trivial and critical as this after almost a year and a half, it really seems to be just abandoned. |
|
A candidate for transfer of ownership to https://github.com/clj-commons perhaps @danielcompton? |
|
Perhaps, although SparkFund is still around and may want to keep maintaining this project? Also, it probably doesn’t meet the notability requirements based on Clojars downloads: https://clojars.org/sparkfund/useful-specs |
No description provided.