paul_c wrote: >On Friday 21 November 2008, Chris Radek wrote: > > >>The fact remains that the licenses say what they say, and those are >>the rules we will live by. >> >> >Yet you can't/won't say which licenses apply to what code or even what >licenses are involved. > > Each file or directory should have a license statement in it. This will take the form of a single line pointing out the license name, or several paragraphs of license text (usually with a pointer to more information to be found on the web), or possibly something else. If you're aware of any source files that don't have license statements (either in the file itself or in the directory in which it resides), please bring them to our attention.
Note: Statements like "there are licensing issues" or "licensing in EMC2 is all FUBAR'ed" are not effective descriptions of a problem. There is no intent on the part of the developers (that I know of anyway) to obscure the license status of any part of EMC2, so all it should take is a more detailed report of any problems to get them fixed. This is the same as bug reporting, the more specific you are, the faster the bug is likely to be found. - Steve ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
