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

License ??? #1

Open
alterechtschreibung opened this issue Sep 23, 2012 · 8 comments
Open

License ??? #1

alterechtschreibung opened this issue Sep 23, 2012 · 8 comments

Comments

@alterechtschreibung
Copy link

What is the license of this project?

Would be great to see Month Calendar Widget in the f-droid FOSS market, have a look here:
http://f-droid.org/forums/topic/month-calendar-widget/

However, a license text is necessary. Please include it in your repo or tell us, where to find it.

Best,
Tobias Kuban

P.S.: It is also possible to include a donation button there, see:
http://f-droid.org/forums/topic/about-this-forum/

@grote
Copy link

grote commented Jan 24, 2014

Any news here?

@JoseGD
Copy link
Owner

JoseGD commented Jan 26, 2014

Hi all, sorry for neglecting this repo for so much time.

I've updated the code here to version 1.5.0 some time ago, that was the last change. I won't update it to 1.5.5 because from that version I've introduced extensions to the widget that for now are proprietary, and the code in 1.5.5 doesn't have clear boundaries between the main widget and the extensions (actually, the first and only extension to date).

The version I'm working now introduces many changes to the code base, in fact it has a new plugin architecture. Alongside the next Month Calendar Widget I'm working on the second extension, MCW Calendar Events. After releasing both apps on Google Play I will decide what to do with this repo, hoping to have a more clear picture of what is open source and what is closed source.

I hope you will understand that all these changes and the mix of open source and proprietary code made me defer the decision on the license.

@grote
Copy link

grote commented Jan 26, 2014

I'm very sorry to hear that you are going the non-free way. Could you at least put a license on the code that is out there and free it to enable people to pick it up?

@JoseGD
Copy link
Owner

JoseGD commented Jan 27, 2014

Thanks for your comprehension.

I decided to charge for the app's extensions because making the app more robust and giving the kind of support I'm giving now is taking a lot of my time. I discarded ads from the beginning, so I have to charge.

I would release all of the source code here if it were up to me, but people then will download the code, generate the APK and probably distribute it, so my sales will be like the Paypal donations I receive :(

Regarding your request, sure I can do that, but I'm a newbie in the open source world, what license do you suggest?

And about the code as it is here, if I resolve the mess I made mixing code meant to be OSS and non-OSS code, I will for sure update this repo, since many useful features are coming in the fee widget.

@grote
Copy link

grote commented Jan 27, 2014

Thanks for considering publishing your old code under a Free license!

If you want your code to be shared alike (copyleft), then choose GPLv3. if you don't want that choose Apache2 license.

You are probably right that less people will pay for your app, if they can get if for free from somewhere else. But it is also true that they can do this already. There's many black markets for apps where all are free of charge.

If you liberate your app, you might get a little less money, but the majority of people will stay pay via Google Play like they do now. If you keep your app closed and non-free, you also loose on potential contributions from people.

Some people say that non-free software is a political problem.

@JoseGD
Copy link
Owner

JoseGD commented Feb 4, 2014

Thanks, Grote.
You're right that anyway my apps will be pirated. Just wanted to minimize that.
Please be patient, right now I'm in the midst of developing the second extension to the widget, after that I will for sure make a decision regarding the license

@grote
Copy link

grote commented Mar 13, 2014

any news?

@pejakm
Copy link

pejakm commented Apr 19, 2015

@JoseGD Any news on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants