HowTo Licencing #137

Open
opened 2 months ago by fnetX · 1 comments
fnetX commented 2 months ago
Collaborator

I had this on my backlog for a while, but won't manage to write this anytime soon.

I think, we as Codeberg, could make well use of a guide to Licences. Although, we don't need to give legal advice here, it would be cool to

  • explain that Codeberg content requires a valid licence
  • point out the issues of not having a licence
  • tell users that approved licences are not equally easy to use (e.g. I heard of legal trouble by using the Unlicence or WTFPL and similar as these are not always properly applicable in all jurisdictions)
  • compare some common and well-known licences and probably tell users to just chose one of them
  • especially explain what Copyleft means, also for the daily use of the material
  • give some overview of Licence compatibility - what can include which licenced material and how can you maybe use incompatible material by shipping it separately ...
  • clarify some common issues with licences, e.g. clarifying how to apply them properly and unmistakably (also see Codeberg/Community#407 -ONLY vs. -OR-LATER variants must be done by the user for example)
  • maybe even go so far as explaining why non OSI / FSF approved licences might be dangerous
  • in any cases link to more resources

This is a broad topic and an initial version does definitely not need to cover all this. The debate over Licences is controversial, it would be really neat to give users a first starting point for their daily work at Codeberg, but leave the really complicated topics to good links in other parts of the web ...

I had this on my backlog for a while, but won't manage to write this anytime soon. I think, we as Codeberg, could make well use of a guide to Licences. Although, we don't need to give legal advice here, it would be cool to - explain that Codeberg content requires a valid licence - point out the issues of not having a licence - tell users that approved licences are not equally easy to use (e.g. I heard of legal trouble by using the Unlicence or WTFPL and similar as these are not always properly applicable in all jurisdictions) - compare some common and well-known licences and probably tell users to just chose one of them - especially explain what Copyleft means, also for the daily use of the material - give some overview of Licence compatibility - what can include which licenced material and how can you maybe use incompatible material by shipping it separately ... - clarify some common issues with licences, e.g. clarifying how to apply them properly and unmistakably (also see https://codeberg.org/Codeberg/Community/issues/407#issuecomment-180493, chosing -ONLY vs. -OR-LATER variants must be done by the user for example) - maybe even go so far as explaining why non OSI / FSF approved licences might be dangerous - in any cases link to more resources This is a broad topic and an initial version does definitely not need to cover all this. The debate over Licences is controversial, it would be really neat to give users a first starting point for their daily work at Codeberg, but leave the really complicated topics to good links in other parts of the web ...
fnetX added the
Kind: Documentation
Kind: Enhancement
Priority: Medium
labels 2 months ago
Poster
Collaborator

@yp Are you by chance interested in picking this up? I assume you are mayhaps a person who can give many arguments on this topic, and at least having a draft could be a good starting point to spread awareness on the matter.

The main issue we're seeing right now is that we don't yet have a good resource to point users at. When we see a repo with troublesome licencing, we usually start explaining from the beginning why this is a matter. I probably spent hours on Mastodon telling users that their custom licence is not a really good idea and other discussions, forming all this into a neat and easy-to-understand document will help us a lot with the mission of spreading FLOSS awareness.

@yp Are you by chance interested in picking this up? I assume you are mayhaps a person who can give many arguments on this topic, and at least having a draft could be a good starting point to spread awareness on the matter. The main issue we're seeing right now is that we don't yet have a good resource to point users at. When we see a repo with troublesome licencing, we usually start explaining from the beginning why this is a matter. I probably spent hours on Mastodon telling users that their custom licence is not a really good idea and other discussions, forming all this into a neat and easy-to-understand document will help us a lot with the mission of spreading FLOSS awareness.
n added the
Status: Help wanted
label 3 weeks ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.