Releasing app under MIT license

Hey guys,

I was in the act of publishing my chat app to the app store, while a nice error message popped up:

info.xml did not validate: Element ‘licence’: [facet ‘enumeration’] The value ‘mit’ is not an element of the set {‘agpl’}., line 18

Why is it not allowed to use a more permissive license? I would like to avoid one more release just because of this license stuff.

cc @jospoortvliet @LukasReschke

PS: I am not allowed to post a github link? Why?

@sualko No idea about the github link issue :smiley:

As for the MIT license: in the beginning we had a bunch of licenses that you could select. AGPL was required but you could add more licenses like MIT, Apache 2 and MPL. The issue that popped up was that at some point we were not sure which licenses were compatible with each other and you really should license the app under the AGPL so we got rid of the additional licenses. After thinking about MIT/BSD/Apache/etc. we concluded that it really only make sense for libraries since Nextcloud requires all apps to be licensed under the AGPL anyways.

Im also unsure how multiple licenses behave in Nextcloud itself. For instace when we added multiple authors, descriptions and names we broke the apps page.

So all in all you can of course license your app under AGPL compatible licenses as well, it’s just a bit more complicated than it seems. If you are really interested in solving this for the info.xml as well feel free to open an issue on the store https://github.com/nextcloud/appstore/issues

The most important issue is probably the license compatibility. If you can come up with good references and everything is crystal clear it should not be an issue to add it to the store. The next thing we need to think about is if it breaks stuff and how we can/could work around that :wink:

@BernhardPosselt thank you for your detailed answer and I can totally comprehend the confusion around this legal stuff. I feel the same :smile:.

The most important issue is probably the license compatibility

This is exactly my problem. My app simply includes an application (which is released under MIT) and allows to set some configurations. Similar to the Documents app. My question is, how fare agpl influence this application and its dependencies (which are licensed under MIT, MPL, CC-BY 4.0).

Im also unsure how multiple licenses behave in Nextcloud itself

I am not sure what you mean, because in the info.xml multiple license tags are not allowed, as you can see in https://apps.nextcloud.com/schema/apps/info.xsd

I am not sure what you mean, because in the info.xml multiple license tags are not allowed, as you can see in https://apps.nextcloud.com/schema/apps/info.xsd

What I mean by that is: if you click on “Apps” in your Nextcloud instance and it displays the apps, would there be breakage if there were multiple license elements. As for allowing different licenses by having only one tag: you are required to at least AGPL license your code (if you distribute it ofc, for instance over the app store) so you can’t simply have one license tag with MIT in it. If you want to use a different license, you would always need to dual (or tripple, etc) license it

This is exactly my problem. My app simply includes an application (which is released under MIT) and allows to set some configurations. Similar to the Documents app. My question is, how fare agpl influence this application and its dependencies (which are licensed under MIT, MPL, CC-BY 4.0).

That should not be an issue at all if the AGPL is compatible with those licenses, see https://www.gnu.org/licenses/license-list.en.html

However you can’t use (as in: distribute) libraries/dependencies that are incompatible with the AGPL (for instance: CC-NC/CC-ND, BSD 4 clause, Apache 1.0, MPL 1.1)

Our whole issue is about dual/multi licensing.

I am sorry to hear about your experiences with the forum :sweat_smile: …what is the error you get, if you are trying to give a GitHub link over here? … I have looked into that - and have seen that you have posted an GitHub link in the past (but this was August) so it should not be a problem about spam :thinking: I have updated your trust level in the backend - please try again :muscle: …and report back!

I you experience more problems over here feel free to report back - also via pm :wink:

Greetings

Marius

@BernhardPosselt Thank you for that link, I will have a look at it.

@MariusBluem Thank you for taking the time to look into my github link issue. The message was somthing like “You are not allowed to post a link to that domain”. Test: https://github.com/jsxc/jsxc.nextcloud

The number of links is limited but you can set exceptions. It needs some intervention of an admin:

https://help.nextcloud.com/t/allow-links-to-github-com/5180?source_topic_id=6630

It works now :muscle:

1 Like