Page MenuHomePhabricator

Efl README file should not have licensing information Separate License file should be added.
Open, Pending on user inputPublic

Description

Hi All, I was trying to look through the readme file in EFL and that is cluttered with alot of licenses of other aspects of efl like win 32 stuff and alot of other things.

Can we split the licenses into their own file called LICENSES and leave the readme for useful information regarding for example a note that efl module is not on meson for example and the like.

If we are in agreement with this kindly assign the task to me and I will get it done and committed and submitted to code review i know its a trivial thing but i think everything should be sent through review no matter how trivial it might be.

eagles051387 triaged this task as Pending on user input priority.
raster added a subscriber: raster.Aug 1 2018, 11:47 AM

ummm i am not so sure it's a good idea. licenses are an often asked question. often enough and important enough to put in the README imho... :)