Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open up access #107

Open
2 of 5 tasks
Floppy opened this issue Apr 27, 2016 · 0 comments
Open
2 of 5 tasks

Open up access #107

Floppy opened this issue Apr 27, 2016 · 0 comments

Comments

@Floppy
Copy link
Contributor

Floppy commented Apr 27, 2016

@rnorris will confirm, but my understanding from the meeting the other week is that we can open up this demo now. We should:

  • Remove the root password protection
  • Apply the password protection to the signals area only (because full signal data is confusing for non-experts and requires a lot of explanation
  • Make a signals page that shows a static example of the UI, or shows one easily-understandable signal, perhaps.
  • Link the full signals interface from that simple page
  • Add many caveats and explanation that this is NOT live data, from ONE train, and is incomplete and nothing should be read into it. Proof of concept only.

@rnorris can you confirm that that all makes sense, and when we can go about doing it? We should obviously break up this ticket into smaller ones for the actual work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant