Open apatrida opened 2 years ago
Leaving out access's permision to my google drive
This project aimed to add features to a current open source project for our in-house needs, and then provide the community use of our solution for no charge. You are welcome to run the project with any permissions you want and choose online or offline. Even if our entire codebase was published open-source, you would still need to provide credentials to access your OAUTH services, and open-source would not prevent "dubious" behavior as you state.
A large portion of our extended features rely on in-house proprietary code that simply will not be open-sourced for a variety of reasons.
Furthermore, we don't see too many bug reports or feature requests, so we are not sure what you are referring to as "in limbo".
This project appears to have slowed down and has left a lot of nice features in limbo.
The code cannot be verified easily for security, because it isn't open-source.
The hosting of the site online by unknown vendor with invalid contact information is dubious for some users. The email given in the app doesn't work, so that is more dubious for some users.
You can open-source this and still have your hosted version with commercial offerings (i.e. image media server) but if you never even do that now, why are you holding the source in secret?
Sure, you want to make a commercial offering, but you haven't. So then what? This works goes into
/dev/null
?