Dev note
This commit is contained in:
parent
22eb5e0665
commit
c90c72f4b8
1 changed files with 6 additions and 5 deletions
11
doc/dev.md
11
doc/dev.md
|
|
@ -24,11 +24,12 @@ $ git submodule update --recursive
|
|||
|
||||
When adding libraries to babashka, consider these evaluation criteria:
|
||||
|
||||
- Would adding the library or class extend the reach of babashka to more
|
||||
libraries in the Clojure eco-system?
|
||||
- Is the library or class useful for general purpose scripting?
|
||||
- Could the functionality be met by shelling out to another CLI or be written as
|
||||
a small layer over an existing CLI (like `babashka.curl`) instead?
|
||||
- Adding the library or class extends the reach of babashka to more libraries in
|
||||
the Clojure eco-system.
|
||||
- The library or class useful for general purpose scripting or accomplishing
|
||||
useful devops tasks.
|
||||
- The functionality can't be met by shelling out to another CLI or can't be
|
||||
written as a small layer over an existing CLI (like `babashka.curl`) instead.
|
||||
|
||||
If none of the criteria are met, but adding a feature is still useful to a
|
||||
particular company or niche audience, it can still be added when hidden behind a
|
||||
|
|
|
|||
Loading…
Reference in a new issue