Hi!
We have a number of Clojure projects relying heavily on Clojure core.async at Exoscale. From a glance, it seems most usage in the wild is rather directed at the ClojureScript ecosystem. As a sidenote, thanks for the library, coupled with transducers it gives us great way to test transforms in isolation.
While hitting an issue which could be a bug in the library (but we're only at the beginning of the investigation so far) I created a ticket[1] and had a quick glance at the open ticket issues.
I was surprised to see that no issues (open or closed) had seen acknowledgement since last August[2].
I'm well aware of the low resource availability at Cognitect and the obvious focus on projects with more reach such as Clojure itself, ClojureScript, and spec; so please
don't read this email as a complaint.
The situation did prompt a few questions which follow:
- Is the project considered depreciated from Cognitect's perspective?
- If not, is the project considered stable and maintenance only from Cognitect's perspective?
- As external contributors, is there anything we can do to improve the situation?
Cheers, and thanks for the library again.
- pyr
[1]:
https://dev.clojure.org/jira/browse/ASYNC-214 [2]:
https://dev.clojure.org/jira/secure/IssueNavigator.jspa?sorter/field=created&sorter/order=DESC