#32893: Automating the remote training cycle ------------------------------------+---------------------- Reporter: ggus | Owner: ggus Type: defect | Status: assigned Priority: Medium | Milestone: Component: Community/Training | Version: Severity: Normal | Keywords: Actual Points: | Parent ID: Points: | Reviewer: Sponsor: | ------------------------------------+---------------------- For the last few months I've been organizing the remote trainings for Tor and centralizing everything via email has been limiting and confusing.
For the public launch, it would be important to scale this work. These are the main points: a) a way to receive new partnership requests that is not linked to my personal email b) easily follow the ongoing trainings c) have templates for each step of the partnership, for example, welcome and introduction, partnership agreement, training materials, scheduling online meeting, user feedback report d) have a history of who the organizations are and what was discussed Possible solution: 1. Create a new alias: training@tpo redirecting to a queue in RT, so we can track the requests by status 'New', 'Open', 'Closed'. 2. Create templates in different languages (ES, PT_BR, EN) in RT. 3. Use Gitlab kanban to have an overview. 4. For now, since this program is not for public participation, we could host the partnership agreement in Nextcloud. 5. An IRC private channel to receive notifications about new emails in training@tpo. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32893> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs