{"action":"created","issue":{"url":"https://api.github.com/repos/openstreetmap/operations/issues/162","repository_url":"https://api.github.com/repos/openstreetmap/operations","labels_url":"https://api.github.com/repos/openstreetmap/operations/issues/162/labels{/name}","comments_url":"https://api.github.com/repos/openstreetmap/operations/issues/162/comments","events_url":"https://api.github.com/repos/openstreetmap/operations/issues/162/events","html_url":"https://github.com/openstreetmap/operations/issues/162","id":227972284,"number":162,"title":"Policy for new OAuth providers","user":{"login":"Zverik","id":766031,"avatar_url":"https://avatars2.githubusercontent.com/u/766031?v=3","gravatar_id":"","url":"https://api.github.com/users/Zverik","html_url":"https://github.com/Zverik","followers_url":"https://api.github.com/users/Zverik/followers","following_url":"https://api.github.com/users/Zverik/following{/other_user}","gists_url":"https://api.github.com/users/Zverik/gists{/gist_id}","starred_url":"https://api.github.com/users/Zverik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Zverik/subscriptions","organizations_url":"https://api.github.com/users/Zverik/orgs","repos_url":"https://api.github.com/users/Zverik/repos","events_url":"https://api.github.com/users/Zverik/events{/privacy}","received_events_url":"https://api.github.com/users/Zverik/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-05-11T12:20:04Z","updated_at":"2017-05-16T08:39:07Z","closed_at":null,"body":"This is a draft I came up with, prompted by @lonvia in https://github.com/openstreetmap/openstreetmap-website/pull/1433. How does it look?\r\n\r\n# Policy for new OAuth providers\r\n\r\nBesides the usual login and password, people use special buttons for signing in to OpenStreetMap with a social account. For example, with Facebook or GitHub. These buttons link a user’s profile to the authentication provider, allowing them to sign in with one click. This way a new user doesn’t even have to have a password: their social provider authenticates them instead.\r\n\r\nAny authentication providers that is used by OpenStreetMap mappers can be added to the signing up page. To prevent overcrowding of the page and ensure people do not lose their accounts, we have a few requirements for a new auth provider:\r\n\r\n1. Published gem with an [OmniAuth strategy](https://github.com/omniauth/omniauth/wiki/strategy-contribution-guide). The OSM website uses OmniAuth for interacting with auth providers, so there is no way around it.\r\n1. Pull request to the [openstreetmap-website](https://github.com/openstreetmap/openstreetmap-website) that adds the support. It should affect:\r\n    * Gemfiles.\r\n    * Example.application.yml and omniauth.rb in the config directory.\r\n    * Lib/auth.rb, login.html.erb, en locale and an icon for the web interface.\r\n    * Tests for user creation, user controller and user login.\r\n1. Three active mappers must use the authentication service and vouch for its support. Active means at least 500 mapping days on the [HDYC profile](https://hdyc.neis-one.org/). This ensures that a much greater number of casual mappers might also benefit from the new provider.\r\n1. At least hundred thousand users or a sizable part of a specialized community should be registered in the service (shown with either a direct number or a related statistics), and there should be other pointers that it would not go offline in three years. That might mean a roadmap, a financial backing, infrastructure built on top of the service (popular apps, connections with other services) etc.\r\n1. For enabling auto-validation of email addresses, a proof that all addresses that the auth provider sends via API are validated beforehand either by sending an email to a user, or by acquiring these from a provider that validates addresses this way.\r\n\r\nCompliance to all five of these requirements does not guarantee that the auth provider will be immediately supported by the OpenStreetMap website by merging the corresponding pull request. But it remove most, if not all, non-technical questions, so your request is processed without involving other working groups and without sidetracking."},"comment":{"url":"https://api.github.com/repos/openstreetmap/operations/issues/comments/301714789","html_url":"https://github.com/openstreetmap/operations/issues/162#issuecomment-301714789","issue_url":"https://api.github.com/repos/openstreetmap/operations/issues/162","id":301714789,"user":{"login":"Zverik","id":766031,"avatar_url":"https://avatars2.githubusercontent.com/u/766031?v=3","gravatar_id":"","url":"https://api.github.com/users/Zverik","html_url":"https://github.com/Zverik","followers_url":"https://api.github.com/users/Zverik/followers","following_url":"https://api.github.com/users/Zverik/following{/other_user}","gists_url":"https://api.github.com/users/Zverik/gists{/gist_id}","starred_url":"https://api.github.com/users/Zverik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Zverik/subscriptions","organizations_url":"https://api.github.com/users/Zverik/orgs","repos_url":"https://api.github.com/users/Zverik/repos","events_url":"https://api.github.com/users/Zverik/events{/privacy}","received_events_url":"https://api.github.com/users/Zverik/received_events","type":"User","site_admin":false},"created_at":"2017-05-16T08:39:07Z","updated_at":"2017-05-16T08:39:07Z","body":"So \"bugger off\" to any service that mapper use, but that hasn't got wide adoption among the regular public? How adding \"small\" providers with e.g. hundreds of thousand users would hurt the website?"}}
{"actor":{"display_login":"Zverik"}}