PEP 639, Round 2: Improving license clarity with better package metadata

(Picking a somewhat random, but relevant, part of your post to quote)

OK. There’s a lot of history on this discussion, going back over a very extended period. And the PEP itself is very long, compared to the average PEP. I haven’t been following the discussions at all, and I frankly don’t have the time to give the PEP itself the sort of detailed reading that it clearly needs. In addition, I’m very much a “licensing skeptic” in the sense that I don’t have much patience for debates over complex details of license interactions and similar, so my point of view is probably too aggressively “keep it simple”.

I think the realistic thing for me to do at this point is to acknowledge that I can’t keep up with the discussion here, and leave it to others to discuss and decide. As a result, I’d like someone else to volunteer to be PEP delegate for this PEP. Such a volunteer needs to be “accepted by the other PyPA core reviewers, the lead PyPI maintainer and the default PEP-Delegate for package distribution metadata PEPs” according to our process, but hopefully that won’t be an issue. If we don’t get a volunteer, I’m not sure what will happen as the process isn’t clear, but I assume the PEP will need to go direct to the SC.

I’m happy to stay on as PEP sponsor, and advise on process-related issues in that capacity.

2 Likes