5 ms·

I'm looking forward to this. As of now, if you want to contain development of your software to your personal gitea instance, you are actually raising the comple

I'm looking forward to this. As of now, if you want to contain development of your software to your personal gitea instance, you are actually raising the complexity for new contributors, as they have to create a new account on your instance to create issues and pull requests. This is even worse if the instance is with closed registration and others are not supposed to create accounts there.

codetrotter 3y ago
Speaking of Gitea, it is worth to point out that on the OP website they mention that Forgejo is working on implementing ForgeFed. Forgejo in turn, is a fork of Gitea. So anyone currently running their own instance of Gitea should consider keeping an eye on Forgejo. https://forgejo.org/ https://forgejo.org/
- ComputerGuru 3y ago
  How split is the community over this? I had front row seats to the gogs vs gitea split and it was clear that gitea had the upper hand when it came to momentum there. Is there a similar consensus now?
  - xena 3y ago
    It's too early to know for sure yet.
  - Macha 3y ago
    My impression is that Forgejo is at this point mostly a "swap the names" fork, along with a few features that Gitea dropped the ball on like ForgeFed. At the same time, Gitea has developed some pretty big enhancements to CI in that time so there's definitely a lot more development going on in Gitea. The largest hosted instance, Codeberg has thrown in behind the Forgejo fork, which is the largest endorsement it has, but I think a lot of smaller instance operators are either continuing with Gitea or adopting a wait and see approach. I think the real test for Forgejo is how sustainable it will be once the codebases diverge to the extent that it can't just rebase on Gitea for the feature work Gitea does.
    - Semaphor 3y ago
      > once the codebases diverge to the extent that it can't just rebase on Gitea for the feature work Gitea does. The plan is to stay close enough for that not to happen, at least that’s how I understand it.
      - sangnoir 3y ago
        > The plan is to stay close enough for that not to happen, at least that’s how I understand it. That's a shame. I have no interest in CI and other "enterprise-y" features and was hoping to side-grade to Forgejo. I run my instance on an Raspberry Pi Zero and my non-latest version of Gitea is a memory-hog as it is. I'll be giving Gogs another look.
  - Encrypt-Keeper 3y ago
    Forgejo is just Gitea with extra features potentially extra bolted on top.
- vilunov 3y ago
  Before I learned about that I usually dismissed Forgejo as an unimportant fork which will die off pretty quickly, but support of ForgeFed makes me seriously consider migrating from Gitea. I still believe that Gitea's org strategy is the right one in the long run, however.
- lolinder 3y ago
  Note that Forgejo is specifically planning on contributing ForgeFed upstream when they're done: > We're planning on merging federation into Forgejo first, then upstreaming it to Gitea. There are other reasons to switch to the fork, but I think you'll get ForgeFed either way, which is as it should be. The more participation in the protocol the better! https://codeberg.org/forgejo/forgejo/issues/59 https://codeberg.org/forgejo/forgejo/issues/59
immibis 3y ago
We all used to create accounts all over the internet all the time for everything. What happened to that?
- vidarh 3y ago
  What happened is that it massively sucks.
  - api 3y ago
    It sucks less than it did back then since today we have password managers.
  - lelanthran 3y ago
    > What happened is that it massively sucks. Until you say a naughty word on some forum, and Google bans your account and you cannot log in anywhere. Or you say a naughty word on some forum and Microsoft bans you, so your GH account gets closed, your xbox stops working and you have to wipe Windows and install Linux and hope like hell that you have a local copy of all your 365 docs. Far fetched? Maybe it is, but I feel less anxiety by having separate accounts everywhere.
    - lolinder 3y ago
      The premise of ForgeFed is that you'd have one account but that one account would not need to be under the control of a corporation, you could have a private instance that you used interact with all open source software projects.
      - lelanthran 3y ago
        > The premise of ForgeFed is that you'd have one account but that one account would not need to be under the control of a corporation, you could have a private instance that you used interact with all open source software projects. Yes, but maintaining my own private instance sucks more than remembering a handful of account credentials.
Klonoar 3y ago
Can’t you just allow Github/etc OAuth?
- vilunov 3y ago
  I host a number of services for me and close friends and family, and I limit the access by manually creating accounts for them. I could enable OAuth via 3rd party service, but that would mean I'll have to pay much more attention to setup of ACLs, as these users will have a new account created for them with a link to their Github account. Besides, I want to stay more or less independent from 3rd party services, particularly I'm bothered by the need to explicitly register an OAuth client. AP has a much better flow in that regard, services can interoperate without a given permission to do so.
- lolinder 3y ago
  Most of the point of running your own Gitea instance is to help move FOSS away from GitHub's stranglehold. A proper federation protocol for the decentralized alternatives would be far more useful for that goal than enabling GitHub OAuth.
  - Klonoar 3y ago
    Look, I'm aware of the point of Gitea/etc. I also don't really care. I want people to be able to easily contribute so they don't give up and just go back to GitHub. OAuth with a GitHub access level solves this, full stop. A proper federation protocol is correct and the right option long term but there is no need to knock what actually works right this moment. Doing the right option often takes far longer than is ideal.
    - nine_k 3y ago
      For people using GitHub, yes. The point is to allow people not using GitHub to contribute easily. OAuth and ForgeFed solve different, though related, problems.

