Unverified Commit f6463445 authored by anarcat's avatar anarcat
Browse files

markdown linting 

Those are mostly tests to see if we can get something that satisfies
markdownlint.
parent 125f2541

policy/template.md

+5 −2
Original line number Diff line number Diff line
@@ -2,6 +2,8 @@ 
title: TPA-RFC-X: RFC template

---



[[_TOC_]]



Summary: this template describes the basic field a TPA-RFC policy

should have. Refer to [policy/tpa-rfc-1-policy](policy/tpa-rfc-1-policy) for the actual policy requirements.
@@ -11,7 +13,9 @@ should have. Refer to [policy/tpa-rfc-1-policy](policy/tpa-rfc-1-policy) for the 


## Scope



## ...

## Affected users



## (etc)



# Examples
@@ -25,7 +29,6 @@ Counter examples: 


# Deadline





# Status



This proposal is currently in the `draft` state.

service/lists.md

+111 −47
Original line number Diff line number Diff line 
[[_TOC_]]



Our mailinglist server, lists.torproject.org, is running an instance of mailman.

Our mailing list server, lists.torproject.org, is running an instance

of mailman.



The listmaster team is responsible for configurating all lists as required.

They make decisions about which lists to create and which to retire, who should

have owner or moderator access to existing lists, if lists are private,

restricted, or public, and many other aspects of running mailing lists.

The "listmaster" team is responsible for configuring all lists as

required.  They make decisions about which lists to create and which

to retire, who should have owner or moderator access to existing

lists, if lists are private, restricted, or public, and many other

aspects of running mailing lists.



If you want to request a new list or propose a change to existing lists please

file a ticket in the `Service - lists` component.  If listmaster approves, they

will coordinate with the admin team to have the list added and then configure

it as needed. Don't forget to update the [list of mailing

