brainstorm ideas for TPA in-person meeting
we'll have the chance to meet in person with a bunch of people, we should use it. we'll share "THE BAR" space with the ops team, but we can welcome other folks in our session as well.
Once settled, we should throw the results in https://nc.torproject.net/f/458264 (or the wiki? see also https://gitlab.torproject.org/tpo/team/-/wikis//2023-Tor-Meeting-Costa-Rica-Wiki#schedule)
I suggest we proceed by making one comment here per idea, and 
Activity
added Next label
assigned to @anarcat
docs work party!
ideas:
- cleanup the double-wiki mess (tpo/web/team#39 (closed))
- make sure all the web stuff is properly documented
- probe service admins to document their stuff properly
-
wiki work party!
- brainstorm ideas on the wiki replacement in general (https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service, #40909)
-
Service admins meetup
- Title: solving friction points between TPA and its users
- Facilitator: anarcat
- Who: service admins and TPA
- Duration: one hour
- Description: TPA manages dozens of services, but dozens more are managed by "service admins" who are at the mercy of the accesses and infrastructure created by TPA. dear Service admins, how are you doing? what do you need from TPA? how could we improve our services for your application? funky ideas and far-reaching dreams welcome
Brought back from Limerick, where this was canceled.
-
Global architecture diagram
- Title: drawing a global architecture diagram
- Facilitator: anarcat
- Who: TPA, possibly also service admins
- Duration: two hours
- Description: make a diagram of all of our services (not just TPA!), how they interact, and figure out if there are senseless things in there or things to improve. possibly make a completely new diagram from scratch in the second hour
Brought back from Limerick, where this was canceled.
-
Monitoring: Icinga/Nagios or Prometheus?
- Title: should we upgrade Icinga or replace it with Prometheus?
- Facilitator: anarcat
- Who: TPA, service admins
- Description: TPA-RFC-33: Monitoring stalled at the requirements drafting (#40755 (closed)), find ways to unlock this deadlock and decide what we're going to do with monitoring
Improving GitLab for development and collaboration
As we're relying more and more on GitLab for software development and various aspects of team collaboration, let's set aside some time with TPA and other teams to identify how we could improve GitLab and GitLab CI to meet the needs of the organization even better.
-
I added the service admin meetup and wiki work party items to the schedule, sorry @lavamind your comment came a bit late. :)
I really would like to attend this wiki party session but it's conflicting with another session I should attend.
So I'll give my small contribution here beforehand (sorry, it's in a terse braindump format):
- I'm using "Onion MkDocs" (https://rhatto.pages.torproject.net/onion-mkdocs/) at some projects. It could be used instead of the built-in wikis from GitLab. Or something similar. Also working with private repositories. Search is awesome, but wonder how it would behave with lots of content.
- Instead of one big wiki for the whole TPO, smaller per-context GitLab pages could be used.
- Maybe some MkDocs l10n plugin could be integrated with Weblate.
- Seems like the next hackweek will be about docs. We could try to convert some wikis and see how it goes (I'd like to migrate the Onion Support Wiki to a regular repository with GitLab Pages). Also, some projects like the Tor Policies could have it's own GitLab Pages.
EOF for now :)
Have a nice session!
mentioned in issue tpo/team#115 (moved)
mentioned in issue tpo/community/hackweek#13 (closed)