[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #21235 [Internal Services/Wiki]: Try dividing up services by vegas teams
#21235: Try dividing up services by vegas teams
----------------------------------------+-----------------
Reporter: arma | Owner:
Type: task | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Wiki | Version:
Severity: Normal | Keywords:
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
----------------------------------------+-----------------
https://trac.torproject.org/projects/tor/wiki/org/operations/Infrastructure
has a big list called "user facing services", and it's a jumble of things
that are more clearly in particular Vegas teams (help.tp.o,
exonerator.tp.o, etc) and things that are needed by multiple teams
(trac.tp.o), and things that don't really map to any team (jabber.tp.o).
We could learn something useful about our situation by trying to annotate
the services list by which Vegas team cares about each.
I can imagine that for the services that have multiple teams caring about
them, we could pick a primary team to lead the care-and-feeding of the
service.
I could also imagine making a new 'infrastructure' team or the like, for
the services that would otherwise be homeless. That's kind of a sad
outcome, because it could easily turn into a graveyard for ignored
services. But it might still be the best proposal so far.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21235>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs