Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] Fwd: [cross-project-issues-dev] Remember to update your file, to use consistent licensing text


Please ensure that this is done for your projects (especially those that are participating in the Helios train). See also for details.



---------- Forwarded message ----------
From: David M Williams <david_williams@xxxxxxxxxx>
Date: Wed, Apr 7, 2010 at 2:03 PM
Subject: [cross-project-issues-dev] Remember to update your file, to use consistent licensing text
To: cross-project-issues-dev@xxxxxxxxxxx

As I'm sure you are all aware, a new Helios Requirement this year is to use consistent license text, so the "license acceptance" dialog can be made more meaningful and easier to use.

And, that's _exactly_ consistent license text ... same year, same text, same capitalization. (I've heard consecutive white space doesn't matter, but why push it?).

So, yes, this does means almost all of us have to change.

See bug 306627 for some details on this topic, and the exact text to use.

Of course, this applies to those features that use the Eclipse SUA and if someone was shipping a feature in Helios that didn't use that, then you wouldn't want to change yours .... but, then I'd wonder why it was in Helios?

For reference, see
for details on the legally required documents ... but, this Helios requirement goes beyond the minimum requirement and gets us all to use the exact same text, so the software can tell when its really the same license.
If you try to get the "standard text" from the website, you need to be careful to get the plain HTML and ASCII versions, make sure there's no web encoding conversion errors, etc., so probably easiest to get from the bugzilla entry.

One disturbing angle that's come up, while some checked if we all use the same text, is that some of you are not using ANY (yet).  That is really a big "no no" and would be a "stop ship" issue, if found "at the last minute" (as far as I know,
it should be a stop ship issue even for milestones, etc ... but, I'm not here to judge ... yet).

So, let's try to get this all corrected for M7, so we don't have to monkey around with this routine level of detail for release candidates. Plus, if you fix yours for M7, that'll make all the slackers really standout in M7 and we can more easily see who they are :)

Much Thanks,

cross-project-issues-dev mailing list

Back to the top