- Unofficial Call and Response lyrics
- hidden highlight selection when search with * or # is active
- freestanding quarter turn stair
- Who was the first to say “Shut up and calculate!”?
- Anatomically Correct Demons
- The gun which makes no sound
- Do Gods inherit sins committed by their avataras?
- Can the list of Divyadesams be added to or subtracted from?
- Were Periyalwar and Andal reborn as cowherds?
- Required alt text field in assets
- Issue with Matrix `type` property and Live Preview?
- Help me with this rebus puzzle please
- Who am I? - Riddles
- What and where can I be?
- Bongard number 2 is here
- Wherever I May Roam 2000
- Stuck in an Appliance
- Please help with this geocaching puzzle
- What are the main benefits and issues surrounding data today?
- Using Random Forest Probabilities for customer sensitivity
Does anyone curate terms-of-service boilerplate?
Typically I use boilerplate documents for software license, contributor agreements, code of conduct, and so on. These are typically community-created, verified by legal experts and don't need to be read more than once. If a project says "Apache 2.0" or "Developer Certificate of Origin", I know exactly what that means (and if I don't, I can look it up, or ask questions here!).
I'd like to take the same approach for a terms of service document. Is there any body that curates and approves boilerplate terms of service? (Similarly to how OSI and FSF curate lists of software licenses.)