Me too. I can't wait for federation to be done though. Requiring people to register on my personal instance to report bugs or contribute is quite a pain point.
Forgejo v13.0 added the capability to remove EXIF metadata from images that are uploaded in a user’s avatar. Unfortunately, a licensing mistake was made and Forgejo relied on an AGPL-licensed library to accomplish this work. While other options are being pursued, Forgejo has removed this capability to bring us into license compliance.
I mean, they're 100% correct to do this. Forgejo is definitionally a SaaS application thanks to https://codeberg.org/. Specifically because of the affero clause, you can't relicense AGPLv3 code as GPLv3, so you can't include it in the project.
Moving it to some sort of pluggable module would be good, rather than just dropping it though. There's nothing stopping them shipping code that downloads and sets up exif-terminator. I think working with the AGPL would send a good message and set a good example here.
I’ve been working on an alternative Frontend for Forgejo called Joui.
It’s coming together nicely. Currently support v15 and up. I hope they added a action logs api in v16, as that’s one of the most common complaints I get from Joui users.
13 Comments
Alph4d0g@piefed.social · 14 pts · 19d
I dig having my own self hosted instance. Thanks for this awesome tool.
treadful@lemmy.zip · 8 pts · 18d
Me too. I can't wait for federation to be done though. Requiring people to register on my personal instance to report bugs or contribute is quite a pain point.
ikidd@lemmy.dbzer0.com · 7 pts · 18d
I haven't done it, but I think you can add Github and other OIDC providers to Forgejo.
treadful@lemmy.zip · 3 pts · 18d
Interesting. I didn't realize that was more than LDAP. Gonna look into it, thank you.
EDIT: Works great. Just disabled creating new repos, orgs, and local registrations and that's pretty much what I want.
qprimed@lemmy.ml · 4 pts · 19d
absolutely 110%
just recently spun up a instance and its now one of my most vital local services. such satisfaction to strangle the self-inflicted github dependency.
Kissaki@programming.dev · 13 pts · 19d
😬
med@sh.itjust.works · 5 pts · 18d
I mean, they're 100% correct to do this. Forgejo is definitionally a SaaS application thanks to https://codeberg.org/. Specifically because of the affero clause, you can't relicense AGPLv3 code as GPLv3, so you can't include it in the project.
Moving it to some sort of pluggable module would be good, rather than just dropping it though. There's nothing stopping them shipping code that downloads and sets up exif-terminator. I think working with the AGPL would send a good message and set a good example here.
PR
PR commit
Reopened issue to resolve the problem
Kissaki@programming.dev · 10 pts · 19d
Ooh, very nice. Watching for release notifications is something I use excessively on GitHub. Looking forward to being able to use that on Codeberg.
vinnymac@lemmy.world · 6 pts · 18d
I’ve been working on an alternative Frontend for Forgejo called Joui.
It’s coming together nicely. Currently support v15 and up. I hope they added a action logs api in v16, as that’s one of the most common complaints I get from Joui users.
nykula@piefed.social · 1 pts · 17d
Interesting, where can I find the Joui code? Quick web search only returns the main Forgejo frontend.
vinnymac@lemmy.world · 3 pts · 17d
It’s currently a private beta, and will be AGPLv3 licensed when I open source it.
In case you just want to see it, here are the only public screenshots of it I’ve shared https://mastodon.social/@vinnymac/116660529396212878
It has some Ui customization settings as well built in, including tweaking the theme and accents.
That was months ago though.
xyro@morbier.foo · 3 pts · 18d
Yay, no need to work around that anymore !
tristynalxander@mander.xyz · 3 pts · 18d
ikidd@lemmy.dbzer0.com · 4 pts · 18d
Still a work in progress as far as I know.