Also - nice initiative, I guess, but I have to say their web UI seems to be stuck in the 1990s.
Sourcehut welcomes Bitbucket refugees
21–30 of 219 posts
Re: Sourcehut welcomes Bitbucket refugees
#22Earlier quoted context omitted.
> Where is the source? The homepage links to https://git.sr.ht/~sircmpwn/?search=sr.ht (EDIT: which is now also the URL in the blogpost with the link text "100% open source software") There are also Hg repos at hg.sr.ht; idk how easy it is to find git.sr.ht from hg.sr.ht. > how can they beat Bitbucket while the code is unusable Well, for Hg users, it's not like there's going to be much of a choice in a year (given BB…
Mercurial users can use their builtin Web UI unlike Git users
https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb
But in both cases, the user has to have a server to put it on, making services like Sourcehut and Bitbucket (may it rest in peace) useful.
Re: Sourcehut welcomes Bitbucket refugees
#23Am I the only one who can't find the source of this "open source software"? How they can beat Bitbucket while they hide the code under unusable UI?
Clicking the text "100% open source software" brings you to the following list of git repos which collectively contain the source code for sourcehut: https://git.sr.ht/~sircmpwn/?search=sr.ht
Re: Sourcehut welcomes Bitbucket refugees
#24Earlier quoted context omitted.
Well, the page contains nothing but a tool to import data from a competitor in order to get users of the competitor to sign up for your service. That meets my definition of spam to a certain extend.
The competitor is leaving the market, which hardly makes them a competitor at all. Any users who don't want to be left out in the cold need tools like this.
Re: Sourcehut welcomes Bitbucket refugees
#25Earlier quoted context omitted.
> Where is the source? The homepage links to https://git.sr.ht/~sircmpwn/?search=sr.ht (EDIT: which is now also the URL in the blogpost with the link text "100% open source software") There are also Hg repos at hg.sr.ht; idk how easy it is to find git.sr.ht from hg.sr.ht. > how can they beat Bitbucket while the code is unusable Well, for Hg users, it's not like there's going to be much of a choice in a year (given BB…
Mercurial users can use their builtin Web UI unlike Git users
Re: Sourcehut welcomes Bitbucket refugees
#26Am I the only one who can't find the source of this "open source software"? How they can beat Bitbucket while they hide the code under unusable UI?
Re: Sourcehut welcomes Bitbucket refugees
#27Earlier quoted context omitted.
Clicking the text "100% open source software" brings you to the following list of git repos which collectively contain the source code for sourcehut: https://git.sr.ht/~sircmpwn/?search=sr.ht
Can you make "sr.ht git services" the blue title of the repo "card" and "~sircmpwn/git.sr.ht" - the subtitle (with dimmed color)? This simple change will improve UI usability in 10x times.
Re: Sourcehut welcomes Bitbucket refugees
#28Earlier quoted context omitted.
The competitor is leaving the market, which hardly makes them a competitor at all. Any users who don't want to be left out in the cold need tools like this.
Then why not make the tool open source + standalone and compatible with other alternatives like GitHub/GitLab/Gitea/Gogs/etc. so the users can pick the competitor or tool they like?
Re: Sourcehut welcomes Bitbucket refugees
#29Am I the only one who reads that as "source chute"? Also - nice initiative, I guess, but I have to say their web UI seems to be stuck in the 1990s.
Another way sr.ht is stuck in the 1990s is that it doesn't bludgeon my browser with analytics and gazillion requests like a certain bucket was fond of doing.
In general, sr.ht seems simple, in a very positive way. AFAICT, it doesn't try to compete with the GitHub-ish web UI for pull requests and code review. Personally, I don't mind.
Re: Sourcehut welcomes Bitbucket refugees
#30Am I the only one who reads that as "source chute"? Also - nice initiative, I guess, but I have to say their web UI seems to be stuck in the 1990s.
To some of us decidedly a feature, not a bug. And:
> All features work without JavaScript
My endless upvote.