Fossil – Next Generation

Re:Fossil – Next Generation by dognotdog on Tuesday November 21, 2017 @08:54PM (#15753565)

That's the beauty of fossil... you hardly need one! Most aspects (wiki, issues) those services offer can be in the local repo, always accessible.

[ Parent | on HN ]

Re:Fossil – Next Generation by jimktrains2 on Tuesday November 21, 2017 @09:54PM (#15753846)

I use GitHub to have a publicly accessible, discoverable, and searchable presence for the repo.

Perhaps we should build something like gnu social (or diaspora, but not as bad) for code projects, or build on existing distributed social networks.

[ Parent | on HN ]

Re:Fossil – Next Generation by zaarn on Wednesday November 22, 2017 @02:27AM (#15754994)

This is somewhat in the works.

There is an issue on GitLab to enable federated pull requests and I believe Gogs/Gitea community is working on getting some sort of standard figured out if I'm not mistaken.

[ Parent | on HN ]

Re:Fossil – Next Generation by sytse on Wednesday November 22, 2017 @10:54AM (#15757717)

Issue for reference https://gitlab.com/gitlab-org/gitlab-ce/issues/4013

[ Parent | on HN ]

Re:Fossil – Next Generation by hinkley on Wednesday November 22, 2017 @02:23PM (#15759628)

Maybe a better option is to convince people like DigitalOcean to provide a prebuilt image.

But I’m not sure I agree with the conclusion here You do need the network effect if you want git gone. GitHub is just easy enough to cross reference bugs in other repositories your project depends on.

[ Parent | on HN ]