this post was submitted on 22 Aug 2024
48 points (98.0% liked)

Forgejo

140 readers
1 users here now

This is a community dedicated to Forgejo.

Useful links:

Rules:

founded 1 year ago
MODERATORS
alx
you are viewing a single comment's thread
view the rest of the comments
[–] v9CYKjLeia10dZpz88iU -3 points 3 months ago* (last edited 3 months ago) (2 children)

Isn't GitTea still under the MIT? I just don't see the purpose for switching licenses, I didn't think it was significantly different. It really doesn't matter to me though, I didn't plan on creating a custom version anyway.

[–] [email protected] 5 points 3 months ago (1 children)

If you had read the very short blog post you would have learned that they wanted to merge in some GPL licensed code contributions. This sort of behavior is exactly what the GPL copyleft language is intended to encourage.

[–] v9CYKjLeia10dZpz88iU 1 points 3 months ago

I had read the discussion in the past and saw they already had GPL related dependencies they had pulled into the repository. I don't know the full history or the contributors project goals. I usually don't find GPL code hard to avoid in normal MIT projects already separated from the GPL, but I can't state an opinion because I haven't tried to understand the background. This is to say, I don't find it completely convincing, and view it partially related to the contributors just liking the GPL.

I wouldn't personally make this choice because the project competes with an MIT licensed version. As an example, one of their goals is federation which might bring companies which realize they don't need GitHub to promote their projects or collaborate. If their competition does the same, those companies might be more likely to choose the permissively licensed version instead. Though, this is a hypothetical example, and I think I'm just negatively biased against the GPL.