On 03.07.2020 15:26, Henk-Jaap Wagenaar wrote:
On Fri, 3 Jul 2020 at 13:10, Ivan Pozdeev <vano@mail.mipt.ru> wrote:

So what?


They'll have to synchronise their history to ours to be able to make a PR. And if they don't, it doesn't matter for us what they do with the data anyway since they are responsible for maintaining it and keeping it relevant if they need to, not us

That is not a very collaborative mindset.

I fail to see how. We provide all the tools to collaborate. If a person has a divergent history, they will see that when trying to collaborate (submit a PR or otherwise interact with our repo from theirs in any way) and will be able to fix that problem then and there.

Can somebody give an example of when we force-pushed before? Surely there should be a PEP outlining when we force push and how we communicate this to our "consumers" before/when we do so?

Plus, since it's the PEPs repo, it's tightly bould to the Python project -- the usefulness of a fork disconnected from it is pretty low.

It partially serves as documentation for the Python project, so mirroring it and its documentation (in git form or in its presented form) can definitely have a use, for example, if you are an environment that has no internet access (common in secret government work, and I am sure their IT team will be even less pleased that they have to do something by hand and overwrite history!).