Michael Ball
Michael Ball
This is potentially front-end + back-end problem. I'm not sure what's the best solution, but I don't like what we currently do. Let's say I have my own project called...
/cc @brianharvey What usernames should we prevent people from taking? I'm not thinking of dirty words, but things that are impersonations or stuff like that. "admin", "snapcloud", "system" -- those...
sha1 is the lapis default which is not a secure hashing function. This affects session cookie encryption so setting the option to sha256 would be preferred. Note: Doing this will...
I think saving a project opened from another user should trigger a remix even if you don't click that button. - we should always send down the projectId as at...
Lapis supports defining the relationships models have to each other. I.e. for User we can have `user:get_projects()` - [ ] User has many Projects - [ ] User has many...
Much further down the list, but an interesting problem. Where possible, we should preserve the naming history of objects (users, projects, collection, etc.). GitHub does this to **enormous** effect, where...
Users should be able to leave comments on a project, and should be able to reply to a comment. Suggesting the following schema: Comments Table * user_id * project_id *...
To address user support needs, and potentially other requests. This script should take 2 usernames and copy projects from 1 username to the other.
A meta issue to track and note what needs to be done to support running the app on a Cloud Foundry Platform, like SAP. - [ ] running the app...
Sigh, this one may be annoying, but it's worth exploring as we haven't yet found a long term partner for the cloud. I'll look into this once things settle down.