News for hackers. Stuff that matters.
Re:Cloudflare CTO: “If we did [take on GitHub] what features... by rakoo on Thursday May 30, 2019 @05:53PM (#20056280)
Bare git only stores code, not issues, tickets, wiki, and all the stuff that goes beyond source files. There are a myriad of open source solutions for this, but there is no standard format that allows easy migration and inter-linking.
Re:Cloudflare CTO: “If we did [take on GitHub] what features... by roblabla on Thursday May 30, 2019 @06:14PM (#20056482)
Well for wiki, usually a branch containing markdown will transfer well across forges. Issues and PRs are the real issue. I’ve been hoping git appraise would get supported by the forges for distributed PRs, but it doesn’t look like that’ll happen.

Gitlab is implementing MRs via git send-email though, which is part of an epic to federate Merge Requests: https://gitlab.com/groups/gitlab-org/-/epics/260 .

Re:Cloudflare CTO: “If we did [take on GitHub] what features... by rakoo on Thursday May 30, 2019 @08:00PM (#20057112)
Very interesting that gitlab is standardizing on the de facto standard of patch requests! How ironic it is that the existing git-request-pull isn't used more than needed thouh
Re:Cloudflare CTO: “If we did [take on GitHub] what features... by tracker1 on Thursday May 30, 2019 @08:15PM (#20057189)
would be easy enough for a branch of "issues" containing a number, index.json and ####.md where the number is the initial issue and comments, with some front-matter to associate user details.
Re:Cloudflare CTO: “If we did [take on GitHub] what features... by tracker1 on Friday May 31, 2019 @04:14PM (#20064533)
To be clear, there would be directories, each directory being the next incremental number representing the issue number, and the directory containing numbered markdown documents with yml front matter starting at 0 being the root of the issue thread.

I'm kind of surprised it isn't already like this, or similar.