-
-
Notifications
You must be signed in to change notification settings - Fork 31k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python license documentation file has a stale link to Zope Corporation #126022
Comments
I verified redirection and destination. @serhiy-storchaka commented on the PR "This is a legal document. It cannot be changed without consulting lawyers. Please open an issue for further discussion." @ambv How continue? |
For context, the dead link www.zope.com for the Zope Corporation was discussed in bpo-25910/gh-70098. It was proposed to change it to www.zope.org, but it was a link for the Zope Foundation, which is a different entity. Alternative proposition was to remove the link. In result, it was left unchanged. The license file was also excluded in several other rounds of link updates. Then it was changed to www.zope.org in #16880. I wonder if it was a correct change. cc @orsenthil, @gvanrossum, @jimfulton, @aeros, @terryjreedy |
I'd recommend to link to the wayback machine, e.g. http://web.archive.org/web/20130102003549/http://www.zope.com/ (that's the last year it was functioning IIUC -- the last snapshot from 2023 already looks very different, more sales-oriented. Should this also be changed in other copies of the license? |
Thanks Guido,
I'm not sure what would be best. Zope Corp is long gone.
The Plone Foundation took over the Zope IP.
I'm CCing Martijn Peters, who may have a suggestion. 😁
Jim
…On Sun, Oct 27, 2024 at 9:51 AM Guido van Rossum ***@***.***> wrote:
I'd recommend to link to the wayback machine, e.g.
http://web.archive.org/web/20130102003549/http://www.zope.com/ (that's
the last year it was functioning IIUC -- the last snapshot from 2023
already looks very different, more sales-oriented.
Should this also be changed in other copies of the license?
—
Reply to this email directly, view it on GitHub
<#126022 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF4U56JR4TWVGDOTO2SPQDZ5UDV3AVCNFSM6AAAAABQVJ4CR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBQGA3TINBXHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Strictly speaking, this is not in in the license text, but in a historical reference. This is why we have some freedom of changing it. I have not found mention of the Zope Corporation on https://zope.dev/, so this is a wrong link. BTW, the link https://foundation.zope.dev/ in Wikipedia is not working. The only other references to zope.com are in email addresses of some authors:
|
This comment was marked as outdated.
This comment was marked as outdated.
another option is to remove the URL link altogether. there are other obsolete sentences, e.g. "Zope Corporation is a sponsoring member of the PSF." is probably also obsolete and should be written in past tense? should the whole paragraph be updated? |
I would take Jim Fulton's guidance here. He created the Zope software system, he was at Zope.com from (close to) its beginnings as Digital Creations till (almost?) the end (2013 IIRC). But regardless, it is my position that the Doc/license.rst file is simply a marked-up copy of the LICENSE file in the project root. That file was updated to remove the zope.com link seven years ago: 8474d87. We should use the exact same words here to be faithful. If you really want to plant link on "Zope Corporation", IMO a wayback machine link (from before the sale of the company) is the best. PS. Be careful to distinguish the several different uses: Zope.com was the company; Zope is the software (actively being maintained at https://github.com/zopefoundation/Zope); Zope.org was the Zope foundation (what the PSF is for Python), now subsumed by the Plone foundation (Plone was one of the the most successful Zope applications/frameworks). The software lives under the zopefoundation org on GitHub. |
Let's wait a bit for Martijn's suggestion and apply it across the board. Otherwise, removing the stale URL seems like the best course of action. |
First of all, I am the Martin Peeters mentioned by @jimfulton there was just a typo in my name. Zope Corporation's intellectual property was transferred to the Zope Foundation, and then to the Plone Foundation. As the president of the Plone Foundation, I brought that subject to today's board meeting, and we believe that the correct URL should be zope.dev. |
I’m not sure I trust this “Martin Peeters”. The person Jim was referring to is Martijn Pieters: https://github.com/mjpieters. Jim I have met and I know he is deep into Zope. The other account is unknown to me. Cc: The Real Martijn Pieters @mjpieters |
Please trust him. I'm a dufus. 😁
Martin, again apologies!
Jim
…On Thu, Oct 31, 2024 at 5:53 PM Guido van Rossum ***@***.***> wrote:
I’m not sure I trust this “Martin Peeters”. The person Jim was referring
to is Martijn Pieters: https://github.com/mjpieters. Jim I have met and I
know he is deep into Zope. The other account is unknown to me.
—
Reply to this email directly, view it on GitHub
<#126022 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF4U5Z2LPU7LA2EL2JL4B3Z6K7FXAVCNFSM6AAAAABQVJ4CR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJRGAZTINBVGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Oops. Jim is right, Martin is the Plone foundation board president. My apologies, Martin! (And also sorry Martijn for dragging you into this.. :-) However I don’t think that a reference to Zope.com, the (former) company, can be replaced with zope.dev, which is for the software. We should take the lead from the “official” LICENSE file and remove the link. |
And if my 2c is any use here: I was indeed a Digital Creations employee and long-time Zope and Plone contributor but I've not been active in those communities and codebases for quite some time now. I'm certainly not the person to ask for licensing and URL advise here! I'd go with what @mpeeters has to say on the subject, instead. 😃 We could, for tradition's sake, also drag in the Other Martijn, Martijn Faassen, and complete the set? 🫠 |
I was not offended at all. I know my first name/last name can be confusing :) |
…honGH-128516) (cherry picked from commit 9682a88) Co-authored-by: partev <[email protected]>
…honGH-128516) (cherry picked from commit 9682a88) Co-authored-by: partev <[email protected]>
#129290) Co-authored-by: partev <[email protected]>
#129291) Co-authored-by: partev <[email protected]>
Thanks everyone, we removed the https://www.zope.org link and also made some other updates to |
…ts (pythonGH-129308) (cherry picked from commit a156b19) Co-authored-by: partev <[email protected]>
…ts (pythonGH-129308) (cherry picked from commit a156b19) Co-authored-by: partev <[email protected]>
…cts (GH-129308) (#129317) Co-authored-by: partev <[email protected]>
…cts (GH-129308) (#129318) Co-authored-by: partev <[email protected]>
Python license file https://docs.python.org/3.14/license.html refers to "Digital Creations (now Zope Corporation; see https://www.zope.org/)". However, Zope Corporations' current website is https://zope.dev and not zope.org. Currently zope.org redirects to zope.dev but at some point in the future this redirection may stop working and it is probably better to link to the new URL which is https://zope.dev
Linked PRs
The text was updated successfully, but these errors were encountered: