Opened 5 years ago

Closed 5 years ago

#13991 closed task (fixed)

Create new hidserv-stats@ mailing list

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

Description

Paul asks for a new mailing list to discuss hidden-service related statistics with researchers, including: "how best to gather them, existing results, how to protect privacy in gathering or reporting statistics, how potential changes to HS design might affect statistics or the gathering of them, etc."

If I understand Paul correctly, the idea of discussing these things on a private mailing list rather than on tor-dev@ is that researchers may be more willing to disclose speculative or preliminary work if it is not public. Paul is considering to make the archives public after six months. This new list is also supposed to be temporary until we have reasonable hidden-service statistics in Tor, if I understand correctly. All discussions of actual proposals and code patches will still happen on tor-dev@, of course. This list is just for the research part preceding design and code. Paul can probably elaborate on the decisions made here if needed.

Information required:

What is the list name? - hidserv-stats
What is a one sentence description of the list? (see ​lists.torproject.org for examples) - discussion regarding research on hidden-service related statistics
Who will be the list maintainer? - Paul
Should the list be public (ie, anyone can subscribe) or closed? - Closed
Should emails sent to the list be archived? - Yes, but privately for now
Should this be listed on the front page? - Yes

I'll create a sysadmin ticket for creating this list in 24 hours from now, unless somebody objects.

Child Tickets

Change History (2)

comment:1 Changed 5 years ago by karsten

Created #13999 for the sysadmin part.

comment:2 Changed 5 years ago by karsten

Resolution: fixed
Status: newclosed

List is created and configured. Closing.

Note: See TracTickets for help on using tickets.