Hi @Gary126657 Gary - I’m stoked that you’re considering contributing to our little open source project 
I agree our guidelines could use some work to clear up the repo structure and guidelines.
CE-PiicoDev-Unified is the main unifying library
Device modules are found on their respective product pages / guides eg. the TMP117 temperature sensor has the following repo.
The PyPi package is purely for deployment/distribution - it’s mostly used by Raspberry Pi users since it downloads every PiicoDev driver file which is unnecessary for Pico/Microbit users.
Contributions should be made either to the Unified repo or to device repos.
The PyPi repo is a collection of the entire ecosystem at a moment in time and pushed to PyPi. We actually scrape all the individual repos to build this repo before deploying.
A side note about PR#13 - it’s unlikely we can merge the PR into the main branch because it introduces too much new code for Unified to cope with. You can see my discussion and some strategies here.
Given the delicate nature of keeping Unified… unifying, some user-changes are not viable to merge into the main branch (microbit restrictions), but represent a lot of value for the community. I’ve recently started curating outstanding contributions.
If you’d like to discuss your ideas before getting too far down the rabbit hole I’d love to! Good alignment will help us arrive at a solution that can be merged, or at the very least curated for other curious makers.
