Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process for Contributing to Qwiic_Py #15

Open
fourstix opened this issue Jul 14, 2019 · 0 comments
Open

Process for Contributing to Qwiic_Py #15

fourstix opened this issue Jul 14, 2019 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@fourstix
Copy link

Hi,
I have some CircuitPython projects that I have written for Sparkfun Qwiic products:
Sparkfun_CircuitPython_QwiicAS2935
Sparkfun_CircuitPython_QwiicJoystick
Sparkfun_CircuitPython_QwiicRelay
Sparkfun_CircuitPython_QwiicTwist
(There's also one for Sparkfun_CircuitPython_QwiicKeyboard, but probably little interest in that.)
It's fairly easy to port them to use Qwiic_I2C_Py instead. What is the process should I follow for converting them to Qwiic_Py?

I believe I can follow the steps here to create the Qwiic_xxx_Py github repsitory in the format documented here, and I can publish them to PyPi if you wish as well. But how should I alert Sparkfun they are ready for harvesting?

Should I co-ordinate with Sparkfun to not duplicate work? Is there interest in my porting these projects for Qwiic_Py?
Thanks, fourstix

@santaimpersonator santaimpersonator self-assigned this Dec 28, 2019
@santaimpersonator santaimpersonator transferred this issue from sparkfun/qwiic_keypad_py Feb 19, 2021
@santaimpersonator santaimpersonator added the enhancement New feature or request label Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants