Feature #7698

Create a place to gather information about the different mailing lists, and their scope and policy

Added by sajolida 2014-07-31 15:13:28 . Updated 2016-03-21 17:12:25 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_2.3
Start date:
2014-07-31
Due date:
% Done:

60%

Feature Branch:
web/7698-contacts
Type of work:
Website
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

lists: -project, -news, -ux, -dev, -testers, -l10n, -press, -fundraising, -sysadmins, -security.

If I forgot any, add it to the list :)

When this ticket is closed, Feature #7937 can be closed too, as it’s done here.

Subtasks

Related issues

Related to Tails - Bug #7574: Document the tails-press mailing list Resolved 2014-07-11
Related to Tails - Bug #7535: Add new Tails UX mailing-list information to the documentation Resolved 2014-07-09
Related to Tails - Feature #7536: Document tails-project@ Rejected 2014-07-09
Related to Tails - Feature #7697: Create list and repo for tails-fundraising Resolved 2014-07-31
Related to Tails - Feature #7785: Simplified lists subscribing forms Resolved 2014-08-15
Related to Tails - Bug #11423: Merge /support/chat and /contribute/chat into /about/contact Confirmed 2016-05-16
Related to Tails - Bug #11424: Make /about/contact translatable Resolved 2016-05-16
Has duplicate Tails - Feature #7573: Create a "contact" web page Duplicate
Has duplicate Tails - Feature #7937: Advertise security contact information Duplicate 2014-09-22
Has duplicate Tails - Bug #10867: 'Talk to us' section on website needs link to tails-project Duplicate 2016-01-07
Blocked by Tails - Bug #9112: Complete our page listing OpenPGP keys Resolved 2015-03-26

History

#1 Updated by sajolida 2014-07-31 15:13:41

  • related to Bug #7574: Document the tails-press mailing list added

#2 Updated by sajolida 2014-07-31 15:13:47

  • related to Bug #7535: Add new Tails UX mailing-list information to the documentation added

#3 Updated by BitingBird 2014-08-07 11:29:06

#4 Updated by BitingBird 2014-08-08 17:23:24

  • related to Feature #7697: Create list and repo for tails-fundraising added

#5 Updated by BitingBird 2014-08-15 10:38:14

  • related to Feature #7785: Simplified lists subscribing forms added

#6 Updated by BitingBird 2014-08-15 10:46:18

  • Description updated

listing the lists

#7 Updated by sajolida 2014-08-20 15:17:12

#8 Updated by sajolida 2014-08-20 15:17:44

#9 Updated by sajolida 2014-08-20 15:17:53

#10 Updated by intrigeri 2014-09-22 12:30:17

  • Description updated

