Trying out #gitea http://gitea.io/ self-hosted git service.

1. Looks very lightweight.
2. Written in Go.
3. Free Software.

Gitlab seems very heavy to me, especially the responsiveness of the User Interface, while gitea interface looks very clean, minimal and responsive. I hope the similar is true with gogs as well. Thinking about self-hosting my repositories using gitea using #orangepi

Another self-hosted git service I came across recently is #pagure. https://pagure.io/pagure

However, I'm still running #cgit for the time being.
@arunisaac Does pagure supports wiki for repos? I see #gitea and #gogs being lightweight have almost all features that #github and #gitlab does.
Yes, I think #pagure supports wikis. I have not used pagure, but the pagure project site says so. https://pagure.io/pagure
"With pagure you can host your project with its documentation, let your users report issues or request enhancements using the ticketing system and build your community of contributors by allowing them to fork your projects and contribute to it via the now-popular pull-request mechanism."
@arunisaac Also I love the single binary file to start using #gitea and #gogs right away.
What I dislike about #gitlab, #gitea, #gogs and other similar projects is that any user who wants to contribute to one of your repos must create an account in your instance. So, you are forced to run a public instance. It's unpleasant business to run large public instances. It becomes a single point of failure. And, benefits of decentralization are diminished or lost.

We need something P2P or federated for hosting git. Some approaches I've heard of are #gittorrent, git over #ipfs, #bugseverywhere and #ditz. However, many of these projects are inactive and don't seem to be maintained. :-(
@arunisaac Yes. I have also been looking at distributed git. Remember #ssbc? git on top of ssbc https://github.com/clehner/git-ssb