{"action":"created","issue":{"url":"https://api.github.com/repos/edx/edx-platform/issues/6636","labels_url":"https://api.github.com/repos/edx/edx-platform/issues/6636/labels{/name}","comments_url":"https://api.github.com/repos/edx/edx-platform/issues/6636/comments","events_url":"https://api.github.com/repos/edx/edx-platform/issues/6636/events","html_url":"https://github.com/edx/edx-platform/pull/6636","id":54415426,"number":6636,"title":"WIP: MIT Feature - Personal Online Courses","user":{"login":"cewing","id":417109,"avatar_url":"https://avatars.githubusercontent.com/u/417109?v=3","gravatar_id":"","url":"https://api.github.com/users/cewing","html_url":"https://github.com/cewing","followers_url":"https://api.github.com/users/cewing/followers","following_url":"https://api.github.com/users/cewing/following{/other_user}","gists_url":"https://api.github.com/users/cewing/gists{/gist_id}","starred_url":"https://api.github.com/users/cewing/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cewing/subscriptions","organizations_url":"https://api.github.com/users/cewing/orgs","repos_url":"https://api.github.com/users/cewing/repos","events_url":"https://api.github.com/users/cewing/events{/privacy}","received_events_url":"https://api.github.com/users/cewing/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/edx/edx-platform/labels/waiting%20on%20author","name":"waiting on author","color":"0052cc"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":44,"created_at":"2015-01-15T05:59:04Z","updated_at":"2015-03-18T21:16:26Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/edx/edx-platform/pulls/6636","html_url":"https://github.com/edx/edx-platform/pull/6636","diff_url":"https://github.com/edx/edx-platform/pull/6636.diff","patch_url":"https://github.com/edx/edx-platform/pull/6636.patch"},"body":"This PR implements \"Personal Online Courses\" or POCs (working title). POCs are a simplified approach to SPOCs that allow for a course (or portions of a course) to be reused with a small groups of students. Course instructors assign a \"POC Coach\" who can create a POC, choose a subset of course modules for the POC (with start and end dates) and administer students. Importantly, POC Coaches cannot change the content and do not have the same permissions as course staff. \r\n\r\nPOCs were originally proposed [on the edx code list last year](https://groups.google.com/d/msg/edx-code/BF5_am0CmD4/90w-B2sun4gJ) and have been discussed with edX Product (including @explorerleslie ) and with edX Engineering ( @cpennington and @nedbat ). \r\n\r\nThis feature is intended to be used on edX.org. In particular, we are fielding requests to use this feature with 15.390.1x and 15.390.2x. This PR only affects LMS. \r\n\r\nFor manual testing, please view the [demo screencast](https://drive.google.com/file/d/0B9nbgzSIkR7mcTlXSkZqQTZwSnc/view?usp=sharing). The edX Demo course can be used for testing. \r\n\r\nWe are under constant demand for this feature. We would like to have it merged by the end of January. \r\n\r\nFor this WIP PR we have a couple of issues that we could use some help with:\r\n\r\n1. This PR has a dependency on PR https://github.com/edx/edx-platform/pull/5802 which provides the settings override feature that allows POC start and end dates to be applied just for POC students. \r\n\r\n2. Since POCs may omit some content from the MOOC, we need to override grading policy. We would like feedback from @ormsbee on our approach.\r\n\r\n3. We have introduced a new role -- POC Coach (working title) -- and a new course tab to go with it. @chrissrossi inquired about [the best approach to handling tab permissions on the mailing list](https://groups.google.com/d/msg/edx-code/08V3Ni7NxlI/as7cKCjXkoMJ) but we would like a confirmation that the approach suggested by @andyarmstrong is OK. We have not yet implemented this. \r\n\r\nAll the authors of this PR are covered under the edX-MIT agreement. "},"comment":{"url":"https://api.github.com/repos/edx/edx-platform/issues/comments/83181984","html_url":"https://github.com/edx/edx-platform/pull/6636#issuecomment-83181984","issue_url":"https://api.github.com/repos/edx/edx-platform/issues/6636","id":83181984,"user":{"login":"sarina","id":1985317,"avatar_url":"https://avatars.githubusercontent.com/u/1985317?v=3","gravatar_id":"","url":"https://api.github.com/users/sarina","html_url":"https://github.com/sarina","followers_url":"https://api.github.com/users/sarina/followers","following_url":"https://api.github.com/users/sarina/following{/other_user}","gists_url":"https://api.github.com/users/sarina/gists{/gist_id}","starred_url":"https://api.github.com/users/sarina/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sarina/subscriptions","organizations_url":"https://api.github.com/users/sarina/orgs","repos_url":"https://api.github.com/users/sarina/repos","events_url":"https://api.github.com/users/sarina/events{/privacy}","received_events_url":"https://api.github.com/users/sarina/received_events","type":"User","site_admin":false},"created_at":"2015-03-18T21:16:25Z","updated_at":"2015-03-18T21:16:25Z","body":"@pdpinch: 100% accessible code is a hard requirement from here on out for all features on edx.org. We will be requiring an accessibility review on all updates to user-facing functionality, and won't be merging code until it's accessible.\r\n\r\nThat said, I spoke with Beth and we agree that there is a bit of wiggle room here. Because this is a provisional feature and Mark is slammed with work, we will move forward with this without an immediate accessibility review. However, please plan for the following:\r\n\r\n  - In early April, Mark will provide a full accessibility review and recommendations for fixes.\r\n\r\n  - We will give you a month from that point to address his feedback. We will expect that you'll fix the accessibility issues that are brought up within that time period. We will provide review and assistance as needed.\r\n\r\n  - Moving forward, new features and functionalities to this and other features will need accessibility reviews. Heads up in advance of code landing (as much advance as is possible!) will help smooth this process and make sure all kinds of review (arch review, accessibility, etc) can happen in a timely fashion.\r\n\r\nWe'll work on updating our contributing documentation to include a note about accessibility and links to documentation on best practices.\r\n\r\nI hope that makes sense! Let me know if there's anything that I can clarify."}}