#11 Updated by intrigeri 2014-09-22 12:30:40

  • related to deleted (Feature #7573: Create a "contact" web page)

#12 Updated by intrigeri 2014-09-22 12:30:54

#13 Updated by intrigeri 2014-09-22 12:33:08

  • related to Feature #7937: Advertise security contact information added

#14 Updated by intrigeri 2014-09-22 12:33:39

  • Description updated

#15 Updated by BitingBird 2014-09-25 14:40:02

Maybe even add pointers to tor, debian, GNOME lists ? (since we sometimes refers users to those, asking them to report upstream).

#16 Updated by BitingBird 2015-01-31 11:02:34

It seems to me that the best place to put this page would be in doc/about, with a link from the about page.

It should also include the irc info (like in the “contact us” footer we use in lots of pages).

If each list has a shortcut to subscribe like in support/tails-support, that’s even better.

#17 Updated by sajolida 2015-02-05 21:26:42

  • Assignee deleted (sajolida)

#18 Updated by sajolida 2015-02-21 09:32:03

I gave up on this a while ago because I’m too busy, but that could be something for BitingBird, no?

#19 Updated by BitingBird 2015-02-21 18:31:10

  • Assignee set to BitingBird
  • Target version set to Tails_1.3.2

Yep, I’ll take it.

#20 Updated by BitingBird 2015-03-14 17:10:04

  • Feature Branch set to bitingbird:about/7698-contacts

#21 Updated by BitingBird 2015-03-14 18:22:09

  • Status changed from Confirmed to In Progress
  • Assignee changed from BitingBird to sajolida
  • QA Check set to Ready for QA

New page! It is quite long, so I kept the desciption of each mailing-list minimal. The footer with contact infos could probably be changed to only link to this page.

#22 Updated by BitingBird 2015-03-14 18:49:01

The first commits are about the contact page, the last ones are cleaning of the footer.

#23 Updated by sajolida 2015-03-15 16:45:33

  • Assignee changed from sajolida to BitingBird
  • QA Check changed from Ready for QA to Info Needed

Thanks for working on this.

Here are my first two remarks.

How would this interact with:

  • /support/tails-support
  • /master/support/talk

I’m not particularly convinced by having this being our “Contact” page as the mailing list in it are as much about “contacting” than about “contributing”. Still it’s hard to draw a clear line between what’s contributing and what’s being a user (for example in the case of tails-support and tails-testers).

How could we make this better? Should we call it “mailing lists” or “communication channels”? Should we have more structure in there? At least add a [[!toc]].

Should we point all occurences of, for example, tails-dev to this page?

Should we propose buttons to download the OpenPGP of each schleuder list in there? Would this duplicate too much /doc/about/openpgp_keys?

#24 Updated by BitingBird 2015-03-15 17:01:30

sajolida wrote:
> How would this interact with:
>
> * /support/tails-support
> * /master/support/talk

I think those pages should stay, I didn’t touch them and linked to them.

> I’m not particularly convinced by having this being our “Contact” page as the mailing list in it are as much about “contacting” than about “contributing”. Still it’s hard to draw a clear line between what’s contributing and what’s being a user (for example in the case of tails-support and tails-testers).

I think contact is generic and works for people wanting to ask as well as for people wanting to contribute, but we can rename.
>
> How could we make this better? Should we call it “mailing lists” or “communication channels”? Should we have more structure in there? At least add a [[!toc]].

It also lists email addresses and irc chats, so “mailing lists” definitly doesn’t work. I don’t see how “communication channels” is better than “contact”, but I don’t mind if you want to rename.

We can of course add !toc. I can add a commit for that if you want.
>
> Should we point all occurences of, for example, tails-dev to this page?

I think so. The support pages are special, because users might be confused and need very detailed explanations, but I don’t think each mailing-list needs an explanation page.
>
> Should we propose buttons to download the OpenPGP of each schleuder list in there? Would this duplicate too much /doc/about/openpgp_keys?

I think /doc/about/openpgp_keys should be completed instead, and links to it added in the relevant places.

#25 Updated by BitingBird 2015-03-15 17:29:08

  • Assignee changed from BitingBird to sajolida

#26 Updated by BitingBird 2015-04-01 12:40:14

  • Target version changed from Tails_1.3.2 to Tails_1.4

#27 Updated by BitingBird 2015-04-10 19:30:24

  • Description updated

#28 Updated by BitingBird 2015-04-11 14:40:57

  • related to Bug #9112: Complete our page listing OpenPGP keys added

#29 Updated by BitingBird 2015-04-11 14:52:54

Added a few commits to improve this page (including the !toc, some links to contribute/how sections, and a sentence to describe some lists better, and being more clear each time that they are “public mailing-lists”).

#30 Updated by BitingBird 2015-04-11 15:55:34

  • related to deleted (Bug #9112: Complete our page listing OpenPGP keys)

#31 Updated by BitingBird 2015-04-11 15:55:45

  • blocked by Bug #9112: Complete our page listing OpenPGP keys added

#32 Updated by BitingBird 2015-04-25 06:20:58

replace -fundraising by -accounting

#33 Updated by sajolida 2015-04-27 02:55:02

  • QA Check changed from Info Needed to Ready for QA

I bet this hasn’t been set to Ready for QA after note #25, so I’ll have a look.

#34 Updated by BitingBird 2015-04-27 04:43:47

  • QA Check changed from Ready for QA to Info Needed

I answered some of your remarks in #24 (I’d love some feedback, because we might have to agree on what we want before being able to agree on the implementation :)), and I still have a few details to correct (replace -fundraising by -accounting, check the links to the GPG keys since the work on this is in Bug #9112). I’ll try to finish Bug #9112 and unblock this one after :)

#35 Updated by BitingBird 2015-05-04 10:15:24

Replaced fundraising by accounting, corrected the links to the keys and Bug #9112 is ready for QA.

#36 Updated by BitingBird 2015-05-08 23:28:37

Bug #9112 is merged, youhou :)

#37 Updated by sajolida 2015-05-12 13:48:27

  • Assignee changed from sajolida to BitingBird
  • Target version deleted (Tails_1.4)
  • QA Check changed from Info Needed to Dev Needed
  • Feature Branch changed from bitingbird:about/7698-contacts to about/7698-contacts

Thanks for working on this. I’ve pushed some improvements on about/7698-contacts. Make sure to fetch them.

I think there are many small things that need to be improved:

  • I propose to link to the public archives of those lists. That’s a useful information and it definitely fits there.
  • Shall we clarify in which language can people write to those email addresses?
  • I improved the link to an OpenPGP key with commit:17eee73. If you like it, please do the same for the other ones.
  • Some links to OpenPGP keys are broken.
  • I think we should separate the description of #tails and #tails-dev like we do for all the rest.
  • Shall we link from other parts of the website to this same page. In many places we refer to those lists without explaining to people how to subscribe or consult them. Maybe we should point more systematically to this new page.
  • The information about tails-l10n is duplicated with contribute/how/translate#follow-up. Can you propose something to fix that?

#38 Updated by BitingBird 2015-05-20 11:36:56

I added the link to the archives, and the notice about languages (in two separate commits :)).

I saw your changes and I like them, but they were not pulled in my repo when I pulled, so I won’t touch the rest until I have fixed my git, too much chances for conflicts.

I don’t understand “I think we should separate the description of #tails and #tails-dev like we do for all the rest.” They are separated from each other, and I don’t see from what else you’d like to separate them.

#39 Updated by BitingBird 2015-05-20 11:37:58

  • % Done changed from 0 to 40

#40 Updated by sajolida 2015-05-20 15:23:08

I add a quick look and it looks good :)

