Changes between Version 1 and Version 2 of doc/developer/TermsOfService

09/10/09 15:10:14 (12 years ago)



  • doc/developer/TermsOfService

    v1 v2  
    4747SELECT * FROM TOS_Accepted_Users WHERE user_id = CurrentUser LIMIT BY 1 
     51=== Some thoughts by gbastien === 
     52Added: september 10, 2009 
     54Here's an attempt to summarize what can be found about the term Of Services from mailing list discussions 
     56There are many scenarios involving the TOS.  One must be able to specify some rules 
     58 1. Whether or not the TOS must be shown 
     59 2. When (once, every time) 
     60 3. To whom (Can this be linked somehow with a profile?  Different profiles can have different TOS with different rules) 
     61 4. How to deal with multiple versions 
     62 5. Is the TOS per node, per network 
     63 6. Should the user accept it explicitly (Agree button) or implicitly (just show the TOS) 
     64 7. Handle multiple languages 
     65 8. A way to see the TOS any time, not just in an acceptance context 
     67The above schema deals with 4 and 5, behavior can be added to get 1 (don't show if networks.default_TOS is null) and 8 (hookMenu of the network to add a new link to the TOS) 
     69There is also Dave's idea to make the TOS a contentType to be added to the contentLibrary, we add rules 7 and 3, but we lose possibilities for 6 and 8 
     71> I handled it by using the HTMLeditor plug in to create an HTML "Terms of use page" that is added to the reusable content library.  I included language that says "By Creating an account and logging in to this network you, the user, are agreeing to the terms of use listed here in." and then continue to list the terms of use.  Then I placed that content on the Login page for the Network. 
     73> Granted the user doesn't have to click a seperate check box to accept the terms, but by placing this on the login page, they are accepting the terms each time they login by the act of logging in.  Which is nice because if your terms of use change, they're automatically accepting the new change the next time they authenticate.