lists](#list-of-mailing-lists) (below)

upon changes.

If you want to request a new list or propose a change to existing

lists please [file a ticket][].  If "listmaster" approves, they will

coordinate with the admin team to have the list added and then

configure it as needed. Don't forget to update the [list of mailing

lists](#list-of-mailing-lists) (below) upon changes.



# How-to



## create a list



A list can be created by running `newlist` on the mailing list server (currently `eugeni`):

A list can be created by running `newlist` on the mailing list server

(currently `eugeni`):



```

ssh eugeni.torproject.org sudo -u list newlist

```



If you do not have root access, proceed with the mailman admin password on the [list creation form](https://lists.torproject.org/cgi-bin/mailman/create), which might or might not work.

If you do not have root access, proceed with the mailman admin

password on the [list creation form](https://lists.torproject.org/cgi-bin/mailman/create), which might or might not

work.



Mailman creates the list name with an upper case letter. Usually people like all lower-case more. So log in to the newly created list at https://lists.torproject.org/ and change the list name and the subject line to lower case.

Mailman creates the list name with an upper case letter. Usually

people like all lower-case more. So log in to the newly created list

at <https://lists.torproject.org/> and change the list name and the

subject line to lower case.



If people want to have specific settings (no archive, no public listing, etc.), can you set them also at this stage.

If people want to have specific settings (no archive, no public

listing, etc.), can you set them also at this stage.



TPA should store the new list password in their password manager.



Don't forget to update the  [list of mailing

lists](#list-of-mailing-lists) (below) upon changes and close the trac ticket.

Don't forget to update the [list of mailing lists](#list-of-mailing-lists) (below) upon

changes and close the trac ticket.



## Remove a list



To remove a list, use the `rmlist` command on eugeni:

To remove a list, use the `rmlist` command on `eugeni`:



```

ssh eugeni.torproject.org sudo -u list rmlist LISTNAME

```



By default, archives are kept. If that's not wanted, use the `-a` flag.

By default, archives are kept. If that's not wanted, use the `-a`

flag.



Don't forget to update the [list of mailing lists](./doc/emailLists) upon changes.



## What are our most important lists?

New to Tor? If so then welcome! Our most important lists are as follows...



 * [tor-talk@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk) - High traffic general discussion list, useful for general user questions and discussion. The list's lack of moderation is something we're growing to view as a problem, and as such might not be the best place at present.

 * [tor-dev@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev) - Discussion list for developers, researchers, and other technical discussions.

New to Tor? If so then welcome! Our most important lists are as

follows...



 * [tor-talk@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk) - High traffic general discussion list, useful for

   general user questions and discussion. The list's lack of

   moderation is something we're growing to view as a problem, and as

   such might not be the best place at present.

 * [tor-dev@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev) - Discussion list for developers, researchers, and

   other technical discussions.

 * [tor-relays@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays) - Discussion list for relay operators.

 * [tor-project@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project) - Discussion list for tor contributors. Only active and past tor contributors can post to this list.

 * [tor-project@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project) - Discussion list for tor contributors. Only

   active and past tor contributors can post to this list.



## How do I get permission to post to tor-project@

Just ask. Anyone is allowed to watch, but posting is restricted to those that actively want to make Tor better. As long as you're willing to keep your posts constructive just [contact Damian](https://www.atagar.com/contact/).



Note that unlike many of our lists this one is pretty actively moderated, so unconstructive comments may lose you posting permissions. Sorry about that, but this is one list we're striving to keep the noise down on. ;)

Just ask. Anyone is allowed to watch, but posting is restricted to

those that actively want to make Tor better. As long as you're willing

to keep your posts constructive just [contact Damian](https://www.atagar.com/contact/).



Note that unlike many of our lists this one is pretty actively

moderated, so unconstructive comments may lose you posting

permissions. Sorry about that, but this is one list we're striving to

keep the noise down on. ;)



## How do I ask for a new mailing list?

For general information, look up [lists.torproject.org service](./org/operations/Infrastructure/lists.torproject.org) description.



Creating a new list is easy, but please only request one if you have a good reason. Unused lists will periodically be removed to cut down on bloat. With that out of the way, to request a new list simply [/newticket file a ticket] to the **"Internal services/Service - lists"** component with the following...

For general information, look up [lists.torproject.org service](./org/operations/Infrastructure/lists.torproject.org)

description.



Creating a new list is easy, but please only request one if you have a

good reason. Unused lists will periodically be removed to cut down on

bloat. With that out of the way, to request a new list simply [file a

ticket][] with the following...



[file a ticket]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/new



 * What is the list name?

 * What is the email address of the list maintainer? This person will be given the list's Mailman administrator password, be notified of bounces, and emails to the list owner. If this is a closed list then they'll be responsible for maintaining the membership.

 * What is a one sentence description of the list? (see  [lists.torproject.org](https://lists.torproject.org/cgi-bin/mailman/listinfo) for examples)

 * What is the email address of the list maintainer? This person will

   be given the list's Mailman administrator password, be notified of

   bounces, and emails to the list owner. If this is a closed list

   then they'll be responsible for maintaining the membership.

 * What is a one sentence description of the list? (see

   [lists.torproject.org](https://lists.torproject.org/cgi-bin/mailman/listinfo) for examples)



Lists default to being public and archived. If you would prefer something else then you'll need to change its configuration in Mailman.

Lists default to being public and archived. If you would prefer

something else then you'll need to change its configuration in

Mailman.



Creating lists involves at least two people, so please be patient while your list is being created.  Be sure to regularly check the ticket you created for questions by list admins.

Creating lists involves at least two people, so please be patient

while your list is being created.  Be sure to regularly check the

ticket you created for questions by list admins.



Members of tor-internal@ do not require approval for their lists. Non-members will need signoff of Damian or qbi.

Members of tor-internal@ do not require approval for their

lists. Non-members will need sign-off of Damian or qbi.



## Why do we have internal lists?



In additional to our [public email lists](https://www.torproject.org/docs/documentation.html.en#MailingLists) Tor maintains a handful of communication channels reserved for core contributors. This is not a secret inner cabal, but rather community members (both paid and unpaid) who have been long-time contributors with the project. (See our [Core Contributor Guidelines](https://gitweb.torproject.org/community/policies.git/tree/membership.txt).)

In additional to our [public email lists](https://www.torproject.org/docs/documentation.html.en#MailingLists) Tor maintains a handful

of communication channels reserved for core contributors. This is not

a secret inner cabal, but rather community members (both paid and

unpaid) who have been long-time contributors with the project. (See

our [Core Contributor Guidelines](https://gitweb.torproject.org/community/policies.git/tree/membership.txt).)



Why do we have these internal discussions? Funding proposals, trip reports, and other things sometimes include details that shouldn't be public. In general though we strongly encourage discussions to happen in public instead.

Why do we have these internal discussions? Funding proposals, trip

reports, and other things sometimes include details that shouldn't be

public. In general though we strongly encourage discussions to happen

in public instead.



Note that this is a living document. Policies are not set in stone, and might change if we find something better.

Note that this is a living document. Policies are not set in stone,

and might change if we find something better.



## How do I get added to internal lists?



Internal communication channels are open only to core contributors. For information on becoming a core contributor, see the [Core Contributor Guidelines](https://gitweb.torproject.org/community/policies.git/tree/membership.txt).

Internal communication channels are open only to core

contributors. For information on becoming a core contributor, see the

[Core Contributor Guidelines](https://gitweb.torproject.org/community/policies.git/tree/membership.txt).



# Reference







## List of mailing lists



### Discussion Lists



The following are lists with subscriber generated threads.



| **List**                     | **Maintainer**                              | **Type** | **Description**                                                                                              |
@@ -115,6 +163,7 @@ The following are lists with subscriber generated threads. 
| [global-south](https://lists.torproject.org/cgi-bin/mailman/listinfo/global-south)            | sukhbir, arma, qbi, nickm, gus              | Public   | Tor in the Global South                                                                                      |



### Notification Lists



The following lists are generally read-only for their subscribers. Traffic is either notifications on specific topics or auto-generated.



| **List**                    | **Maintainer**           | **Type** | **Description**                                             |
@@ -136,6 +185,7 @@ The following lists are generally read-only for their subscribers. Traffic is ei 
| tor-svninternal             | arma, qbi, nickm         | Private  | Commits to the internal SVN.                                |



### Administrative Lists



The following are private lists with a narrowly defined purpose. Most have a very small membership.



| **List**                 | **Maintainer**         | **Type** | **Description**                                                                                                                                                                                                                                                  |
@@ -158,6 +208,7 @@ The following are private lists with a narrowly defined purpose. Most have a ver 
| [wtf](https://lists.torproject.org/cgi-bin/mailman/listinfo/wtf)                 | nickm, sysrqb, qbi     | Private  | a wise tech forum for warm tech fuzzies                                                                                                                                                                                                                          |



### Team Lists



Lists related to subteams within Tor.



| **List**                  | **Maintainer**             | **Type** | **Description**                           |
@@ -179,16 +230,29 @@ Lists related to subteams within Tor. 


### Internal Lists



We have three email lists ([tor-team@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-team), [tor-internal@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-internal), and [bad-relays@](https://lists.torproject.org/cgi-bin/mailman/listinfo/bad-relays)), and a private IRC channel on OFTC.

We have three email lists ([tor-team@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-team), [tor-internal@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-internal), and

[bad-relays@](https://lists.torproject.org/cgi-bin/mailman/listinfo/bad-relays)), and a private IRC channel on OFTC.



 * [tor-team@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-team) is an invite-only list that is reachable by the outside world. As such it both used for email CCs, and receives quite a bit of spam.

 * [tor-internal@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-internal) is an invite-only list that is not reachable by the outside world. Some individuals that are especially adverse to spam only subscribe to this one.

 * [bad-relays@](https://lists.torproject.org/cgi-bin/mailman/listinfo/bad-relays) is an invite-only list that is reachable by the outside world. It is also used for email CCs.

 * Our internal IRC channel is used for unofficial real time internal communication.

 * [tor-team@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-team) is an invite-only list that is reachable by the

   outside world. As such it both used for email CCs, and receives

   quite a bit of spam.

 * [tor-internal@](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-internal) is an invite-only list that is not reachable by

   the outside world. Some individuals that are especially adverse to

   spam only subscribe to this one.

 * [bad-relays@](https://lists.torproject.org/cgi-bin/mailman/listinfo/bad-relays) is an invite-only list that is reachable by the

   outside world. It is also used for email CCs.

 * Our internal IRC channel is used for unofficial real time internal

   communication.



### Encrypted Mailing Lists

We have mailing lists handled by [Schleuder](https://schleuder.nadir.org/) that we use within different teams.



 * tor-security@ is an encrypted list. See its entry under "Administrative Lists".

 * network-team-security@ is for any security issues related to "tor" and is an invite-only list used by the [Network Team](./org/teams/NetworkTeam). Only subscribers can post.

 * tor-community-council@ is used by [Community Council](./org/CommunityCouncil) members. Anyone can use it to email the community council.
 
We have mailing lists handled by [Schleuder](https://schleuder.nadir.org/) that we use within

different teams.



 * tor-security@ is an encrypted list. See its entry under

   "Administrative Lists".

 * network-team-security@ is for any security issues related to "tor"

   and is an invite-only list used by the [Network Team](./org/teams/NetworkTeam). Only

   subscribers can post.

 * tor-community-council@ is used by [Community Council](./org/CommunityCouncil)

   members. Anyone can use it to email the community council.

service/nextcloud.md

+212 −69

File changed.

Preview size limit exceeded, changes collapsed.