This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-18
Channels
- # announcements (5)
- # aws (4)
- # babashka (30)
- # beginners (90)
- # calva (31)
- # clj-on-windows (16)
- # clojure (110)
- # clojure-dev (10)
- # clojure-europe (26)
- # clojure-nl (1)
- # clojure-norway (20)
- # clojure-spec (25)
- # clojure-uk (15)
- # clojured (2)
- # clojurescript (12)
- # code-reviews (2)
- # community-development (3)
- # conjure (14)
- # datomic (26)
- # defnpodcast (2)
- # events (1)
- # fulcro (17)
- # graalvm (8)
- # gratitude (1)
- # introduce-yourself (2)
- # jobs-discuss (7)
- # kaocha (6)
- # lsp (9)
- # luminus (5)
- # nextjournal (7)
- # observability (9)
- # off-topic (71)
- # portal (5)
- # practicalli (1)
- # rdf (21)
- # re-frame (15)
- # releases (1)
- # shadow-cljs (24)
- # testing (7)
- # tools-build (13)
- # tools-deps (14)
- # xtdb (7)
Hello! I am Gleb Eliseev, a member of the Freshcode team. We are developing an open source content curation platform designed for use in the Clojure ecosystem to easily and quickly find best practices for newcomers and developers who start their first pet project and are not active community members (https://github.com/clojure-garden/clojure-garden ). One of the main parts of our platform is the library ranking system. To build this ranking system, we need access to search for messages in the Clojurians Slack archive. We would like to access the archive database. (If required, we are ready to create an API for the clojurians-log/clojurians-log-v2 project.)
Hey all! Gleb had DM'd me regarding this and we thought it's best to discuss this in public. Since I/we (at LambdaIsland) are only maintaining the code (v1 and v2) which hosts the logs, we don't really "own" this user data. Hence I felt this is not my call to make and thus I leave it to the clojurians admins! If the clojurians admins decide this is something which should be allowed / a part of the v2, I'd be happy to look into it together with clojure.garden team to make it more robust/secure/ even anonymised if need be!
Thanks @U013MQC5YKD! The admins will discuss it today & get back to y'all.