Opened 5 months ago

Last modified 5 months ago

#32893 assigned defect

Automating the remote training cycle

Reported by: ggus Owned by: ggus
Priority: Medium Milestone:
Component: Community/Training Version:
Severity: Normal Keywords:
Cc: pili, antonela, nah, ggus Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

TicketStatusOwnerSummaryComponent
#32981closedpiliNew RT queue 'training'Internal Services/Tor Sysadmin Team

Change History (1)

comment:1 Changed 5 months ago by anarcat

we had a meeting about this:

http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-01-16-19.03.html

the TL;DR: is:

  1. RT queue: #32981
  2. templates: can be done by RT admins (ie. you :)
  3. Kanban: "nice to have", not absolutely mandatory, but if so, maybe we could try https://github.com/nixcloud/rt-extension-kanban
  4. not really discussed
  5. "nice to have" as well, maybe should be avoided for now

We also considered using GitLab or Discourse, but for now we feel RT is a better fit.

Note: See TracTickets for help on using tickets.