Allow LICENSE to be named LICENSE.md #46
Conversation
Markdown is used throughout the open source community for years and it is a significantly better experience user experience, specially when they are presented in github/gitlab/etc. By offering the LICENSE in markdown, we can format links, lists, etc, which significantly reduces the barrier for someone to read and navigate in these files.
|
Related to apache/datafusion#966 |
|
I think you need to raise this with legal first. Note also that the NOTICE and LICENSE files are source files, and are released along with other source. |
|
@sebbASF , could you clarify what do you mean with being source files? I understood that these files were to be read by people, not consumed by a compiler or something. |
|
I meant that the N&L files are intended to be read alongside the other source files when included in the release bundle. The files will not always be served via an app that handles Markdown. |
I think this makes sense and matches my expectations as well. I am curious if there is any legal issue that disallows use of md extension here? I do think this would be an improvement for some of the projects for cases when the file did end up being served through interfaces that renders markdown files. For example, our README.md files also will not always be served via an app that handles markdown, but in case it does (GitHub web UI), it helps our users a lot. On the other hand, readmes are not legal disclaimers like N&L, so perhaps I am missing something here? |
|
N&L are legal files. Any changes must be agreed by ASF Legal. |
3 participants
Markdown is used throughout the open source community for years and it is a significantly better experience user experience, specially when they are presented in github/gitlab/etc.
By offering the LICENSE in markdown, we can format links, lists, etc, which significantly reduces the barrier for someone to read and navigate in these files.