This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (15)
- # announcements (4)
- # aws (2)
- # bangalore-clj (7)
- # beginners (236)
- # calva (24)
- # cider (11)
- # cljs-dev (63)
- # clojure (141)
- # clojure-europe (3)
- # clojure-india (2)
- # clojure-italy (8)
- # clojure-nl (3)
- # clojure-spec (8)
- # clojure-uk (52)
- # clojured (1)
- # clojuredesign-podcast (4)
- # clojurescript (35)
- # clojutre (3)
- # community-development (1)
- # cursive (77)
- # data-science (1)
- # datomic (3)
- # emacs (13)
- # fulcro (7)
- # graalvm (78)
- # graphql (2)
- # nrepl (7)
- # off-topic (18)
- # pathom (25)
- # reagent (12)
- # reitit (31)
- # shadow-cljs (178)
- # spacemacs (7)
- # tools-deps (32)
- # xtdb (10)
- # yada (3)
interesting that I found a random Rich Hickey quote in this article https://feross.org/funding-experiment-recap/ wonder if it's a little out of context :thinking_face:
It doesn't seem out of context to me: https://gist.github.com/richhickey/1563cddea1002958f96e7ba9519972d9
I've been an OSS contributor for over 25 years at this point. I've never asked for money. Same as when I blogged very actively in the early 2000's while I was at Macromedia (Jeremy Allaire encouraged my team to start blogging) and I saw many blogs running ads to generate revenue and I decided I would never do that (and told my readers that).
But I made that conscious decision not to benefit financially (in any direct way) from my OSS or blogging work -- and in exchange I do not consider anyone entitled to anything from me: not my time, not bug fixes, not new features, nada. If you want something else, pay me as a consultant or contribute it yourself.
I like to think that all that time/effort spent has benefited me in indirect ways tho'...
I can only imagine how frustrating facing that entitlement is after putting so much work into giving the world something for free.
@U04V70XH6 That's a great model and stance. Which model do you prefer for more commercial open source ventures?
@UJY23QLS1 Not quite sure what you're asking there? How an OSS author/company can make a living? If your project is popular enough, offer consulting around it (which is basically what I said above).
That's what Cognitect does, essentially, and their previous incarnations too (back when they were originally a Ruby consultancy although I don't know how much OSS they did back then).
There are a lot of companies, large and small, that make their "living" from consulting services (including commercial support) based around the OSS project(s) that they maintain.
Yeah, I see how that can scale. I assumed you were referring to small, one-person projects, but that isn't a given. 👍
I'm fortunate to have a full time job that "allows" me to work on OSS for some time during work hours -- and that's been true for me for decades, partly because I've made it a condition of employment (and I won't work for companies that do not support OSS in some capacity).
Back when I did CFML for a living, I contributed to a lot of OSS frameworks (MVC, DI/AOP, ORM) and as a freelancer that enabled me to get paid gigs consulting on projects around those frameworks.
We are oss lovers at JUXT, but it's definitely hard to reconcile billing hours with OSS. Especially on projects like Edge. I spend a lot of my time making the docs nice and thinking about it. Nobody internally is knocking the door down for me to do those things, people are generally pretty happy internally. So am I producing value for the company? It's hard to measure.
Yeah, at WSN the general thinking is that if we use an OSS library, we can justify doing (some) work on it during the day. It's harder to justify working on OSS libraries that we don't use. It's why I've had to hand off
congomongo (in Clojure) and a bunch of stuff in CFML (now that we no longer use it).
JDBC stuff is core to what we do so that's easy to justify (even the docs 🙂 ).
core.memoize are fairly core as well.
tools.cli is less core these days.
clj-new is a "side project" 🙂