awesome-clojure-likes
awesome-clojure-likes copied to clipboard
chr15m
"Actively developed"
Should actively developed projects be indicated? contributing.md only says the project status should be included if the project is not actively maintained. Some of the listed languages (Clojerl, Joker, Ferret, Toccata) are actively worked on right now but lack the label "actively developed", which makes the reader question if they're less active than those with the label.
Interesting idea. Couple of thoughts about this:
-
I wonder if there are tools like "badges" that we could use to indicate GitHub stars and last commit date etc.? I did a cursory search but I couldn't find anything.
-
Now that I think of it, I guess "actively maintained" is a bit loaded. Some software does not receive frequent updates because it is basically complete. For example, consider GNU Make which has not had a release since 2016 but obviously works fine, and is used every day in thousands of projects. Similarly, I am co-maintainer of Wisp on that list and whilst it is very infrequently updated it basically works fine as a "homoiconic JavaScript" without requiring many further changes.
I suppose at the end of the day the thing to do is give people the information and let them make up their own minds.
I wonder if there are tools like "badges" that we could use to indicate GitHub stars and last commit date etc.?
For a project list repo of mine I've written a script that takes files containing data about each project (example; that's a properties file, not YAML) and then queries the GitHub GraphQL API for the star count and the last commit date to generate the README.md. It doesn't use anything fancy to compose the query; it works with GraphQL fragments as strings. The script should be easy to port to or reimplement in a more expressive language like Clojure. As a bonus you will get your repository recognized as a Clojure repository by GitHub when you commit it.
I am co-maintainer of Wisp on that list and whilst it is very infrequently updated it basically works fine as a "homoiconic JavaScript" without requiring many further changes.
You could establish a standard set of labels and explain their meaning in the document. Projects that don't get updates because they don't need them could be marked as "mature" or "finished" rather than "dormant".
@dbohdan both good ideas, thank you. I will try to find some time to get to this if somebody else doesn't PR it first.