Re: Python-2.0.1 and CNRI-Python-GPL-Compatible
Max Mehl <[email protected]> Fri, 20 Mar 2026 16:18:29 +0000
| Newsgroups | gmane.comp.licenses.open-source.general |
|---|---|
| Message-ID | <AS8PR06MB75275BA7016ED71CBB0FB75EFB4CA@AS8PR06MB7527.eurprd06.prod.outlook.com> |
--===============3640343423511397041== Content-Language: en-GB Content-Type: multipart/alternative; boundary="_000_AS8PR06MB75275BA7016ED71CBB0FB75EFB4CAAS8PR06MB7527eurp_" Content-Transfer-Encoding: 7bit --_000_AS8PR06MB75275BA7016ED71CBB0FB75EFB4CAAS8PR06MB7527eurp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi all, Thanks for the additional comments. I=92ve met Deb (ED of PSF) in Berlin th= is week and she was fine with me submitting both licenses, provided I Cc he= r in the submission emails. Consequently, I=92ve opened two separate threads on license-review@. Best, Max From: License-discuss <[email protected]> on beh= alf of McCoy Smith <[email protected]> Date: Tuesday, 17. March 2026 at 15:34 To: [email protected] <[email protected].= org> Subject: Re: [License-discuss] Python-2.0.1 and CNRI-Python-GPL-Compatible Max: If you think the newer version of the Python license ought to be approved b= y the OSI, someone needs to submit it through the license approval process,= described here: https://opensource.org/licenses/review-process Given that it sounds like 2.0.1 is now being used by Python, and 2.0 is onl= y a legacy of older versions, I'd suggest that if submitted, at the same ti= me 2.0 be "Voluntarily Retired" as have many other licenses that have been = superceded by newer versions (see the list here: https://opensource.org/lic= enses?categories=3Dsuperseded%2Cvoluntarily-retired); if it is not, 2.0 wil= l likely be tagged (if 2.0.1 is approved) as superseded, like these license= s: https://opensource.org/licenses?categories=3Dsuperseded Same comment for= the newer CNRI license versus the old one. I would suggest that someone from the Python community (if you aren't one a= lready) do the submission, if that result is indeed desired. The review pro= cess requirements are in the link above. *This is no commentary on the approvability of the 2.0.1. or new CNRI licen= se, which I haven't read, but just a general comment on how the result you = want might be accomplished. McCoy Smith On 3/16/2026 5:46 PM, Pamela Chestek wrote: I don't see a reason. The OSI generally only reacts to requests for license= approval, it doesn't generally approve licenses without them being submitt= ed. I'm assuming it hasn't be approved just because no one has asked for it= before. Pam Pamela S. Chestek Chestek Legal 4641 Post St. Unit 4316 El Dorado Hills, CA 95762 +1 919-800-8033 [email protected]<mailto:[email protected]> www.chesteklegal.com<http://www.chesteklegal.com/> On 3/6/2026 5:47 AM, Max Mehl wrote: Hi everyone, As requested by Nick, I would like point to an ongoing discussion on Python= licenses, affecting both OSI's and SPDX=92s realms, and request OSI=92s ap= proval of two licenses. As you know, the licensing history of Python is quite complex, and the curr= ent license consists of multiple other licenses representing the long histo= ry and the different =93ownerships=94 of the project (CWI, CNRI, BeOpen, PS= F). spdx/license-list-XML#2197<https://github.com/spdx/license-list-XML/iss= ues/2197> and an email to spdx-legal@<https://lists.spdx.org/g/Spdx-legal/t= opic/107252308> describe a bunch of intertwined problems around the identif= iers of components of Python licenses. Recently, OSI fixed some of those al= ready, thanks! Now, I wonder about the status of the license SPDX describes as Python-2.0.= 1<https://spdx.org/licenses/Python-2.0.1.html>. IIRC, the main difference b= etween Python-2.0<https://spdx.org/licenses/Python-2.0.html> and Python-2.0= .1 is in the CNRI part, making it GPL compatible (the =93Virginia clause=94= ). SPDX lists this updated sub-part as CNRI-Python-GPL-Compatible<https://s= pdx.org/licenses/CNRI-Python-GPL-Compatible.html>, a successor of CNRI-Pyth= on<https://spdx.org/licenses/CNRI-Python.html>. Since Python 1.6.1 and 2.0.1, Python releases have been licensed under Pyth= on-2.0.1 (and recently additionally 0BSD for its documentation), while Pyth= on-2.0 has only been used for Python 1.6 and 2.0. So modern CPython release= s would probably be best described as being licensed under "Python-2.0.1 AN= D 0BSD". But OSI only approved Python-2.0 as an Open Source license, as well as the = old CNRI-Python part. This is why I suggest OSI to approve Python-2.0.1 and= CNRI-Python-GPL-Compatible as Open Source licenses, and mark Python-2.0 an= d CNRI-Python as superseded. Is there any reason not to? Best, Max -- Max Mehl Open Source / Supply Chain Enterprise-Team Chief Technology Office (CTO) DB Systel GmbH / Deutsche Bahn Schedule a meeting: cal.com/mxmehl<https://cal.com/mxmehl> ________________________________ Pflichtangaben anzeigen<https://www.deutschebahn.com/pflichtangaben/2026030= 5> N=E4here Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier:= https://www.deutschebahn.com/de/konzern/datenschutz _______________________________________________ The opinions expressed in this email are those of the sender and not necess= arily those of the Open Source Initiative. Official statements by the Open = Source Initiative will be sent from an opensource.org email address. License-discuss mailing list [email protected]<mailto:[email protected]= e.org> http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensour= ce.org _______________________________________________ The opinions expressed in this email are those of the sender and not necess= arily those of the Open Source Initiative. Official statements by the Open = Source Initiative will be sent from an opensource.org email address. License-discuss mailing list [email protected]<mailto:[email protected]= e.org> http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensour= ce.org ________________________________ Pflichtangaben anzeigen<https://www.deutschebahn.com/pflichtangaben/2026031= 9> N=E4here Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier:= https://www.deutschebahn.com/de/konzern/datenschutz --_000_AS8PR06MB75275BA7016ED71CBB0FB75EFB4CAAS8PR06MB7527eurp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> </head> <body> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Hi all,</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Thanks for the additional comments. I=92ve met Deb (ED of PSF) in Berlin th= is week and she was fine with me submitting both licenses, provided I Cc he= r in the submission emails.</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Consequently, I=92ve opened two separate threads on license-review@.</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Best,</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Max </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div id=3D"mail-editor-reference-message-container" style=3D"color: inherit= ; background-color: inherit;"> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr;"> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"te= xt-align: left; padding: 3pt 0in 0in; border-width: 1pt medium medium; bord= er-style: solid none none; border-color: rgb(181, 196, 223) currentcolor cu= rrentcolor; font-family: Aptos; font-size: 12pt; color: black;"> <b>From: </b>License-discuss <[email protected]= rg> on behalf of McCoy Smith <[email protected]><br> <b>Date: </b>Tuesday, 17. March 2026 at 15:34<br> <b>To: </b>[email protected] <[email protected]= pensource.org><br> <b>Subject: </b>Re: [License-discuss] Python-2.0.1 and CNRI-Python-GPL-Comp= atible<br> <br> </div> <p class=3D"ms-outlook-mobile-reference-message skipProofing">Max:</p> <p class=3D"ms-outlook-mobile-reference-message skipProofing">If you think = the newer version of the Python license ought to be approved by the OSI, so= meone needs to submit it through the license approval process, described he= re: <a href=3D"https://opensource.org/licenses/review-process" class=3D"moz-txt= -link-freetext" originalsrc=3D"https://opensource.org/licenses/review-proce= ss" data-outlook-id=3D"fd6a6813-a28d-48a4-8e0b-7de4c8297231" style=3D"margi= n-top: 0px; margin-bottom: 0px;"> https://opensource.org/licenses/review-process</a></p> <p class=3D"ms-outlook-mobile-reference-message skipProofing">Given that it= sounds like 2.0.1 is now being used by Python, and 2.0 is only a legacy of= older versions, I'd suggest that if submitted, at the same time 2.0 be &qu= ot;Voluntarily Retired" as have many other licenses that have been superceded by newer versions (see the list here: <= a href=3D"https://opensource.org/licenses?categories=3Dsuperseded%2Cvolunta= rily-retired" class=3D"moz-txt-link-freetext" originalsrc=3D"https://openso= urce.org/licenses?categories=3Dsuperseded%2Cvoluntarily-retired" data-outlo= ok-id=3D"bbc957bc-2e98-418a-bcd0-3a50dba639ed" style=3D"margin-top: 0px; ma= rgin-bottom: 0px;"> https://opensource.org/licenses?categories=3Dsuperseded%2Cvoluntarily-retir= ed</a>); if it is not, 2.0 will likely be tagged (if 2.0.1 is approved) as = superseded, like these licenses: <a href=3D"https://opensource.org/licenses?categories=3Dsuperseded" class= =3D"moz-txt-link-freetext" originalsrc=3D"https://opensource.org/licenses?c= ategories=3Dsuperseded" data-outlook-id=3D"8fae0716-8fa9-48df-a701-c09e0a3f= ea51" style=3D"margin-top: 0px; margin-bottom: 0px;"> https://opensource.org/licenses?categories=3Dsuperseded</a> Same comme= nt for the newer CNRI license versus the old one.</p> <p class=3D"ms-outlook-mobile-reference-message skipProofing">I would sugge= st that someone from the Python community (if you aren't one already) do th= e submission, if that result is indeed desired. The review process requirem= ents are in the link above.</p> <p class=3D"ms-outlook-mobile-reference-message skipProofing">*This is no c= ommentary on the approvability of the 2.0.1. or new CNRI license, which I h= aven't read, but just a general comment on how the result you want might be= accomplished.</p> <p class=3D"ms-outlook-mobile-reference-message skipProofing">McCoy Smith</= p> <div class=3D"moz-cite-prefix">On 3/16/2026 5:46 PM, Pamela Chestek wrote:<= /div> <blockquote> <p class=3D"ms-outlook-mobile-reference-message skipProofing">I don't see a= reason. The OSI generally only reacts to requests for license approval, it= doesn't generally approve licenses without them being submitted. I'm assum= ing it hasn't be approved just because no one has asked for it before.</p> <p class=3D"ms-outlook-mobile-reference-message skipProofing">Pam</p> <div class=3D"moz-signature">Pamela S. Chestek<br> Chestek Legal<br> 4641 Post St.<br> Unit 4316<br> El Dorado Hills, CA 95762<br> +1 919-800-8033<br> <a href=3D"mailto:[email protected]" class=3D"moz-txt-link-abbreviate= d moz-txt-link-freetext" data-outlook-id=3D"2dd6090b-d946-4d92-a020-cb387b9= 77537">[email protected]</a><br> <a href=3D"http://www.chesteklegal.com/" class=3D"moz-txt-link-abbreviated"= originalsrc=3D"http://www.chesteklegal.com/" data-outlook-id=3D"8e84faa6-9= 086-4c01-9821-d52eedaf6b64">www.chesteklegal.com</a><br> <br> <br> </div> <div class=3D"moz-cite-prefix">On 3/6/2026 5:47 AM, Max Mehl wrote:</div> <blockquote> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> Hi everyone,</div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> As requested by Nick, I would like point to an ongoing discussion on Python= licenses, affecting both OSI's and SPDX=92s realms, and request OSI=92s ap= proval of two licenses.</div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> As you know, the licensing history of Python is quite complex, and the curr= ent license consists of multiple other licenses representing the long histo= ry and the different =93ownerships=94 of the project (CWI, CNRI, BeOpen, PS= F). <a href=3D"https://github.com/spdx/license-list-XML/issues/2197" originalsr= c=3D"https://github.com/spdx/license-list-XML/issues/2197" data-outlook-id= =3D"c8d254e9-cda2-4b06-8db7-bce26d43e3bc"> spdx/license-list-XML#2197</a> and an <a href=3D"https://lists.spdx.or= g/g/Spdx-legal/topic/107252308" originalsrc=3D"https://lists.spdx.org/g/Spd= x-legal/topic/107252308" data-outlook-id=3D"fe102278-b8de-497c-ada5-f66db75= 2c1b7"> email to spdx-legal@</a> describe a bunch of intertwined problems arou= nd the identifiers of components of Python licenses. Recently, OSI fixed so= me of those already, thanks!</div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> Now, I wonder about the status of the license SPDX describes as <a href=3D"= https://spdx.org/licenses/Python-2.0.1.html" originalsrc=3D"https://spdx.or= g/licenses/Python-2.0.1.html" data-outlook-id=3D"8715974d-cf48-4f8a-804a-70= c055157f8c"> Python-2.0.1</a>. IIRC, the main difference between <a href=3D"https://spdx= .org/licenses/Python-2.0.html" originalsrc=3D"https://spdx.org/licenses/Pyt= hon-2.0.html" data-outlook-id=3D"91fa97a6-11f5-41c0-87e0-e557e08fc45c"> Python-2.0</a> and Python-2.0.1 is in the CNRI part, making it GPL com= patible (the =93Virginia clause=94). SPDX lists this updated sub-part as <a href=3D"https://spdx.org/licenses/CNRI-Python-GPL-Compatible.html" origi= nalsrc=3D"https://spdx.org/licenses/CNRI-Python-GPL-Compatible.html" data-o= utlook-id=3D"3567c9f9-2b49-47b0-81ea-244c5030e6b1"> CNRI-Python-GPL-Compatible</a>, a successor of <a href=3D"https://spdx.org/= licenses/CNRI-Python.html" originalsrc=3D"https://spdx.org/licenses/CNRI-Py= thon.html" data-outlook-id=3D"4e10b719-943a-4ba5-9168-f442c0eccf57"> CNRI-Python</a>.</div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> Since Python 1.6.1 and 2.0.1, Python releases have been licensed under Pyth= on-2.0.1 (and recently additionally 0BSD for its documentation), while Pyth= on-2.0 has only been used for Python 1.6 and 2.0. So modern CPython release= s would probably be best described as being licensed under "Python-2.0.1 AND 0BSD". </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> But OSI only approved Python-2.0 as an Open Source license, as well as the = old CNRI-Python part. This is why I suggest OSI to approve <b>Python-2.0.1</b> and <b>CNRI-Python-GPL-Compatible</b> as Open= Source licenses, and mark Python-2.0 and CNRI-Python as superseded. Is the= re any reason not to?</div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> Best,</div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> Max </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: = 12pt; color: rgb(0, 0, 0);"> <br> </div> <div id=3D"ms-outlook-mobile-signature" style=3D"color: inherit; background= -color: inherit;"> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;">-- </span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;"><b>Max Mehl</b></span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;">Open Source / Supply Chain</span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;">Enterprise-Team Chief Technology Office (CTO)= </span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;">DB Systel GmbH / Deutsche Bahn</span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;"><br> </span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;">Schedule a meeting: <a href=3D"https://cal.co= m/mxmehl" originalsrc=3D"https://cal.com/mxmehl" data-outlook-id=3D"4bf758b= e-12c8-40e6-b18a-99718d15ab49" style=3D"margin-top: 0px; margin-bottom: 0px= ;"> cal.com/mxmehl</a></span></p> <p class=3D"MsoNormal" style=3D"margin: 0cm; font-family: Aptos, sans-serif= ; font-size: 11pt;"> <span style=3D"color: black;"><br> </span></p> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr;"> <br> </div> <hr> <div class=3D"ms-outlook-mobile-reference-message skipProofing"><br> <a href=3D"https://www.deutschebahn.com/pflichtangaben/20260305" data-outlo= ok-id=3D"ccfb1650-24ce-4059-9282-5828ef1c244d">Pflichtangaben anzeigen</a><= br> <br> N=E4here Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier:= <a href=3D"https://www.deutschebahn.com/de/konzern/datenschutz" class=3D"m= oz-txt-link-freetext" data-outlook-id=3D"9417115d-f3d4-4424-b942-49c50e4736= c4"> https://www.deutschebahn.com/de/konzern/datenschutz</a></div> <pre><div class=3D"moz-quote-pre">_________________________________________= ______=0A= The opinions expressed in this email are those of the sender and not necess= arily those of the Open Source Initiative. Official statements by the Open = Source Initiative will be sent from an opensource.org email address.=0A= =0A= License-discuss mailing list=0A= <a href=3D"mailto:[email protected]" class=3D"moz-txt-li= nk-abbreviated moz-txt-link-freetext" data-outlook-id=3D"5796e451-d9c8-4304= -b026-2fa8ddb8cfd1">[email protected]</a>=0A= <a href=3D"http://lists.opensource.org/mailman/listinfo/license-discuss_lis= ts.opensource.org" class=3D"moz-txt-link-freetext" originalsrc=3D"http://li= sts.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" d= ata-outlook-id=3D"aea3c48b-6ff7-4167-ab28-f1ebae710dfc">http://lists.openso= urce.org/mailman/listinfo/license-discuss_lists.opensource.org</a>=0A= </div></pre> </blockquote> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"di= rection: ltr;"> <br> </div> <pre><div class=3D"moz-quote-pre">_________________________________________= ______=0A= The opinions expressed in this email are those of the sender and not necess= arily those of the Open Source Initiative. Official statements by the Open = Source Initiative will be sent from an opensource.org email address.=0A= =0A= License-discuss mailing list=0A= <a href=3D"mailto:[email protected]" class=3D"moz-txt-li= nk-abbreviated" data-outlook-id=3D"089cd246-fd46-4668-a773-5813b710c7cb">Li= [email protected]</a>=0A= <a href=3D"http://lists.opensource.org/mailman/listinfo/license-discuss_lis= ts.opensource.org" class=3D"moz-txt-link-freetext" originalsrc=3D"http://li= sts.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" d= ata-outlook-id=3D"ac2e82ce-02df-42ad-a7a3-b9938ddf23d8">http://lists.openso= urce.org/mailman/listinfo/license-discuss_lists.opensource.org</a>=0A= </div></pre> </blockquote> </div> <br> <hr> <br> <a href=3D"https://www.deutschebahn.com/pflichtangaben/20260319">Pflichtang= aben anzeigen</a><br> <br> N=E4here Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier:= <a href=3D"https://www.deutschebahn.com/de/konzern/datenschutz"> https://www.deutschebahn.com/de/konzern/datenschutz</a> </body> </html> --_000_AS8PR06MB75275BA7016ED71CBB0FB75EFB4CAAS8PR06MB7527eurp_-- --===============3640343423511397041== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVGhlIG9waW5p b25zIGV4cHJlc3NlZCBpbiB0aGlzIGVtYWlsIGFyZSB0aG9zZSBvZiB0aGUgc2VuZGVyIGFuZCBu b3QgbmVjZXNzYXJpbHkgdGhvc2Ugb2YgdGhlIE9wZW4gU291cmNlIEluaXRpYXRpdmUuIE9mZmlj aWFsIHN0YXRlbWVudHMgYnkgdGhlIE9wZW4gU291cmNlIEluaXRpYXRpdmUgd2lsbCBiZSBzZW50 IGZyb20gYW4gb3BlbnNvdXJjZS5vcmcgZW1haWwgYWRkcmVzcy4KCkxpY2Vuc2UtZGlzY3VzcyBt YWlsaW5nIGxpc3QKTGljZW5zZS1kaXNjdXNzQGxpc3RzLm9wZW5zb3VyY2Uub3JnCmh0dHA6Ly9s aXN0cy5vcGVuc291cmNlLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2xpY2Vuc2UtZGlzY3Vzc19saXN0 cy5vcGVuc291cmNlLm9yZwo= --===============3640343423511397041==--