On 2/6/20 7:23 AM, 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? This is an area of GitLab I've not explored completely yet, but that I'll get acquainted with pretty soon, since Heptapod itself will need to provide packages at some point. >> 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. While it does get closer, I think it's realistic to support wikis in Heptapod before that deadline. > > I am personally done with bitbucket/atlassian. Hosting the downloads > should be simple, if we had the bandwidth we could do it on the > buildbot master. Perhaps we could ask the PSF if we can upload them to > www.pypy.org/downloads/files. Seen from my outsider perspective, it would look great to have the downloads hosted at PSF. > Hosting the wiki is a bit more complicated. Perhaps since we never get > outside edits anyway we could just incorporate it into the pypy.org > website as static pages. You could also import it as a separate repository right now, and then make it a proper wiki once Heptapod supports them. After all, it's backed by a standard Mercurial repository.
But I'd suggest to keep it on Bitbucket for a while and make a decision around April, based on where Heptapod stands at that time. Regards, -- Georges Racinet https://octobus.net, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics
signature.asc
Description: OpenPGP digital signature
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
