Open nperozzi opened 1 month ago
One more note: If we have a README file for each library, shouldn´t we separate the libraries into folders?
One more note: If we have a README file for each library, shouldn´t we separate the libraries into folders?
I don't think we need a README for each library. Most of them are easy to understand since they have code that references them. However, I do think that we should explain the sketches / envs, since we need to describe what the minimal setup is required for testing each one of them, and what the expected outcome is.
As a note: We had the libraries in separate folders a while back. But, in 6de6451610f1a4197224e9a18b1edc7b60533f7a I decided that we didn't really benefit from having two files in each folder, with the same name (like lib/timer/timer.cpp
and lib/timer/timer.h
).
Understood: no README for libraries but yes for the sketches/envs. 👍😄
NOTE: Now that I know that we can discuss topics as Issues, I will go nuts with the issues 😀 !!!
This issue is to discuss how to structure the README files. We talked about it once but I have little space in my memory so I forgot 😓 .
This is how I think we can structure README files (Largely inspired in kinx project and ChatGPT suggestions):
Main README:
README file in each library folder: