I recently contributed to a project hosted on sr.ht for the first time. It took some getting used to. I can see the potential, but there are some sharp edges.<p>The email-based workflow could be convenient for some, but speaking for myself, I'd mainly prefer to interact via the web UI. The ability to send updates to patches submitted from the web UI seems to be missing. If I made a mistake or was asked to change something, I had to completely re-submit the patch as a separate email. I couldn't find a way to communicate on mailing lists without using an external email client. Basic things, like needing to hand-wrap my emails at 70-something characters, and remember to remove quoted text from the bottom of emails, is an unfortunate barrier to entry for new contributors. All of these things could be abstracted away via the web UI for those who don't want to use email.
> Welcome to sourcehut! This suite of open source tools is the software development platform you've been waiting for.<p>> Git and Mercurial hosting, mailing lists, bug tracking, continuous integration, and more<p>> Absolutely no tracking or advertising<p>> All features work without JavaScript<p>> 100% free and open source software<p>For someone who is not familiar with sourcehut what other benefits does it provide over gitlab?<p>(Don't get me wrong i absolutely like that every feature works without javascript, i am just curious)
I really like the page design, very clear and non-flashy. Looks like time was well spent delivering features and good performance instead of building a "beautiful" page.
Full transparency: I'm trying to build something similar at <a href="https://gopherworks.io" rel="nofollow">https://gopherworks.io</a> if anyone's interested in helping.<p>I recently wrote an article for my own code hosting service where I talked a little about SourceHut and what makes it unique:<p>- SourceHut follows a zero investor approach [1]<p>- SourceHut's Principal Engineer, Drew Devault, prides himself in simple infrastructure [2]<p>- Drew believes Mailing List Workflows are the way forward [3]<p>- SourceHut is designed for accessibility first [4]<p>[1] <a href="https://sourcehut.org/blog/2019-10-23-srht-puts-users-first/" rel="nofollow">https://sourcehut.org/blog/2019-10-23-srht-puts-users-first/</a><p>[2] <a href="https://sourcehut.org/blog/2020-04-20-prioritizing-simplitity/" rel="nofollow">https://sourcehut.org/blog/2020-04-20-prioritizing-simplitit...</a><p>[3] <a href="https://sourcehut.org/blog/2020-10-29-how-mailing-lists-prevent-censorship/" rel="nofollow">https://sourcehut.org/blog/2020-10-29-how-mailing-lists-prev...</a><p>[4] <a href="https://sourcehut.org/blog/2020-05-27-accessibility-through-simplicity/" rel="nofollow">https://sourcehut.org/blog/2020-05-27-accessibility-through-...</a><p>SourceHut is an interesting concept and basically the equivalent of a built-at-home GitHub. It's based on Python (and now Go), runs on Alpine on baremetal in a datacenter in the US. Some of the above aren't just views for SourceHut though, they're more like a way of life. If you'd like to test that join the SourceHut channel on Freenode and ask if anyone has any reference for Dockerfiles or Kubernetes and see what response you get.<p>SourceHut and other code hosting sites are popping up as a wave of programmers push for decentralization. Some may say that it's in response to youtube-dl, but this has been happening slowly for a while. If SourceHut isn't right for you there's always Codeberg which is essentially a Gitea instance backed by a non-profit in the EU.
Been using sourcehut little over a year now. I'm a fan<p>Looks real good in dark mode via the standard "dark reader" browser plugin most people use these days, btw. Would love to see them add a native dark mode though. That's my main gripe.
I've looked at this with some curiosity over the past year, but it was only this morning that I decided to take a closer look. While I'm a huge fan of GitLab, I think this is really something special. I spent $50 to show some support and I'd like to find other ways I can contribute.
I know Drew is very adamant about using mailing lists instead of pull requests. However, I like the public nature of pull requests and how they archive discussions.<p>Is there anything that already exists out there to bring that functionality to the email workflow?
Any one have personal experiences on self hosting an instance that they wish to share? I keep meaning to look in to it a bit more, but always seem to end up nudging it down the list.
I wish more of the SourceHut stack was written in Go, like Gitea. It would greatly increase performance and simplify deployment. Long-waited NetBSD support in CI[1] would be awesome to be finished too.<p>[1] <a href="https://git.sr.ht/~sircmpwn/builds.sr.ht/tree/master/images/netbsd" rel="nofollow">https://git.sr.ht/~sircmpwn/builds.sr.ht/tree/master/images/...</a>