Here is a 3-minute section of a PyCon 2022 keynote by the steering
council discussing migration of CPython to GitHub:

https://youtu.be/m2R5shF1pLc?t=535

In particular, they talk about how much effort went into the
migration, and just how difficult it was, and how GitHub was
directly involved with supporting their effort.  It took nearly 7
years (!) from when the plan was first created in 2015:

https://peps.python.org/pep-0512/

This Python PEP is itself pretty interesting, e.g., it outlines why
they chose GitHub or GitLab.

I hope our migration process doesn't take 7 years like Python's.  For
comparison,
as of today there are 60,730 Python issues and 34,557 sagetrac issues,
so the size
of  the relevant data sets is comparable.   So to anybody who are
working on this
herculean effort, my hat is off to you.

William


On Mon, Sep 19, 2022 at 12:51 AM Marc Mezzarobba <m...@mezzarobba.net> wrote:
>
> Matthias Koeppe wrote:
> > This is great question, thanks for the pointer to this GitLab.com URL.
> > I've updated
> >
> https://github.com/sagemath/sage/wiki/Github-vs-Gitlab-vs-trac#in-favor-of-gitlab
> > based on it.
>
> Additionally, here in France at least, many universities and research
> institutes already host their own (internal or semi-public) gitlab
> instance.
>
> --
> Marc
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/tg971e%2412pj%241%40ciao.gmane.io.



--
William (http://wstein.org)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CACLE5GB71KRBqzNnGJxopidE43Ry2cmrJe4p1sg3MNoyOFpfKQ%40mail.gmail.com.

Reply via email to