Opened 5 years ago

Closed 4 years ago

#9555 closed task (implemented)

create tbb-bugs@lists.torproject.org

Reported by: erinn Owned by:
Priority: Medium Milestone:
Component: Internal Services/Service - lists Version:
Severity: Keywords:
Cc: atagar Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

In talking with Mike about the current TBB/TorBrowser/Torbutton/gitian/et al bugs on trac, we decided the ideal path would be to assign all bugs to a team instead of individual people as the component owners. Our idea is to create an 'owner' named something like tbbteam and as its email, use a mailing list. This way we can squash all of these components into one and all interested people receive updates for them, instead of having to read everything that's on tor-bugs@ or missing things because they aren't the component owner.

(And just to be clear, this isn't meant to be a discussion list.)

Child Tickets

Change History (13)

comment:1 Changed 5 years ago by erinn

Summary: create torbrowser-bugs@lists.torproject.orgcreate tbb-bugs@lists.torproject.org

comment:2 Changed 5 years ago by weasel

Component: Tor Sysadmin TeamService - lists

comment:3 Changed 4 years ago by karsten

Cc: atagar added

Not crazy, though I'm worried that if we do this (and #9556), the ooni people will want their own -bugs and -commits mailing list, and then the pluggable transport people, and in the end we'll have a completely new layer that determines who receives which notifications. So, maybe a bit crazy.

What's wrong with subscribing to tor-bugs and tor-commits and filter email locally?

comment:4 Changed 4 years ago by erinn

Is there a reason it's bad for teams to have their own mailing lists? Almost every other free software project on earth does that and I have never really understood why Tor is so conservative in this regard. There are a lot of TBB developers nowadays as well as a lot of interested parties who might only want to see TBB-related stuff. I don't actually see the downside of other Tor teams getting similar mailing lists, and besides, these are only additions, not actual separations. Mail continues to go to bugs@ and commits@ as well.

There's nothing wrong with filtering email locally, it's just a pain and each new person has to do it. There isn't a good reason for all bundle bugs to be assigned to me anymore, and the tbb-bugs@ alias is more inclusive from a practical standpoint, but also makes it more clear that there is not a single person behind it, and we can collapse all related components into a single "owner".

comment:5 Changed 4 years ago by karsten

I don't feel strongly, but mostly wanted to dig out this almost forgotten ticket and move it forward. A few points though:

  • Creating two new mailing list for each sub group in Tor creates maintenance overhead. Adding new members, removing members, and deleting unused groups add to that overhead. You're right that the group would care for adding/removing members, but adding/removing lists would be on the list admins' plate.
  • New contributors will have to learn yet one more abstraction layer to understand how development works. How do they become a member of the ominous tbbteam group?
  • Those groups using this new abstraction layer will lose the meaning of "person X owns the ticket, so that person is responsible for moving it forward."

But again, I don't feel strongly. atagar, if you think creating this list and the one asked for in #9556 makes sense, please do that.

comment:6 Changed 4 years ago by atagar

atagar, if you think creating this list and the one asked for in #9556 makes sense, please do that.

Personally I'm not thrilled about the added maintenance overhead either. If we opt for this then erinn should have the admin password for the list (and take care of membership).

From irc it sounds like only weasel and phobos have the permission necessary to create lists.

comment:7 in reply to:  6 Changed 4 years ago by erinn

Replying to atagar:

Personally I'm not thrilled about the added maintenance overhead either. If we opt for this then erinn should have the admin password for the list (and take care of membership).

Oops, looks like I did not volunteer for admin for this list, but I did in #9556. I would be happy to admin both.

From irc it sounds like only weasel and phobos have the permission necessary to create lists.

Yes, and weasel said that the listmaster (I guess that is you? And maybe Karsten?) have to request it.

comment:8 Changed 4 years ago by atagar

Yes, and weasel said that the listmaster (I guess that is you? And maybe Karsten?) have to request it.

Hmmm. I think we need clarification on this bit. If you're the admin for this list then Karsten and I are not in the loop. There's several lists we do not manage nor have access to (donations@, for example) so requiring our approval for this seems a little odd.

comment:9 Changed 4 years ago by atagar

Component: Service - listsTor Sysadmin Team

New policy is that any tor person can request a list, so approved. :)

Erinn, please update this when you can with the rest of the answers to this.

comment:10 Changed 4 years ago by erinn

Component: Tor Sysadmin TeamService - lists

Information required:
What is the list name? - tbb-bugs
What is a one sentence description of the list? (see ​lists.torproject.org for examples) - Tor Browser Bundle related bugs
Who will be the list maintainer? - Erinn
Should the list be public (ie, anyone can subscribe) or closed? - Public
Should emails sent to the list be archived? - Yes
Should this be listed on the front page? - Yes

This will also be a "closed" list in the sense that it isn't for discussion, it's just for receiving mails from trac.

comment:11 Changed 4 years ago by atagar

Component: Service - listsTor Sysadmin Team

Spoke with Erinn, swapping the component was an accident.

comment:12 Changed 4 years ago by cypherpunks

Component: Tor Sysadmin TeamService - lists

comment:13 Changed 4 years ago by karsten

Resolution: implemented
Status: newclosed

List created and configured. Closing.

Note: See TracTickets for help on using tickets.