haskellfoundation / haskellfoundation/haskellfoundation.github.io

Make GfRC retargetable

Aperta
#505 7 commenti 3 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
CSS
Stelle
42
Fork
53
Merge medio
1g 17h
PR unite (30g)
4

Descrizione

CC @hasufell @simonpj @mpilgrem

There are continuous attempts to apply GfRC not only to HF itself, but also to other bodies. Currently most of them are void and null at best, because GfRC as written is not "retargetable". There are a few items which need to be fixed.

* As witnessed recently on more than one occasion, GfRC is not set in stone. An organisation subscribing to GfRC should be able to specify a version (say, v2025.05.09) instead of hotlinking an evolving text.
* Organisations should be able to copy a particular edition of GfRC to their own repository for future reference. This is currently illegal, because GfRC does not grant any license to subscribers. Should be one of Creative Commons licenses, I suppose.
* GfRC should say something like "the participating body" and "the leadership of the participating body" instead of "members of the Haskell Foundation" and "the chair of the Foundation, or the vice-chair or co-chair". I'm not sure what's the standard English legal wording for this, maybe "a group refering to these Guidelines" and "leadership of the group refering to these Guidelines" are most suitable.
* It should be made clear that only the section under "Guidelines For Respectful Communication" is normative and the rest ("Preamble", "Motivation", "Acknowledgements") are not. E. g., an organisation may seek to impose GfRC on its employees, a discussion forum may impose GfRC on all participants, but both cases would contradict Preamble. Similarly, motivations may vary, including "...because my employer told me so" or "...because it's a precondition for affilication with HF" and such.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

L’issue non indica alcun file, test o punto di ingresso. Inizia individuando il documento GfRC e rivedendo la discussione composta da sette commenti, quindi risolvi con i maintainer le questioni relative a versioning, licensing, linguaggio di retargeting e ambito normativo prima di modificare qualsiasi cosa; il lavoro è completo quando è disponibile un testo di linee guida concordato e riutilizzabile.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Ambito
content, documentation
Tipo di issue
Documentazione
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.