LWN: Comments on "Moving Python's bugs to GitHub"

Moving Python's bugs to GitHub: postponed till March 24

douglasbagnall — Thu, 10 Mar 2022 08:45:17 +0000

This has been delayed by a war and a security release:

https://discuss.python.org/t/github-issues-migration-what...

(I'm following this because I've got a non-urgent bug that I've been but holding off reporting).

Moving Python's bugs to GitHub

oldtomas — Fri, 04 Mar 2022 06:57:26 +0000

I'm also concerned seeing more and more strategic (for free software) projects moving to Github.

I'm not even sure vendor lockin is the problem. It might be. But having seen how Github (before it was Microsoft) transformed an inherently decentral thing as Git into a centralised service without forcing anyone, and given Microsoft's track record on top of that...

I keep asking myself: what kind of shenanigans are up their sleeve to monetise the $7B they dumped into Github, and in which way are those shenanigans affecting us?

I've lived for too long. I don't trust them. A bit.

Moving Python's bugs to GitHub

johannbg — Wed, 02 Mar 2022 23:56:52 +0000

There is no vendor lock-in on Github so I'm unsure why you think that exporting something from github is an issue + since it's own by Microsoft then it wont go through some financial difficulties like for example gitlab is experiencing so the python community choosing github as it's gitforge was a wise choice.

At this point I would not be surprised if gitlab was relying on IBM/RH buying them given how RH seems to be heavily using it :)

Real accounts

mathstuf — Thu, 24 Feb 2022 22:56:29 +0000

From the LLVM thread that I perused, it seems it involved GitHub engineers being in the loop. So…not something available to us peons. Which is fair as the power to impersonate any account while posting a comment seems…like a lot to just have as an API endpoint hanging out there.

Real accounts

Empterdose — Thu, 24 Feb 2022 20:35:49 +0000

From the example migration, it looks like the migrated issues and comments are at least associated with real, individual GitHub user accounts. (Well, mostly. I've never seen a “mannequin” user before!) Thank goodness – I've previously seen issue migrations to GitHub use a single bot account to create the issues and comments, and the conversations end up being nearly unreadable, or at least very difficult to follow. When did GitHub add the ability to do this? Is it only available for big projects like this one? The migration plan mentions “ECI (Enterprise Cloud Importer)”, but the obvious documentation only mentions code, not issues.

Moving Python's bugs to GitHub

LtWorf — Thu, 24 Feb 2022 10:11:48 +0000

But now that I think of it, microsoft employs Guido, and owns github…

Moving Python's bugs to GitHub

LtWorf — Thu, 24 Feb 2022 10:11:00 +0000

The problem will be moving away from github.