Add README, Contribution guidelines and code of conduct #24
Conversation
|
|
||
| This document provides guidelines for contributing to the I-Ching-app. Please take a moment to review it to ensure a smooth and effective contribution process. | ||
|
|
||
| ## Code of conduct |
There was a problem hiding this comment.
IDK, I'm kinda' neutral on CoC ... but .. I guess it can make sense ... I was actually thinking of moving this under the encorpora "monorepo" - https://github.com/corpora-inc/encorpora ... but, each app having its own issues could be a good thing ...
I'm generally low-maintenance, low-effort on things like this .. I think it can be fine though ...
We probably do need a license though ... I guess I wort of lean APGL like I did with the main corpora software. The idea there is that teams can use it as they like internally but then they may love it so much that they want to get commercial support for their deployment at scale ... 🤔
https://github.com/corpora-inc/corpora?tab=AGPL-3.0-1-ov-file#readme
Anyways, I think we can merge this but I'm kinda' an oddball politically - mixed feelings on CoCs in general :D
| Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make are **greatly appreciated**. | ||
|
|
||
| 1. Fork the Project | ||
| 2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`) |
There was a problem hiding this comment.
I don't personally follow any feature/ convention ... I'm a free spirit when it comes to my code. I wrote this a long time ago (never finished) - https://skyl.github.io/bonsai/ - maybe I will use corpora to rewrite and finish it :). I have a very free-wheeling approach to process though ...
2 participants
Closes 👉 #16 #20