codetrotter 3y ago

Speaking of Gitea, it is worth to point out that on the OP website they mention that Forgejo is working on implementing ForgeFed. Forgejo in turn, is a fork of Gitea. So anyone currently running their own instance of Gitea should consider keeping an eye on Forgejo. https://forgejo.org/ https://forgejo.org/

ComputerGuru 3y ago
How split is the community over this? I had front row seats to the gogs vs gitea split and it was clear that gitea had the upper hand when it came to momentum there. Is there a similar consensus now?
- xena 3y ago
  It's too early to know for sure yet.
- Macha 3y ago
  My impression is that Forgejo is at this point mostly a "swap the names" fork, along with a few features that Gitea dropped the ball on like ForgeFed. At the same time, Gitea has developed some pretty big enhancements to CI in that time so there's definitely a lot more development going on in Gitea. The largest hosted instance, Codeberg has thrown in behind the Forgejo fork, which is the largest endorsement it has, but I think a lot of smaller instance operators are either continuing with Gitea or adopting a wait and see approach. I think the real test for Forgejo is how sustainable it will be once the codebases diverge to the extent that it can't just rebase on Gitea for the feature work Gitea does.
  - Semaphor 3y ago
    > once the codebases diverge to the extent that it can't just rebase on Gitea for the feature work Gitea does. The plan is to stay close enough for that not to happen, at least that’s how I understand it.
    - sangnoir 3y ago
      > The plan is to stay close enough for that not to happen, at least that’s how I understand it. That's a shame. I have no interest in CI and other "enterprise-y" features and was hoping to side-grade to Forgejo. I run my instance on an Raspberry Pi Zero and my non-latest version of Gitea is a memory-hog as it is. I'll be giving Gogs another look.
- Encrypt-Keeper 3y ago
  Forgejo is just Gitea with extra features potentially extra bolted on top.
vilunov 3y ago
Before I learned about that I usually dismissed Forgejo as an unimportant fork which will die off pretty quickly, but support of ForgeFed makes me seriously consider migrating from Gitea. I still believe that Gitea's org strategy is the right one in the long run, however.
lolinder 3y ago
Note that Forgejo is specifically planning on contributing ForgeFed upstream when they're done: > We're planning on merging federation into Forgejo first, then upstreaming it to Gitea. There are other reasons to switch to the fork, but I think you'll get ForgeFed either way, which is as it should be. The more participation in the protocol the better! https://codeberg.org/forgejo/forgejo/issues/59 https://codeberg.org/forgejo/forgejo/issues/59

immibis 3y ago

We all used to create accounts all over the internet all the time for everything. What happened to that?

vidarh 3y ago
What happened is that it massively sucks.
- api 3y ago
  It sucks less than it did back then since today we have password managers.
- lelanthran 3y ago
  > What happened is that it massively sucks. Until you say a naughty word on some forum, and Google bans your account and you cannot log in anywhere. Or you say a naughty word on some forum and Microsoft bans you, so your GH account gets closed, your xbox stops working and you have to wipe Windows and install Linux and hope like hell that you have a local copy of all your 365 docs. Far fetched? Maybe it is, but I feel less anxiety by having separate accounts everywhere.
  - lolinder 3y ago
    The premise of ForgeFed is that you'd have one account but that one account would not need to be under the control of a corporation, you could have a private instance that you used interact with all open source software projects.
    - lelanthran 3y ago
      > The premise of ForgeFed is that you'd have one account but that one account would not need to be under the control of a corporation, you could have a private instance that you used interact with all open source software projects. Yes, but maintaining my own private instance sucks more than remembering a handful of account credentials.

Klonoar 3y ago

Can’t you just allow Github/etc OAuth?

vilunov 3y ago
I host a number of services for me and close friends and family, and I limit the access by manually creating accounts for them. I could enable OAuth via 3rd party service, but that would mean I'll have to pay much more attention to setup of ACLs, as these users will have a new account created for them with a link to their Github account. Besides, I want to stay more or less independent from 3rd party services, particularly I'm bothered by the need to explicitly register an OAuth client. AP has a much better flow in that regard, services can interoperate without a given permission to do so.
lolinder 3y ago
Most of the point of running your own Gitea instance is to help move FOSS away from GitHub's stranglehold. A proper federation protocol for the decentralized alternatives would be far more useful for that goal than enabling GitHub OAuth.
- Klonoar 3y ago
  Look, I'm aware of the point of Gitea/etc. I also don't really care. I want people to be able to easily contribute so they don't give up and just go back to GitHub. OAuth with a GitHub access level solves this, full stop. A proper federation protocol is correct and the right option long term but there is no need to knock what actually works right this moment. Doing the right option often takes far longer than is ideal.
  - nine_k 3y ago
    For people using GitHub, yes. The point is to allow people not using GitHub to contribute easily. OAuth and ForgeFed solve different, though related, problems.