Project License?

[cpu]

👋 Hi there,

I notice the top level repository doesn't have a project license. Is it assumed to be MPLv2 like the embedded Boulder source code? https://github.com/mami-project/lurk/blob/master/serverSTAR_V3/LICENSE.txt

[dr2lopez]

Hi, It is. We did not see the need of replicating the license when started the project. Do you think adding the license file explicitly would be of help? Be goode,

…

-- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/in/dr2lopez/ e-mail: [email protected]<mailto:[email protected]> Tel: +34 913 129 041 Mobile: +34 682 051 091 ---------------------------------- On 17/01/2019, 15:26, "Daniel McCarney" <[email protected]<mailto:[email protected]>> wrote: 👋 Hi there, I notice the top level repository doesn't have a project license. Is it assumed to be MPLv2 like the embedded Boulder source code? https://github.com/mami-project/lurk/blob/master/serverSTAR_V3/LICENSE.txt — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#1>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AHnRJ9iuMhjV3uEgZtxxd8xG_4a6NKtlks5vEIgNgaJpZM4aFexL>.

________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

[cpu]

Hi @dr2lopez,

Thanks for the reply/clarification.

Do you think adding the license file explicitly would be of help?

I think there's some help in doing so. Github does some magic when there is a LICENSE.md file in the top level directory of a project. The Github docs explain fully: https://help.github.com/articles/licensing-a-repository/

There are a few benefits but notably it will let people search for the project using special license search filters and it will also add a license icon in the project summary UI. For example in the Boulder repo because of the top level license file there is a little ⚖️ icon with "MPL-2.0":