First off, I just want to say that this is a fantastic project and I've found it immensely useful for keeping tabs on my dog while we are hiking out of cell range. There really aren't viable off the shelf alternatives for what I needed, so ripple has been a lifesaver in that regard.
This entire project represents an large amount of work, and being something that you seem to have pursued as a hobby I totally understand why you don't want to deal with debates on future development, other people's pull requests, and everything else that comes along with being an open source maintainer. That being said, at this point the binaries have been publicly distributed (probably with roughly ~hundreds of users), and you are both selling hardware that utilizes those binaries and selling an android app that interfaces with them.
I hope that this doesn't come across as accusatory, because honestly I don't think you have done anything wrong, I totally understand being protective of our own projects. But, if any opensource libraries or code was used in these binaries, or even the android app, both projects should have appropriate licenses according to what libraries were used. Normally for a small, single developer project on github like this it wouldn't be a big deal, but considering that money is changing hands for the android app, it is simply not fair to anyone who worked on open source project that has been incorporated into this work to not have it properly licensed.
If you need any help figuring out what your license options are based on the libraries used I would happy to assist, and there are a number of good online resources available. But we can't figure out the license until you fully acknowledge any other software that was used and give credit where it is due.
First off, I just want to say that this is a fantastic project and I've found it immensely useful for keeping tabs on my dog while we are hiking out of cell range. There really aren't viable off the shelf alternatives for what I needed, so ripple has been a lifesaver in that regard.
This entire project represents an large amount of work, and being something that you seem to have pursued as a hobby I totally understand why you don't want to deal with debates on future development, other people's pull requests, and everything else that comes along with being an open source maintainer. That being said, at this point the binaries have been publicly distributed (probably with roughly ~hundreds of users), and you are both selling hardware that utilizes those binaries and selling an android app that interfaces with them.
I hope that this doesn't come across as accusatory, because honestly I don't think you have done anything wrong, I totally understand being protective of our own projects. But, if any opensource libraries or code was used in these binaries, or even the android app, both projects should have appropriate licenses according to what libraries were used. Normally for a small, single developer project on github like this it wouldn't be a big deal, but considering that money is changing hands for the android app, it is simply not fair to anyone who worked on open source project that has been incorporated into this work to not have it properly licensed.
If you need any help figuring out what your license options are based on the libraries used I would happy to assist, and there are a number of good online resources available. But we can't figure out the license until you fully acknowledge any other software that was used and give credit where it is due.
Thank you for your consideration.