On Sun, 6 Mar 2022 at 17:57, Daniel Gruno <humbed...@apache.org> wrote: > > On 06/03/2022 18.43, sebb wrote: > > The GitHub repo has been forcibly changed to track > > > > https://svn.apache.org/repos/asf/steve/trunk > > instead of > > https://svn.apache.org/repos/asf/steve/trunk/pysteve > > > > This has invalidated all the forks, and broken all the PRs. > > > > That is very discouraging for contributors. > > > > Was it really necessary to do it that way, especially without applying > > the PRs first? > > It's an unfortunate side effect, agreed. It was not foreseen that GitHub > would blanket invalidate everything.
I don't believe that this could not have been forseen. The changes had to be force-pushed, which is a normally disallowed precisely because of the problems it causes. > Now, having said that, the PRs could not be easily applied as it's a > mirror-only repo (for now), and nobody on the project expressed any > interest in working on that code-base, Various people have made contributions, but the project has made little or no attempt to engage with them, so it's not surprising that the project has been in the doldrums for so long. > so I consider this sort of moot, > if in a sad way. > > This process is about rectifying exactly that, the interactions on > GitHub and the pull/merge request process. Going forward, we'll have > better integration with the new code-base once we switch from r/o mirror > to r/w repo. > > Sometimes you have to break some eggs. That was not the case here. > > > > Sebb >
