A first step could be to collect some (let's say 6 to 8) web startup leaders who are interested in this. Then ask their expectancies and ideas, collect their requirements, discuss with them. I have some ideas who to contact. What do you think?
2014-08-03 21:10 GMT+02:00 Bernát Kalló <[email protected]>: > Wow wow! Thanks JC! > > Bernát > > > 2014-08-03 20:01 GMT+02:00 JC Torpey <[email protected]>: > > From the POV of a writer who's written dozens of TOS, Privacy Policies and >> other contracts including various legal agreement types for websites, >> businesses and fellow freelancers I can say that writing them is even more >> time consuming and difficult than reading them is. >> >> As such, I agree that there has to be a better way and I'd be more than >> happy to collaborate in a first go at a short, sweet and to the point TOS >> template that website owners can use and modify for their individual needs. >> I have experience with Wikip style licensing and contracts plus a few >> attorneys with whom I can collaborate to ensure the proper legalese is >> covered. >> >> I can dedicate a few hours a week to this or to other TOSDR projects (and >> can start anytime after August 8) if anyone is interested in collaborating? >> >> I think its high time we stop waiting for someone else to create the free >> and open Internet that everyone really can use and get to work on it >> ourselves, don't you? >> >> ~~ JC Torpey >> >> >> On Thursday, July 10, 2014 7:00:11 PM UTC-4, Bernát Kalló wrote: >>> >>> Hello! >>> >>> I'm so glad to see your movement! >>> >>> I have a suggestion (don't know if it has been posted already): Why >>> don't you start writing guidelines for those who want to write legally >>> correct but still human-readable ToS? I've seen your Legal page, and it's >>> really nice. But if i have a service, how can i write something this short, >>> while being sure that i won't get into trouble? >>> >>> What could be even cooler is to create ToS templates, like Creative >>> Commons did for licences. I mean, if i'm a developer of a service, i could >>> assemble a ToS from little pieces, something like "tosdr-nw-nhc", which >>> would mean No Warranties provided and No Harmful Content allowed. Of >>> course, usually there would be more pieces than just two. Then users would >>> need to read the respective rules only once. >>> >>> What do you think? >>> >>> Cheers, >>> Bernát >>> >> -- >> tosdr.org | twitter.com/tosdr | github.com/tosdr >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "Terms of Service; Didn't Read" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/tosdr/bGSNRYapLuQ/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/tosdr. >> For more options, visit https://groups.google.com/d/optout. >> > > -- tosdr.org | twitter.com/tosdr | github.com/tosdr --- You received this message because you are subscribed to the Google Groups "Terms of Service; Didn't Read" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tosdr. For more options, visit https://groups.google.com/d/optout.