Maybe I’ll try to find something more proper than “bad English” and “easy Italian” but I’m not sure what we can do to improve on that and otherwise it’s fine with me.

And be careful “bellow” → “below”.

Tell me when you think it’s ready for a full review.

#41 Updated by BitingBird 2015-07-04 10:25:41

  • Target version set to Tails_1.5

#42 Updated by BitingBird 2015-07-05 03:55:13

  • QA Check changed from Dev Needed to Ready for QA

Added a link to tails-support archives, corrected the spelling and added some details.

I don’t see the broken keys links, I think the openPGP page was not merged yet in that branch and I don’t manage to merge your changes in it…

I think it’s ready for QA, I’ll try to find help with git before assigning to you :)

#43 Updated by BitingBird 2015-07-05 04:36:21

Well… I finally managed to pull, but you moved all the page around, so it’s impossible to merge…

#44 Updated by BitingBird 2015-08-05 07:26:20

  • Priority changed from Normal to Elevated
  • Target version changed from Tails_1.5 to Tails_1.6

Priority elevated because I really want to see this live soon :)

#45 Updated by BitingBird 2015-08-05 08:25:50

  • related to deleted (Feature #7937: Advertise security contact information)

#46 Updated by BitingBird 2015-08-05 08:25:54

  • has duplicate Feature #7937: Advertise security contact information added

#47 Updated by intrigeri 2015-08-06 06:20:58

So, the review should take into account that this is supposed to resolve Feature #7937 as well.

#48 Updated by BitingBird 2015-08-12 07:06:52

I had to redo your changes by hand. Didn’t do the unrelated changes (renaming mailing-list to mailing list in all the website), I’ll let you do that on another branch. I did everything in a single commmit, sorry for the inconvenience but I needed the terminal to see your changes and couldn’t commit and merge in the meantime.

Didn’t keep the alphabetical ordering, since I think presenting them in order of relevance for less-geeky users is more sensible. That’s open to discussion though.

I also didn’t take all changes to the introduction, as I don’t see how they improve.

I took all other changes.

Then I improved lots of things. What do you think?

#49 Updated by BitingBird 2015-08-12 08:30:53

  • Assignee changed from BitingBird to sajolida
  • % Done changed from 40 to 60

#50 Updated by sajolida 2015-08-26 10:45:13

  • Assignee changed from sajolida to BitingBird
  • QA Check changed from Ready for QA to Dev Needed

Cool, I really like the page now and I’m fine with the non-alphabetical order. Thanks for reusing the inline about user support languages in dca5e16.

I pushed a bunch of small commits on top with 76ccda5..88d163f.

Still, you didn’t answer this two concerns I raised in Feature #7698#37:

  • The information about tails-l10n is duplicated with contribute/how translate#follow-up. Can you propose something to fix that?
  • I think we should link from other parts of the website to this same page. In many places we refer to those lists without explaining to people how to subscribe or consult them. For example try to do git grep tails-dev -- "*.mdwn" and you’ll see what I mean. I don’t think we should link to this page every single time (for example not from the notes of the monthly meeting) but probably on all occurrences in the general user and contributor documentation.

#51 Updated by BitingBird 2015-09-22 15:00:47

  • Target version changed from Tails_1.6 to Tails_1.7

#52 Updated by BitingBird 2015-11-17 09:57:20

  • Target version changed from Tails_1.7 to 246

#53 Updated by sajolida 2015-11-27 04:46:27

  • Target version changed from 246 to Tails_2.0

#54 Updated by emmapeel 2016-01-08 11:51:36

  • has duplicate Bug #10867: 'Talk to us' section on website needs link to tails-project added

#55 Updated by emmapeel 2016-01-08 12:03:05

  • Assignee changed from BitingBird to emmapeel

I take it, but will not work on it before Tails Jessie, in case somebody wants to do it before…

#56 Updated by intrigeri 2016-01-08 14:59:26

  • Target version changed from Tails_2.0 to Tails_2.2

#57 Updated by emmapeel 2016-02-17 14:47:29

sajolida wrote:
> Cool, I really like the page now and I’m fine with the non-alphabetical order. Thanks for reusing the inline about user support languages in dca5e16.
>
> I pushed a bunch of small commits on top with 76ccda5..88d163f.
>
> Still, you didn’t answer this two concerns I raised in Feature #7698#37:
>
> * The information about tails-l10n is duplicated with contribute/how translate#follow-up. Can you propose something to fix that?

I don’t see the duplication. In fact this contact page is more like a directory of emails and such. It sends the user straight to contribute/how/translate

> * I think we should link from other parts of the website to this same page. In many places we refer to those lists without explaining to people how to subscribe or consult them. For example try to do git grep tails-dev -- "*.mdwn" and you’ll see what I mean. I don’t think we should link to this page every single time (for example not from the notes of the monthly meeting) but probably on all occurrences in the general user and contributor documentation.

Some lists have their own link. I suggest to always forward to the more clear explanation, and if it is not on other part of the docs, link to here.

For example, there is a support/tails-support page.

#58 Updated by emmapeel 2016-02-19 15:36:44

  • Assignee changed from emmapeel to sajolida
  • QA Check changed from Dev Needed to Ready for QA
  • Feature Branch changed from about/7698-contacts to emmapeel:about/7698-contacts

Please review branch on my repo, I tried not to be redundant with the links and I didn’t edited reports or other information with dates.

I did a git rebase but after I pushed my changes, not sure how it worked. Fingers crossed!

#59 Updated by sajolida 2016-03-07 15:05:15

  • Target version changed from Tails_2.2 to Tails_2.3

#60 Updated by sajolida 2016-03-15 22:10:28

  • Assignee changed from sajolida to emmapeel

We’re almost there, thanks! I did some more work to:

  • Deduplicate the info we had about tails-support (8602344), tails-l10n (e4a1a51), tails-testers (e5d7506), and tails-ux (f7b33e9).
  • Add more links to the new page.
  • Write ‘mailing list’ consistently (8772b32).
  • Remove contribute/talk which had become a placeholder (154dae0).
  • Move the new page to about/contact (522a834).

Please have a look and tell me what you think.

#61 Updated by sajolida 2016-03-19 17:54:57

  • Feature Branch changed from emmapeel:about/7698-contacts to web/7698-contacts

#62 Updated by emmapeel 2016-03-21 10:22:23

  • Assignee changed from emmapeel to sajolida
  • Feature Branch changed from web/7698-contacts to emmapeel:web/7698-contacts

Please review emmapeel:web/7698-contacts…

I liked the cauterization of the talk page… added the anchor for irc and a div for the public mailing list…

#63 Updated by sajolida 2016-03-21 17:12:25

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)
  • Feature Branch changed from emmapeel:web/7698-contacts to web/7698-contacts

Yeah, we can merge now at last!

#64 Updated by sajolida 2016-05-16 09:25:16

  • related to Bug #11423: Merge /support/chat and /contribute/chat into /about/contact added

#65 Updated by sajolida 2016-05-16 09:25:24

  • related to Bug #11424: Make /about/contact translatable added