Hi folks Today we are incredibly excited to announce Clojurists Together <https://clojuriststogether.org/>. The goal of Clojurists Together is to support important Clojure projects, by pooling donations from companies and individuals in the Clojure community and then funding project maintainers.
The Clojurists Together model is based off the successful Ruby Together <https://rubytogether.org> project, which has been running for 2.5 years now. It is run by a committee <https://clojuriststogether.org/team/> of Clojure community members and lives under the Clojars organisation. Being part of Clojars allows us to accept 501(c)3 charitable donations via the SFC <https://sfconservancy.org/>. We’ve been (slowly) working on this for more than a year now, and are looking forward to getting your feedback on it. The announcement post <https://clojuriststogether.org/news/introducing-clojurists-together/> has more details, but briefly, there are two sides to Clojurists Together: Companies and individuals, and open source maintainers. *Companies and individuals* Companies and individuals sign up for a monthly donation to support Clojurists Together at a tier they choose. Different tiers afford different benefits. Company tiers are here <https://clojuriststogether.org/companies/>, individual tiers are here <https://clojuriststogether.org/developers/>. Every quarter, companies are surveyed to find out which tools, libraries, and areas of the Clojure ecosystem they think could be improved, or are important to them. We then compile that information and use it to help us pick projects that will have the biggest impact. *Open Source Maintainers* Every quarter open source maintainers can submit their project for funding for the next quarterly funding period. You can see more on the application here <https://clojuriststogether.org/open-source/>. We look through the applications, and pick the projects that can make the biggest impact. We fund projects based on the amount of support we get. The more support we get from companies and individuals, the more projects we can support, and the more hours we can pay them for. *What now?* - Encourage your managers to sign up for a company membership <https://clojuriststogether.org/companies/>. For the next month, any company or person that signs up will be marked as a founding member. - If you are an open source maintainer, consider applying for funding <https://clojuriststogether.org/open-source/>. - If you are an individual developer, consider signing up for a developer membership <https://clojuriststogether.org/open-source/>. - Spread the word to other people you know that use Clojure commercially. - If you're a designer, and have some time to help us improve the site design, logo, e.t.c. that would be incredible. Please contact us off list for more on this. *Questions?* There may be some mistakes or things that don’t look right in there. Please let us know if you have any questions, either here, or off-list at h...@clojuriststogether.org. This project is for the Clojure community, so we want your input on this. What works well, what doesn’t work for you, what would you like to see? Thanks, from the Clojurists Together Committee <https://clojuriststogether.org/team/>: Toby Crawley, Bridget Hilyer, Maria Geller, Devin Walters, Daniel Solano Gómez, Larry Staton Jr., Daniel Compton. -- 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.
