{"action":"created","issue":{"url":"https://api.github.com/repos/jmmastey/level_up/issues/71","labels_url":"https://api.github.com/repos/jmmastey/level_up/issues/71/labels{/name}","comments_url":"https://api.github.com/repos/jmmastey/level_up/issues/71/comments","events_url":"https://api.github.com/repos/jmmastey/level_up/issues/71/events","html_url":"https://github.com/jmmastey/level_up/issues/71","id":55393621,"number":71,"title":"[Discussion] Use LevelUp with a group","user":{"login":"GeekOnCoffee","id":240650,"avatar_url":"https://avatars.githubusercontent.com/u/240650?v=3","gravatar_id":"","url":"https://api.github.com/users/GeekOnCoffee","html_url":"https://github.com/GeekOnCoffee","followers_url":"https://api.github.com/users/GeekOnCoffee/followers","following_url":"https://api.github.com/users/GeekOnCoffee/following{/other_user}","gists_url":"https://api.github.com/users/GeekOnCoffee/gists{/gist_id}","starred_url":"https://api.github.com/users/GeekOnCoffee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GeekOnCoffee/subscriptions","organizations_url":"https://api.github.com/users/GeekOnCoffee/orgs","repos_url":"https://api.github.com/users/GeekOnCoffee/repos","events_url":"https://api.github.com/users/GeekOnCoffee/events{/privacy}","received_events_url":"https://api.github.com/users/GeekOnCoffee/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-01-25T02:54:28Z","updated_at":"2015-01-29T18:11:48Z","closed_at":null,"body":"We just had our first real Ruby training in Green Bay a month or so ago. I'm now looking for something to continue the learning, and I think LevelUp would be great. \r\n\r\n`/users` is a great start (though it's unclear how to set a user's organization other than via the console) and there's likely a lot more data that would be useful to support the mentor/mentee relationship. \r\n\r\nI think there's some gaps in my understanding of how the workflow should work for a group, so maybe some documentation on that would help as well. \r\n\r\n@jmmastey mentioned he had some thoughts and this would be a good place to start, any features that will be beneficial to the global codebase I'd be potentially looking at submitting pull requests for. "},"comment":{"url":"https://api.github.com/repos/jmmastey/level_up/issues/comments/72074451","html_url":"https://github.com/jmmastey/level_up/issues/71#issuecomment-72074451","issue_url":"https://api.github.com/repos/jmmastey/level_up/issues/71","id":72074451,"user":{"login":"jmmastey","id":302011,"avatar_url":"https://avatars.githubusercontent.com/u/302011?v=3","gravatar_id":"","url":"https://api.github.com/users/jmmastey","html_url":"https://github.com/jmmastey","followers_url":"https://api.github.com/users/jmmastey/followers","following_url":"https://api.github.com/users/jmmastey/following{/other_user}","gists_url":"https://api.github.com/users/jmmastey/gists{/gist_id}","starred_url":"https://api.github.com/users/jmmastey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jmmastey/subscriptions","organizations_url":"https://api.github.com/users/jmmastey/orgs","repos_url":"https://api.github.com/users/jmmastey/repos","events_url":"https://api.github.com/users/jmmastey/events{/privacy}","received_events_url":"https://api.github.com/users/jmmastey/received_events","type":"User","site_admin":false},"created_at":"2015-01-29T18:11:48Z","updated_at":"2015-01-29T18:11:48Z","body":"Hey @GeekOnCoffee, sorry for taking so long to respond. Long week. Some general and some specific thoughts / questions:\r\n\r\n0. Awesome! How was the training? What sort of group are you trying to run (e.g. focused like a bootcamp, evenings and/or weekends, whenever people get time?)\r\n1. There are a lot of features that might be useful, I just haven't built them yet. Tagging orgs outside the console is one of those. For the purposes of your group, I'm perfectly happy to just tag people in the console in the same way, or you're welcome to submit a pull. There are some open issues for visualizations around progress that would be good as well.\r\n2. For the most part, our workflow is dictated more than a little by our corporate hiring. It looks like the following:\r\n- New hires come in, usually one or two a week. They're batched up a bit into a \"cohort\".\r\n- Everyone -- regardless of role -- is asked to complete Engineering Baseline I as part of their onboarding process, so that we can have some consistency in our tech across the department. Other courses are at-will.\r\n- Each new hire forks the https://github.com/jmmastey/level_up_exercises/ repo and then starts into the exercises at their own pace. They meet as part of their cohort (usually two or three times per week) to code review as a group. This is one of the more valuable things we do.\r\n- When an assignment is completed, they submit a PR for it against the exercises repo. This is currently the easiest way for me to track them. For your group, depending on size, you could probably just do the same. You'd probably get some Enova folks reviewing your code ;) If you have your own mentors, you could fork the exercises repo and just submit against that repo.\r\n- Either way, a more experienced developer who has already done the given assignment will review it and provide notes. The learner is given as much feedback as possible, and we try to do it in under 24 hours. I'd like to get to 2 reviewers and < 12 hours in the future, as this feedback loop is _the most important thing_. The learner may need to resubmit multiple times depending on how much correction is necessary.\r\n\r\nRight now, if someone gets stuck, they often come ask one of the mentors in person, and each person has an experienced \"buddy\" as a new hire. Saturating learners in more-experienced mentors has been really successful, though sometimes matters of taste become a bit contentious.\r\n\r\nEither way, let me know how to help you facilitate your group. I'd like to get more non-Enova people onboard over time, and this would be a great way iron out wrinkles. Liberal use of the Feedback button is also quite appreciated. "}}