CodingTrain / CodingTrain/ChooChooTweets
Consider Using an Ethical Open Source Licence
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- JavaScript
- Sterne
- 14
- Forks
- 2
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
It would be worth considering an ethical open source licence in this project given the nature of internet bots being used in unconstructive ways.
[The Ethical Source Movement](https://ethicalsource.dev/licenses/) is an organization that has a website with a list of some of the more developed licenses.
After looking through the licenses and understanding them to the best of my ability I think the [Do No Harm Licence](https://github.com/raisely/NoHarm) maybe the most promising. However, I think it has some short comings when it comes to this project. It doesn't cover spreading misinformation, discrimination against people with disabilities, and is generally a bit vague.
Also it's based on GPL-3 which forces users of the code to adopt the same licence for their project unlike MIT. As far as I understand someone could potentially change one line under an MIT based licence and put the resulting code under another licence thus making attempt for an ethical licence essentially useless. Not a lawyer so I could be wrong about that.
The vagueness of the Do No Harm Licence is not great because from what I've read about these licenses the more specific they are the more theoretically enforceable they are. So if it was more precise then it would be a greater deterrent to misuse. However I think there's maybe a limit to complexity of the licence being a good thing, because if it's an uncommon licence then lay people need to be able to understand how they are allowed to use the project.
Maybe the best method if you think it's worth using an ethical licence is to ether fork or create a new one which is more targeted at tools that are for making bots online. @shiffman would love to hear your thoughts.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Keine Datei, kein Test und kein Einstiegspunkt sind angegeben. Überprüfe die aktuellen MIT-Lizenzbedingungen des Projekts sowie die verlinkten Materialien von Ethical Source Movement und Do No Harm Licence; das Issue wäre erst abgeschlossen, nachdem die Maintainer entschieden haben, ob sie eine Lizenz übernehmen, erstellen oder beibehalten wollen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- javascript
- Bereich
- documentation
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 20/100