Michael Ball
Michael Ball
Right now, only the owner of a collection can add/remove editors. given the way we designate '@snapcloud' as the owner, it'd be nice if we could manage editors, too. (Maybe...
We want some kind of curriculum / tutorial pages. How should we communicate these on the Snap! site? * Should they be "embeddable" within Snap!? * How can/should users/teachers contribute...
* Users should be able to login via SSO / Google / Clever, etc. * These identities shouldn't require and special information, just the perm ID to the external provider...
https://docs.google.com/document/d/1jC_yfp0Ic_wPqFrvVAE6mLA2Ee1o5VwMdWMxawsto40/edit#
These would be a nice addition. - uploadable profile pics - a bio - a location field These could sync to Discourse
The latest projects query timed out a bit recently. It's mostly pretty fast, but I bet we could tune things a bit. * Are there indexes that would help? Perhaps...
I think it's time to cleanup the handling of project notes: * We can remove `updatingnotes?=true` functionality from project lists. At projects sent to the cloud should come to cloud...
We definitely don't want allow iframes on: /login and /signup pages We definitely need iframes on: - /snap/snap.html - /embed - /versions and all the snap stuff there
The collection no longer shows the project due to filtering, but it would be good if it were removed from the DB
It'd be nice not to have to sign into the server and grep - and would hopefully make it easier for others to search logs. Related #65