GNU AGPL? #29

Closed
opened 2026-10-05 03:08:51 +02:00 by adam · 6 comments
Owner

Ever thought of using the GNU AGPL? So that forks of your projetc must open source their code and if someone runs a modified NNTPChan node they must open source their changes as well?

Ever thought of using the GNU AGPL? So that forks of your projetc must open source their code and if someone runs a modified NNTPChan node they must open source their changes as well? <!-- github-sync-id:158517293 -->
adam closed this issue 2026-10-05 03:08:51 +02:00
Author
Owner

I personally dislike the virility clauses in GPL3 which is why I have chosen MIT/X11.

I personally dislike the virility clauses in GPL3 which is why I have chosen MIT/X11. <!-- github-comment-id:223770755 -->
Author
Owner

Okay 😄

Okay :smile: <!-- github-comment-id:223770804 -->
Author
Owner

Whart does "virility" mean?

Whart does "virility" mean? <!-- github-comment-id:223770811 -->
Author
Owner

i used the wrong word here.

what I meant to say is that I dislike AGPL's viral properties, specifically how GPL 3 code cannot be used in non GPL 3 licensed code.

i used the wrong word here. what I meant to say is that I dislike AGPL's viral properties, specifically how GPL 3 code cannot be used in non GPL 3 licensed code. <!-- github-comment-id:223770980 -->
Author
Owner

Oh really.

Oh really. <!-- github-comment-id:223771131 -->
Author
Owner

I wish license writing could be easy. So that everyone could make a license that suits their needs.

I wish license writing could be easy. So that everyone could make a license that suits their needs. <!-- github-comment-id:223771151 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/nntpchan#29