{"action":"closed","issue":{"url":"https://api.github.com/repos/doubleunion/arooo/issues/214","labels_url":"https://api.github.com/repos/doubleunion/arooo/issues/214/labels{/name}","comments_url":"https://api.github.com/repos/doubleunion/arooo/issues/214/comments","events_url":"https://api.github.com/repos/doubleunion/arooo/issues/214/events","html_url":"https://github.com/doubleunion/arooo/issues/214","id":103463838,"number":214,"title":"Update keymember form to note keycode availability and orientation/meeting requirement","user":{"login":"brittag","id":391313,"avatar_url":"https://avatars.githubusercontent.com/u/391313?v=3","gravatar_id":"","url":"https://api.github.com/users/brittag","html_url":"https://github.com/brittag","followers_url":"https://api.github.com/users/brittag/followers","following_url":"https://api.github.com/users/brittag/following{/other_user}","gists_url":"https://api.github.com/users/brittag/gists{/gist_id}","starred_url":"https://api.github.com/users/brittag/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brittag/subscriptions","organizations_url":"https://api.github.com/users/brittag/orgs","repos_url":"https://api.github.com/users/brittag/repos","events_url":"https://api.github.com/users/brittag/events{/privacy}","received_events_url":"https://api.github.com/users/brittag/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-08-27T09:12:08Z","updated_at":"2016-01-31T22:11:55Z","closed_at":"2016-01-31T22:11:55Z","body":"Currently when new members join DU, they sometimes see the key member form and immediately fill it out, which is excellent enthusiasm but can lead to a bit of confusion, and we should update the form to make more sense for that membership flow. :)\r\n\r\nFor reference, the form: https://github.com/doubleunion/arooo/blob/master/app/views/members/statuses/edit.html.haml\r\n\r\nFirst, the page could mention how to get a keycode, since this is relevant information for brand-new members who want access to the space. This could look like this:\r\n\r\n    %h1 Get a key code as a member!\r\n\r\n    %p [paste the relevant paragraph from the Member Handbook]\r\n\r\n    %p Check out the [Member Handbook](link) for more detail about accessing the space, guest policies, and other relevant information.\r\n\r\nThen the page could continue with the \"Become a key member!\" section.\r\n\r\nThe second part: if a member would like to become a key member, they should meet at least the requirements for getting a keycode, and we could make that explicit in the form with a checkbox labeled something like \"I've attended at least two events at DU (including at least one members meeting or orientation), and I've looked through the Member Handbook.\"\r\n\r\nThis is open to adjustment and a little bit complex, so I'm filing it as an issue instead of a pull request. :)\r\n\r\n(Last month I emailed the board about making the keymember requirements explicitly include the keycode requirement, and one of them responded affirmately that this makes sense.)"}}