3 ms·

I realize you're talking about git, but I think it's also pretty important to have a place where users can submit issues and dev's can say "it's fixed in versio

I realize you're talking about git, but I think it's also pretty important to have a place where users can submit issues and dev's can say "it's fixed in version XYZ", these are not features of git. I've been meaning to give radicle a try.

chupapimunyenyo 3y ago
[flagged]
miki123211 3y ago
Fossil does this within the repo, maybe we need a way for Git to do so too.
- __MatrixMan__ 3y ago
  Rather than making it a feature of git, it would probably be sufficient to have a tool that packed issues and PRs from the forge into the repo (in preparation to be migrated) and then unpacked them into the forge's API on the other side.
  - miki123211 3y ago
    This isn't what Fossil does. Fossil lets you synchronize artifacts both ways, so you can clone a repo, participate in discussions when on a plane, write some replies, connect back to the internet and sync them back up to the server. When your server goes down, you don't lose anything. There's no need to remember to back up your issues every day, every time you clone the repo, you also clone its tickets, forum, wiki etc.
- Ayesh 3y ago
  ... Or use Fossil?
  - miki123211 3y ago
    Fossil doesn't have a good story around cross-repo authentication (without separate per-repo accounts), CI/CD, 2FA, SSO support and such. It's a great tool if you're writing a single personal project with little regard for security, but that's about it.
- rkeene2 3y ago
  You can use ChiselApp.com (which I maintain) to host your Fossil as well, and since every clone has the same data (minus passwords) it's trivial to migrate.
asdff 3y ago
You can host your own on your own site. Most major open source projects have their own website anyhow. They really don't need to be on github or gitlab to begin with, just roll it yourself like the rest of your website. The only reason why people do it is because its a meme at this point to have a github (and even gitlab, if only as a foil to github).

chupapimunyenyo 3y ago

[flagged]

miki123211 3y ago

Fossil does this within the repo, maybe we need a way for Git to do so too.

__MatrixMan__ 3y ago
Rather than making it a feature of git, it would probably be sufficient to have a tool that packed issues and PRs from the forge into the repo (in preparation to be migrated) and then unpacked them into the forge's API on the other side.
- miki123211 3y ago
  This isn't what Fossil does. Fossil lets you synchronize artifacts both ways, so you can clone a repo, participate in discussions when on a plane, write some replies, connect back to the internet and sync them back up to the server. When your server goes down, you don't lose anything. There's no need to remember to back up your issues every day, every time you clone the repo, you also clone its tickets, forum, wiki etc.
Ayesh 3y ago
... Or use Fossil?
- miki123211 3y ago
  Fossil doesn't have a good story around cross-repo authentication (without separate per-repo accounts), CI/CD, 2FA, SSO support and such. It's a great tool if you're writing a single personal project with little regard for security, but that's about it.
rkeene2 3y ago
You can use ChiselApp.com (which I maintain) to host your Fossil as well, and since every clone has the same data (minus passwords) it's trivial to migrate.

asdff 3y ago

You can host your own on your own site. Most major open source projects have their own website anyhow. They really don't need to be on github or gitlab to begin with, just roll it yourself like the rest of your website. The only reason why people do it is because its a meme at this point to have a github (and even gitlab, if only as a foil to github).