I worked at a place that just had a git on a sftp server and that was it. Worked well in a small team. Git is made for it.
Having a separate issue tracker turned out to not be a big deal at all. Theres a lot of niceties github has, but it turns out you really dont need a whole bunch to make good software.
Nowadays i would probably go with gitea or forgeo if I had to self host, but git by itself is perfectly fine.
I worked at a place that just had a git on a sftp server and that was it. Worked well in a small team. Git is made for it.
Having a separate issue tracker turned out to not be a big deal at all. Theres a lot of niceties github has, but it turns out you really dont need a whole bunch to make good software.
Nowadays i would probably go with gitea or forgeo if I had to self host, but git by itself is perfectly fine.
Did you not do code reviews? It’s the main thing I would miss. Being able to comment in-line, and manage iterations, is very valuable to me.
We did. You bring down the branch and then discuss. We used jetbrains and it had a function like that. But it was a while back.
Gerrit still exists for that. Whether it’s currently best, idk.
Gerrit is a hosted service, no?
You can self host it.
Their comment was about not having any hosted service though.
What does that even mean? If it’s a service, it’s a program running on some computer somewhere. Is that not hosting?
They were talking about hosting the git repository via sftp - so bare file transfer - a bare repository. And how that was enough for them.
While that is also hosted, and hosted through a service, it’s only a file transfer service and hosting.
That means specifically without a hosted service like a forge or gerrit.
Which is why I was interested in how they handle stuff that is usually done through such forges and services / hosted software.
Oh I see. The Linux kernel has been doing fine with mailing lists (LKML) for decades, if that helps.