**Software Archaeologist** @dashie@oldbytes.space · Jun 02, 2018, 08:21

**Software Archaeologist** @dashie@oldbytes.space · Jun 02, 2018, 08:21

Software Archaeologist @dashie@oldbytes.space

> make a forge
> close the forge
> want to buy github

:blobhyperthink:

**rysiek ✅** @rysiek@mastodon.social · Jun 02, 2018, 08:21

**rysiek ✅** @rysiek@mastodon.social · Jun 02, 2018, 08:21

@dashie MS wants to buy GitHub?

Oh boy.

**Software Archaeologist** @dashie@oldbytes.space · Jun 02, 2018, 08:21

**Software Archaeologist** @dashie@oldbytes.space · Jun 02, 2018, 08:21

@rysiek rumors for now, but lol yeah

**rysiek ✅** @rysiek@mastodon.social · Jun 02, 2018, 08:39

**rysiek ✅** @rysiek@mastodon.social · Jun 02, 2018, 08:39

@dashie

FLOSS community:
> hey let's put all our eggs in this one GitHub basket
> what could possibly go wrong
> GitHub is so convenient

Microsoft:

**Bernie** @codewiz@mstdn.io · Jun 02, 2018, 10:09

**Bernie** @codewiz@mstdn.io · Jun 02, 2018, 10:09

@rysiek @dashie Well, we also seem to be putting several eggs in the GitLab basket, and larger projects host their own GitLab instance.

**rysiek ✅** @rysiek@mastodon.social · Jun 02, 2018, 10:33

**rysiek ✅** @rysiek@mastodon.social · Jun 02, 2018, 10:33

@codewiz @dashie comparing a solution you can self-host with a fully centralized solution is, I feel, disingenuous.

Of course we should have *more* implementations (and we do, actually), but these are problems on two different levels.

I'd like to see federated issues/pull requests between git-hosting instances thouhg.

**Wolf480pl** @Wolf480pl · 2018-06-02T17:01:05Z

Wolf480pl @Wolf480pl

@rysiek @codewiz @dashie IMO for short-term solutions it'd be cool to evaluate which of the following can be implemented on top of git or APub:
- issues
- wikis
- comments/reviews
- any other important feature of github I missed?

Jun 02, 2018, 17:01 · 0 · 1

**Wolf480pl** @Wolf480pl · Jun 02, 2018, 17:11

**Wolf480pl** @Wolf480pl · Jun 02, 2018, 17:11

@rysiek @codewiz @dashie
IMO wikis could easily be either a separate branch or a subdir in the git repo, only needs a CI to render it.
(btw. CI doesn't need federation at all)

issues... I have a feeling the solution will become apparent once we have figured out how to do comments/reviews.

**Wolf480pl** @Wolf480pl · Jun 02, 2018, 17:11

**Wolf480pl** @Wolf480pl · Jun 02, 2018, 17:11

@rysiek @codewiz @dashie

So, comments. On file lines, on diff lines, or on pull requests.
How do we implement them?
And is a pull request basically sending "hey can you pull ac7f... from git.example.com/..." over your favourite communication method, or do we need something more formal?

**Bernie** @codewiz@mstdn.io · Jun 02, 2018, 17:18

**Bernie** @codewiz@mstdn.io · Jun 02, 2018, 17:18

@Wolf480pl @rysiek @dashie Something like that, in a machine-readable form.

Do we need to worry about security? My guess is no: if email is secure enough for Linux kernel development, ActivityPub messages will also do.

And then again, git also has PGP signatures.