On Thu, 2020-02-06 at 08:23 +0200, Matti Picus wrote: > > > - what to do about downloads? It is not clear that the gitlab instance > > > has a place for artifacts. Assume we find a solution, how far back do we > > > want to keep versions? > > Would it be possible to just keep this on bitbucket and point to it? > > I understand the idea of stopping all mercurial services, but a priori > > they won't delete everything else too? If they do, maybe we just need > > a hack like convert the pypy repo to git on bitbucket (and then never > > use it). Same for the wiki. And for all our many-years-old dead > > repos---we can convert them in-place to git if that means they can > > stay there. > > > > Of course all this is assuming we're fine with keeping a few > > historical things on bitbucket. If you decide you'd prefer to have > > nothing more to do with bitbucket soon and they should die instead of > > continuing to get however little publicity we'd continue to give them > > by doing that, then I would understand too. > > In order to stay on bitbucket, we would have to > > - reame pypy/pypy to pypy/pypy_hg > > - create a new pypy/pypy using a git repo > > - transfer the downloads and wiki to the new repo > > As May 31 gets closer, we will have to decide what is easier: these > steps or something else. >
Disclaimer: I don't think I've ever contributed a patch, so don't take my opinion as something important. From an outsider's perspective, I think this is a better choice (or even moving to GitHub). I find Mercurial-based workflows cumbersome, to say lightly. If I have a simple fix, I don't want to spend my time trying to figure out how to use Mercurial, which extensions are required to submit contributions sanely and how to make it all work with some site that seems to try to take advantage of bitbucket removing Mercurial support and that I won't probably use for any other project. Many Gentoo developers have always had mixed feelings about using GitHub. However, even partial GitHub support has drastically increased number of contributions. I agree that PyPy's not the same kind of project -- I suppose there's a different proportional between dedicated long-term contributors and drive-by contributions. Nevertheless, you may really want to consider if using a more common tooling/platform won't result in less people resigning from contributing because it seems too hard. Finally, we're living in times where people start caring about their personal data. Even if it's not explicitly personal, people have their doubts about registering on yet another site that's likely going to track them in ways unimaginable. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
