3 ms·

> In particular, your project automatically gets a bug tracker – and you don’t get a choice about what bug tracker to use, or what it looks like. If you use Git

by etaweb 2y ago

> In particular, your project automatically gets a bug tracker – and you don’t get a choice about what bug tracker to use, or what it looks like. If you use Gitlab, you’re using the Gitlab bug tracker. The same goes for the pull request / merge request system. With Forgejo (Codeberg) you can toggle features such as pull requests, issues, etc. You can also configure any external issue tracker or wiki apparently, though I've never tried it, because those included with the forge are good enough for me.

rglullis 2y ago
Forgejo (once federation is implemented) also fixes the main issue of forcing people to have an account at every forge.
- ambigious7777 2y ago
  I do hope that Forgejo Federation is implemented, but it seems to me progress has stalled on it?
- kelnos 2y ago
  It does solve that problem, but then creates a huge spam problem. Over at gitlab.xfce.org we are constantly fighting new spam accounts that get created daily. We've done all the recommended/paranoid things, like not allowing new accounts to fork or create repos until we manually give them permission (among other things), and we have a script that runs hourly to shut down suspicious accounts. But it's still nuts. If anyone with an account on any other gitlab instance could automatically do things on our gitlab instance, it would be a nightmare. We'd probably disable federation if gitlab offered it.
  - pabs3 2y ago
    The only way to do it is disable registration and have people contact you to allow registration.
    - Svenstaro 2y ago
      We do this in Arch Linux. It requires someone handling the registrations which isn't great either.
      - elcritch 2y ago
        Seems like something LLMs should be good at. Take the new user info and ask it to vet the account or raise it to a human.
  - aitchnyu 2y ago
    Umm, why does a spammer bother with getting a Gitlab account in the first place?
    - da_chicken 2y ago
      Because it's $0 access to eyeballs.
  - rglullis 2y ago
    > If anyone with an account on any other gitlab instance could automatically do things on our gitlab instance I think the idea is the exact opposite, no? People wouldn't be able to do anything on your forge. They would only initiate actions on their own server and then send you notifications of PR requests to the ActivityPub inbox of your repository, and spammers would have no incentive to do this because nothing would end up in public view.

by etaweb 2y ago

rglullis 2y ago

Forgejo (once federation is implemented) also fixes the main issue of forcing people to have an account at every forge.

ambigious7777 2y ago
I do hope that Forgejo Federation is implemented, but it seems to me progress has stalled on it?
kelnos 2y ago
It does solve that problem, but then creates a huge spam problem. Over at gitlab.xfce.org we are constantly fighting new spam accounts that get created daily. We've done all the recommended/paranoid things, like not allowing new accounts to fork or create repos until we manually give them permission (among other things), and we have a script that runs hourly to shut down suspicious accounts. But it's still nuts. If anyone with an account on any other gitlab instance could automatically do things on our gitlab instance, it would be a nightmare. We'd probably disable federation if gitlab offered it.
- pabs3 2y ago
  The only way to do it is disable registration and have people contact you to allow registration.
  - Svenstaro 2y ago
    We do this in Arch Linux. It requires someone handling the registrations which isn't great either.
    - elcritch 2y ago
      Seems like something LLMs should be good at. Take the new user info and ask it to vet the account or raise it to a human.
- aitchnyu 2y ago
  Umm, why does a spammer bother with getting a Gitlab account in the first place?
  - da_chicken 2y ago
    Because it's $0 access to eyeballs.
- rglullis 2y ago
  > If anyone with an account on any other gitlab instance could automatically do things on our gitlab instance I think the idea is the exact opposite, no? People wouldn't be able to do anything on your forge. They would only initiate actions on their own server and then send you notifications of PR requests to the ActivityPub inbox of your repository, and spammers would have no incentive to do this because nothing would end up in public view.