A week ago I asked Madhu about the typical workflow for PA (Program Admin). Madhu was so kind to explain the workflow for PA. I'll summarize the workflow and usage of admin dashboard by the PA. The followings are ordered things that should be done by PA to organize the GSoC program:
- Initialize the program settings such as program name, document page, or timeline of the program. These settings already provided by site.py and timeline.py views.
- Invite organizations to participate.
- Create the organization application survey. I believe this is related to what Madhu's did for survey with form builder. I can easily add the url inside the new admin dashboard to refer to the form builder.
- PA and her team discuss the organization selection internally.
- Accepted organization announced. I don't know yet if there's a view or task to accept organization.
- Student signup period. Students begin submitting proposals to organizations.
- PA can assign slot in this time or before the accepted projects announced. There's a view for slot assignment.
- PA can check the duplicate proposal. There's a view to trigger the duplicate proposals' task queue. This queue will iterate each proposals and filter the proposals by the same student that would be accepted by two or more organizations. The resolution was done manually by gathering a meeting.
- PA can check slot transfer by organization and accept/ignore the request of transfer by org admin. There's a view for this.
- After all organizations solve the duplication status and agree with the given slots. PA can trigger the accept_proposals' task queue. There's a view to trigger accept_proposals queue.
- PA creates survey for mentors and students. There's a survey builder committed by Madhu.
- PA freeze the program after the final term.
No comments:
Post a Comment