-
Notifications
You must be signed in to change notification settings - Fork 140
Application Form: Create separate view of submitted applications for mentors #581
Comments
Depends on Issue #579 |
@klappradla is this something you might be interested in working on maybe? (and the related issue #579) |
Yeah, seems fine. I did not dive into details yet, but I'll just assign them to me then. What in terms of deadlines does |
@klappradla high-priority means that these must absolutely be fixed by the time we open up the applications, the other ones are more like “small improvements” than anything, I think. Regarding deadlines: I've left us a bit of breathing room there. The plan was to start testing the app on the weekend already (so ideally, with most of the bigger changes/ |
We also talked about this feature in the call last week, and I wanted to expand a bit on the issue: The idea is to have a overview with a list of all the applications that have submitted for the project (as either 1st or 2nd choice). Clicking on a single application (e.g. team name) will take the mentor to the detailed view of the application, where the above-mentioned answers can be found. (similar to the projects overview+detailed view). This show view should include:
Alternatively, picks/favs should be available from the dashboard/index, not sure what makes the most sense, UI/UX-wise! |
Wow, thanx a million for the explanation @alicetragedy 🙏 - just perfect! |
Quick question @alicetragedy: should the maintainers know whether their project is the team's first or second choice? |
That's a very good question, and I'm not sure if I have an answer for this. On the one hand, I think the maintainers would be interested in knowing whether their project is in a team's first or second choice; on the other hand, I think this would probably influence the maintainer's “favourite” teams maybe? |
quick (unrelated) note @klappradla: I think @carpodaster is planning to take a shot at #364, so there might be some overlap in your work — maybe you can talk to each other to make sure you don't do the same work twice. :) |
@alicetragedy ah, good call. I was planning to create another separate view/action for this, not including the fav in any existing templates. It used to be in |
Hm, @alicetragedy I'm not 100% sure if I understand your answer 😂 - so you mean "yes they should know wether their project was 1st or 2nd choice"? And @carpodaster I saw you're working on this stuff and did not touch anything related to this yet. I threw in a |
@klappradla yes, they should know. I think that's the best way to go about it 👍 |
@klappradla new namespace sounds good! 👍 Take your time. I haven't written any code yet and probably won't have time for it before Tuesday. |
Well, I'm for now skipping anything mentor-fav related and just add an empty column in the views, so we can then add the respective data there @carpodaster. |
Just to keep you updates: I'm not sure if I find the time to continue on this before Tuesday, but I pushed my current WIP state to this branch (in case someone wants to have a look / try out things) |
Since this year project maintainers will be more involved in the application process, they should be given access to applications submitted for their project (1st and 2nd choice applications). The best way to do so, rather than messing too much with giving access to application drafts, is to create a separate view for mentors to access (for submitted applications only).
The separate view for mentors should only include answers to the following questions:
The text was updated successfully, but these errors were encountered: