| Re: [cross-project-issues-dev] Migrate to EPL 2.0 |
Hi, starting with Waynes script I created one that did the trick for the OSBP project. You can find it here: https://bugs.eclipse.org/bugs/attachment.cgi?id=274671 as part of https://bugs.eclipse.org/bugs/show_bug.cgi?id=536407 It is very likely that it needs to be adjusted :) Mit freundlichen Grüßen / Cordialement / Best Regards ppa. / p.p. Ralf Mollik Bereichsleiter Entwicklung / Director Development OS.bee -----Ursprüngliche Nachricht----- Von: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] Im Auftrag von Ed Merks Gesendet: Montag, 25. Juni 2018 17:43 An: Cross project issues Betreff: [cross-project-issues-dev] Migrate to EPL 2.0 Hi, I wonder if anyone started seriously looking at migrating their project from EPL 1.0 to EPL 2.0? The FAQ says we should: https://www.eclipse.org/legal/epl-2.0/faq.php#h.60mjudroo8e5 Also, Wayne suggested that there will be pressure applied, e.g., perhaps a release train participation requirement. But the FAQ doesn't say much about how to do this: https://www.eclipse.org/legal/epl-2.0/faq.php#h.tci84nlsqpgw The instructions are "So, a project can use the new version by simply updating the file headers and notices." But how simple is that really? Just changing all the copyright headers in all the files sounds simple at face value. https://www.eclipse.org/legal/epl-2.0/faq.php#h.q72cnghf29k0 But I have several thousand files! Is everyone doing this or planning to do this manually, or via various forms of scripts that we each author ourselves? Of course we'll all diligently increment every bundle and feature version (by the appropriate amount) remembering to keep the POMs in sync. And we won't overlook the copyright element in each feature. Nor will we overwrite each about.html with the new one (where is the definitive version of that anyway?), accidentally replacing any Third Party Content sections. To me it seems like a lot of work, made error prone by the sheer tedium involved. Perhaps someone else already has some experience to share? Regards, Ed _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Attachment:
smime.p7s
Description: S/MIME cryptographic signature