Conversation
|
@mike2151 I'm not sure if you wanted me to review this, but I took a quick look and I think something important to note is our current application / hackathon / user permissions hierarchy is very overcomplicated if we are building an open source tool that other hackathons can use. I think before something like this lands, we need to do some work to simplify those models. @ezwang It'd be great if you could help think about this also. Essentially I think we should change it so that the application questions + answers are hardcoded into the models rather than dynamically created in a database. The dynamic creation is great if we were creating a SaaS management tool like initially intended but will make life a lot harder to do stuff like this. Since we're deciding to do open source, we should re-architect the system a bit before adding features. Let me know if I can help with this, although I want to let you guys take charge of this to the extent you're able to. |
|
Perhaps we could have the common fields hardcoded (contact information, resume, GitHub, etc) and leave Hackathon directors with the option to add a few extra custom free response fields? This way we can preserve some of the flexibility while making the application easier to develop. |
|
@ezwang that seems reasonable to me - sorry that im just seeing this - my github notifications don't work very well |
3 participants
No description provided.