{"action":"created","issue":{"url":"https://api.github.com/repos/elmsln/elmsln/issues/475","labels_url":"https://api.github.com/repos/elmsln/elmsln/issues/475/labels{/name}","comments_url":"https://api.github.com/repos/elmsln/elmsln/issues/475/comments","events_url":"https://api.github.com/repos/elmsln/elmsln/issues/475/events","html_url":"https://github.com/elmsln/elmsln/issues/475","id":126576093,"number":475,"title":"Everything we need to fix to make this actually something usable, at an infrastructure level","user":{"login":"btopro","id":329735,"avatar_url":"https://avatars.githubusercontent.com/u/329735?v=3","gravatar_id":"","url":"https://api.github.com/users/btopro","html_url":"https://github.com/btopro","followers_url":"https://api.github.com/users/btopro/followers","following_url":"https://api.github.com/users/btopro/following{/other_user}","gists_url":"https://api.github.com/users/btopro/gists{/gist_id}","starred_url":"https://api.github.com/users/btopro/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/btopro/subscriptions","organizations_url":"https://api.github.com/users/btopro/orgs","repos_url":"https://api.github.com/users/btopro/repos","events_url":"https://api.github.com/users/btopro/events{/privacy}","received_events_url":"https://api.github.com/users/btopro/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/elmsln/elmsln/labels/documentation","name":"documentation","color":"fbca04"}],"state":"open","locked":false,"assignee":{"login":"btopro","id":329735,"avatar_url":"https://avatars.githubusercontent.com/u/329735?v=3","gravatar_id":"","url":"https://api.github.com/users/btopro","html_url":"https://github.com/btopro","followers_url":"https://api.github.com/users/btopro/followers","following_url":"https://api.github.com/users/btopro/following{/other_user}","gists_url":"https://api.github.com/users/btopro/gists{/gist_id}","starred_url":"https://api.github.com/users/btopro/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/btopro/subscriptions","organizations_url":"https://api.github.com/users/btopro/orgs","repos_url":"https://api.github.com/users/btopro/repos","events_url":"https://api.github.com/users/btopro/events{/privacy}","received_events_url":"https://api.github.com/users/btopro/received_events","type":"User","site_admin":false},"milestone":{"url":"https://api.github.com/repos/elmsln/elmsln/milestones/2","html_url":"https://github.com/elmsln/elmsln/milestones/Release%200.1.0","labels_url":"https://api.github.com/repos/elmsln/elmsln/milestones/2/labels","id":1082493,"number":2,"title":"Release 0.1.0","description":"This release is about unification of the user experience, cleaning up some infrastructure issues and preparing server components for the ability to accept upgrades.","creator":{"login":"btopro","id":329735,"avatar_url":"https://avatars.githubusercontent.com/u/329735?v=3","gravatar_id":"","url":"https://api.github.com/users/btopro","html_url":"https://github.com/btopro","followers_url":"https://api.github.com/users/btopro/followers","following_url":"https://api.github.com/users/btopro/following{/other_user}","gists_url":"https://api.github.com/users/btopro/gists{/gist_id}","starred_url":"https://api.github.com/users/btopro/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/btopro/subscriptions","organizations_url":"https://api.github.com/users/btopro/orgs","repos_url":"https://api.github.com/users/btopro/repos","events_url":"https://api.github.com/users/btopro/events{/privacy}","received_events_url":"https://api.github.com/users/btopro/received_events","type":"User","site_admin":false},"open_issues":6,"closed_issues":59,"state":"open","created_at":"2015-04-24T16:03:10Z","updated_at":"2016-01-14T15:32:06Z","due_on":null,"closed_at":null},"comments":2,"created_at":"2016-01-14T04:44:02Z","updated_at":"2016-01-14T21:38:30Z","closed_at":null,"body":"https://www.youtube.com/user/psuelms/videos\r\n\r\nneed to hide these some how, they have tons of views but I'll be starting to record a lot of tutorials soon so... .yeah.. want to do that some place else."},"comment":{"url":"https://api.github.com/repos/elmsln/elmsln/issues/comments/171788308","html_url":"https://github.com/elmsln/elmsln/issues/475#issuecomment-171788308","issue_url":"https://api.github.com/repos/elmsln/elmsln/issues/475","id":171788308,"user":{"login":"btopro","id":329735,"avatar_url":"https://avatars.githubusercontent.com/u/329735?v=3","gravatar_id":"","url":"https://api.github.com/users/btopro","html_url":"https://github.com/btopro","followers_url":"https://api.github.com/users/btopro/followers","following_url":"https://api.github.com/users/btopro/following{/other_user}","gists_url":"https://api.github.com/users/btopro/gists{/gist_id}","starred_url":"https://api.github.com/users/btopro/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/btopro/subscriptions","organizations_url":"https://api.github.com/users/btopro/orgs","repos_url":"https://api.github.com/users/btopro/repos","events_url":"https://api.github.com/users/btopro/events{/privacy}","received_events_url":"https://api.github.com/users/btopro/received_events","type":"User","site_admin":false},"created_at":"2016-01-14T21:38:30Z","updated_at":"2016-01-14T21:38:30Z","body":"I think this will get broken out into several issues referenced here so we can track and tackle each. First of all, thank you for asking all these questions. We're in a bit of bubble given the resources we have access to and our setup so there are a lot of assumptions around distributed user authentication that our systems make a non-issue (hence the frustration I'm sure when I just click stuff and it works).  So, i'm going to run through these one at a time.\r\n\r\n## People, authentication, how do you get data\r\nWe have Cosign (called Webaccess here) which allows for distributed authentication. If s site needs authentication (like every site does) it calls for webaccess. If webaccess is already aware of you being logged in via the Cosign (it's SSO for EVERYTHING web at PSU, login once somewhere, your in everywhere), then you have access to everything. It'll log you in on demand, broker the connection, there's probably .25 seconds involved generally so people don't notice (or care) when switching around.\r\n\r\nWhat the Vagrant setup does is attempt to use Drupal.org's SSO called Bakery (drupal.org/project/bakery). What I really need to do is sit down and get Bakery\r\n1. working out of the box every time in all instances no matter where you are\r\n2. have this be the case via the automated installer whether or not its via vagrant (this has a security implication bc of token generation so it's not as easy as the fake token creation in vagrant but possible for sure)\r\n\r\nThere's an issue recently about switching from CIS to People as the bakery authority. The People distribution at the time of this writing doesn't do much of anything other then hopefully install. It's planned functionality that will be worked on this semester to provide:\r\n1. an account for everyone with VERY lightweight fields associated to it for a global profile of sorts.\r\n2. the authority for telling other sites someone is logged in so that instead of throwing access denied it'll realize they are logged into people and log them in on-demand (much like webaccess does for PSU).\r\n\r\nCIS Provides logistics, we use these logistics to sync with a data source, in our case roster data from our legacy LMS. This is an access string which we pull which relates to sections. These sections then get propagated throughout elmsln and then systems ask for an updated roster nightly (or whenever) and people get synced up based on this data source. @rickhumphries is doing this via some other method, I think pulling from an XML list of users but he could speak to what they do. Wisconsin was manually adding people (obviously I don't recommend this).\r\n\r\nthe compliance system does have the ability to add accounts globally but it's on a per account basis and is intended for when people make access requests.\r\n\r\n## You're not dumb, it's still too complicated\r\nI'm sorry we're not there yet. I want to be but that's also why I built a grassroots army (https://btopro.wordpress.com/2013/09/25/products-are-ephemeral-movements-are-eternal/) for several years to prepare for the point that we are reaching now internally; a distributed series of deployments managed by a distributed group of people, taking input from faculty and students and directly improving the complex infrastructure that needed to be built in order to allow for organized chaos. We're as much a social movement (if not more) then a product, and heart and minds aren't so easily changed.\r\n\r\n## Admin menu settings\r\nThese settings are PER site and there is UX unification still to be done on certain settings to ensure the propagate so that (for example) if someone is added to the people site (which makes sense I totally agree with you) that they then are automatically added to all systems for that course.\r\n\r\n## Kicked out all the time\r\nThis is an issue that I have to resolve, it shouldn't be doing that (obviously) and it's because I'm trying to switch the bakery authority token from CIS to People. If you are comfortable with command line, drush can be used to repair this: `drush @elmsln upwd admin --password=admin --y`\r\n\r\nIf you haven't dug into drush or the command line of the system via `vagrant ssh` I highly recommend it. It's why nothing seemed to be happening for a few months because of investments there. `drush sa` will list all the systems and what you can access. There's also a command line version of elmsln for performing different tasks in automating the administration of the system, just type `leafy`.\r\n\r\n## where do students go / how do they know where to go\r\nInbox will unify their info across courses as it has calendar / messaging / notification aspects planned. As I said, planned. For right now we send them a direct link to their course space as part of setup and we use an LMS as a crutch. I wrote in a blog post 4 years ago that we'd systematically hollow out the LMS till there was nothing left and that's exactly what we're doing. Attacking one problem at a time until eventually there's no more need for an LMS as a crutch. It's why we support LTI launches.  Another potential solution would be to run Moodle or Canvas as an open source crutch that at least centralizes info, then LTI launch off for the parts of ELMSLN that you like and make more sense (we're always about options, even if that's not us, it's empowerment and choice).\r\n\r\nIn Rick's instance, students will be going to the CIS. that's their dashboard and he's added in a notifications / messaging system and dashboard that are pretty custom to what they are doing (along with the badges). We have the code for this and they are willing to share but it needs refactored and added to the right place in the larger ecosystem for sure.\r\n\r\n## Media and navigating away\r\nThese elements are integrated more fully via HAX but at the moment yes you need to navigate away from the content system in order to build out / upload more complex components to the media / interact systems. Interact makes some sense as assembling a timeline is a pretty complicated task of its own, media obviously will be more deeply integrated. After creating media / interactions there's a \"remix\" / \"share\" button in the top right (people with arrows pointing in a circle for now) which has all the possible short codes used to automatically represent what's being looked at. These work on content as well if you'd like to remix one piece of content into another (they can become circular so don't do this :)).\r\n\r\n## where is admin\r\nAdmin lives in the top right under the name of the course, these settings jump you to parts of the drupal admin side of things. Also if you having trouble finding the admin_menu then hit the tilda ` key and it'll pop-down the normal drupal way of doing anything. In mooc, studio, and others there are many features not turned on out of the box and we'll eventually build a \"drupal-ish\" admin menu side of things that basically enables and bulk changes functionality of the site and network of sites to match what someone of a faculty mindset would think (giving them the power / flexibility of drupal without the full admin side).\r\n\r\n## moving from one department to another\r\nThis would happen in CIS, though it has no real implication other then showing things in lists based on department or crafting custom queries to theme based on department (an idea used in a past life).\r\n\r\n#demo\r\nI've been trying to get through the beginning of the semester with some things here and there and then I plan on making a demo. Requirements of a demo (to me):\r\n1. fully functional single sign-on (obviously)\r\n2. fully functional experience for every user based on role (including admin, yes, full admin)\r\n3. The demo forcibly destroys and rebuilds itself either nightly or a few times a day. This ensures we can let people do whatever they want without whatever they want becoming a gaping security hole.\r\n4. hosted in EC2 outside the PSU network, again for security purposes, with no command line access (vagrant will be needed to restore this).\r\n\r\n## tutorial documentation\r\nhit zero 0.1.0 target issues or feel comfortable pushing things off to 0.2.0 (we're close). Push 0.1.0 out and start documenting both in video form as well as refreshing docs.elmsln.org and api.elmsln.org. Youtube will be flooded as soon as we hit 0.1.0 and after we have some additional staffing announcements (cause we're ramping up internally soon...).\r\n\r\n0.1.0 != every system in the network done, but the roadmap is solidifying and system stabilizing that we have clear ways of updating things after the fact; Rick's deployment and success with recent automated upgrades (as well as our internal ones to this affect) have done so as well."}}