[openstreetmap/openstreetmap-website] Require login for User blocks (#3284)
Frederik Ramm
notifications at github.com
Wed Aug 4 12:59:19 UTC 2021
There was some confusion initially because we equated "logged-in user" and "user who has agreed to the ToU". For a transition period this would not be the case.
Nonetheless, my suggestion would be:
* don't design for a two-tier world; assume that all users who can log in will also have agreed to the ToU. Do not spend any effort on making the "has this user agreed to the ToU" flag externally available since it is temporary; do not spend any effort on keying certain functionality to th "has this user agreed to the ToU" flag.
* start restricting access to some things to users who are logged in (even if, currently, this doesn't mean much)
* separately and independently, work on a timeline and communications strategy to deny login to users who have not agreed to the ToU (along the lines of: announce on the lists, 3 months later show a message upon login that asks people to agree to the ToU but they can click on "not now", another 3 months later remove the "not now" option).
And regarding the latest point, I wouldn't bee overly cautious about what @simonpoole dreads to be "unpopular". Just say these terms of use have been in effect for 2yrs+ now and it's time that everyone sign up to them, it's just a formality, click here and you're done.
Summing up, I think @mmd-osm's approach here is exactly right.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/3284#issuecomment-892636167
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20210804/c69a24b9/attachment.htm>
More information about the rails-dev
mailing list