License of code posted to the Fortran Discourse

Yes, we were discussing just code initially, but I think the same applies to the content. Text content is just less likely to be reused than code, but we should have a way to catch that exception. :smile: This pertains to the forum itself: Imagine a user copy/pasting other user’s explanation in their blog/article/book, without asking for permission or giving credit. We want to prevent that from happening, and we don’t want to alienate a user that was taken advantage of.

Good point on modifying a license, I agree, let’s not do that.

I vote for MIT for code and CC-BY for content as defaults. User can explicitly override the defaults on a post-by-post basis.

3 Likes

I vote for MIT for code and CC-BY for content as defaults. User can explicitly override the defaults on a post-by-post basis.

:+1: I also vote for this for the same reasons @milancurcic mentioned.

1 Like

I am also in favour of this approach.

2 Likes

+1
This discussion has clarified a lot of things.

3 Likes

I vote for MIT for code and CC-BY for content as defaults. User can explicitly override the defaults on a post-by-post basis.

:+1: I agree

I agree as well. :+1:

Considering the significant support for MIT + CC-BY and no objections in last two weeks, I went ahead and updated the welcome post.

4 Likes

Thanks @milancurcic. I agree.

“Welcome to the Discourse” says:

By default, the code that you own and post on the Fortran Discourse is licensed under the MIT License , whereas other (non-code) content that you own is licensed under the CC-BY license . You own the copyright to your content.

But Terms of Service says:

Content you submit to the forum belongs to you, and you decide what permission to give others for it. But at a minimum, you license the company to provide content that you submit to the forum to other users of the forum. That special license allows the company to copy, publish, and analyze content you submit to the forum.

Is it normal?

Yes. The former are our community terms that we chose. The latter are the generic terms that come with Discourse. I don’t think they’re in conflict. What do you think?

Hi Milan,
I needed the information about the code license. I remembered vaguely about MIT license but was not sure. So I first searched in the ToS and I was quite disappointed by the vague information. It’s true that it does not contradict the “Welcome to the Discourse” which also says:

If you want attribution or require that the content is licensed differently, state so explicitly in the same post, for example by including a Copyright statement in the code snippet, by posting a link to the license, or similar.

But it did not give me the precise needed information. Perhaps it could be also confusing for newcomers?

Okay, but what specifically is the information that you’re missing? Specific license text or something else?

I needed to be sure the default license for the code posted in the Discourse was the MIT license. My first reaction was to look in the ToS (and FAQ). I did not found there a precise information. So I used the search tool at the top of the page to look for “MIT license” and found the answer in the “Welcome to the Discourse” post.

Happily, if we search “license of code” we will find the same posts. No need to vaguely remember it was MIT.

Of course someone, having creating an account three days ago will remember having read the info on the “Welcome” page. But three months latter, when he needs it, he could have some difficulty to find it.

Note also that I don’t know how to find the “Welcome to the Discourse” page from the top right menu… And I just feel that the user should not have to use the search tool to find such an important information.

I just pinned the “Welcome to Discourse” topic. It should appear at the top of the topics page. Let me know if there are objections.

1 Like