News for hackers. Stuff that matters.
Re:Gitea – Alternative to GitLab and GitHub by simias on Wednesday June 06, 2018 @06:12AM (#17245772)
The more I think about it the more I think Fossil[1] has the right approach by bundling bug tracking and wiki within the VCS. If git did the same thing (and the tools were usable) then nobody would worry about github "going bad" or anything like that. Changing your host would be as simple as changing your 'origin', anybody could replicate all the information easily. When I first heard about Fossil it sounded a bit like feature bloat but I think that was a bit of a kneejerk reaction.

In retrospect I think it makes complete sense to tie code, documentation and issues. They evolve together, maybe they ought to be versioned together.

[1] https://www.fossil-scm.org/

Re:Gitea – Alternative to GitLab and GitHub by falsedan on Wednesday June 06, 2018 @07:11AM (#17246030)
I feel like asking a poject manager to fiddle with some SCM system to get through grooming could be a bit unreasonable. I can't see how Fossil does ticketing to see if it's PM-friendly…

I feel like code reviews naturally should be stored alongside the code it's reviewing, and like the PoC shown by git-appraise from Google[0]

0: https://github.com/google/git-appraise

Re:Gitea – Alternative to GitLab and GitHub by sago on Wednesday June 06, 2018 @06:26AM (#17245840)
I've mused on this in relation to github's pages sitting on the gh-pages branch: a feature I like in the abstract, though I have problems with their implementation (it seems designed to increase lock-in rather than increase flexibility). I'm not sure the VCS needs to build in those tools, but having an established branching convention for associated data could allow many flowers to bloom.