Document the circuit process of RGB LED setup like what components are used (with details), pin configuration (clearly label the pins on the RGB LED and other components). Use pictures and circuit diagrams.
From pull request #87 @SwindleA noticed that after the merge of develop to main (with the intention of removing develop branch), we need to update he asciidoc-build.yml so that the documentation is built when changes are pushed to main.
Create and implement a template so that when users of our library attempt to submit an issue, they are in a more legible and concise format. If you attempt to submit an issue on Micronaut's Website it will ask for several options. Let's start by creating templates for a Bug Report and a Feature Request
Create and implement an 'Improve this Doc' button which, when inserted into our documentation, allows the user to create a pull request suggesting changes to our documentation. An example can be found in the top right corner of the Micronaut Guide
This repository needs a major cleanup. I found a lot of compiler-generated files (.class) files that got checked into the repo in the develop branch. For example, files in the components/bin/main/com/opensourcewithslu/components/controllers directory. In fact, it seems that the entire bin directory should not be part of the repository (bin, indicates binary, meaning generated files).
Please remove these files from the repo and update the .gitignore file to no longer allow such files into the repo.
The repository has a develop branch that has many commits that are not in main. This needs to be resolved, we don't want to have long-lived develop branches. Instead, the main branch should have the latest and greatest work. Feature branches (off main) should be used to develop new features and resolve bugs.
As part of our documentation, create (or copy from Micronaut's Example) a set of community guidelines for those who wish to participate in the contribution/discussion of our library
Create a detailed guide on how a developer would go about creating support for one of our already-supported hardware components. This should walk a potential developer through the exact steps they would need to take to mark a components support as completed. This should include 1. Circuit Building 2. Python testing 3. Java Implementation 4. Micronaut Integration 5. Controller Implementation 6. Documentation. This guide should be included in the "Contributing to the Library" section of our documentation. This would be a great first issue for any new developers joining the project to get quickly up to speed with the development process.
May be an SPI component, may be I2C, may be DigitalOutput, answer is unclear. Unfortunately CrowPi does not have support for this component so code will have to be handled manually
As discussed with Jeff, all contributors to the project should have to sign a CLA stating their guidelines for contribution. An example of this be found at Micronaut's website and they use cla-assistant to implement theirs. Completion of this issue also includes directions on how to fill out the CLA in the "Contributing to the Library" section of the docs