Bug #7574
Document the tails-press mailing list
30%
Description
The “talk to us” section of https://tails.boum.org/contribute/how/promote/ should be removed, and a link to the list provided instead.
https://tails.boum.org/press/ should also link to the list.
Subtasks
Related issues
Related to Tails - |
Resolved | 2014-07-31 | |
Blocks Tails - |
Resolved |
History
#1 Updated by sycamoreone about 11 years ago
I wanted to do that but apparently I can’t assign the ticket (to myself).
Does the tail-press list already exist?
#2 Updated by sycamoreone about 11 years ago
BitingBird wrote:
> The “talk to us” section of https://tails.boum.org/contribute/how/promote/ should be removed, and a link to the list provided instead.
This page is documentation for contributors and the “talk to us” section is the “contribute/talk” inline-page that appears on most pages for contributors.
I think this should stay on the page.
#3 Updated by intrigeri about 11 years ago
> I wanted to do that
Great! I’ve heard that maybe someone else was doing it, though.
If that’s the case, sajolida should be aware of it. sajolida?
> but apparently I can’t assign the ticket (to myself).
Now you can :)
> Does the tail-press list already exist?
Yes: F3CD 9B7B 4BDF 9995 DA22 088E 4570 80B5 A072 CBE3
.
#4 Updated by sycamoreone about 11 years ago
- Assignee set to sycamoreone
#5 Updated by sajolida about 11 years ago
> Great! I’ve heard that maybe someone else was doing it, though.
> If that’s the case, sajolida should be aware of it. sajolida?
No, that was assigned to sycamoreone.
#6 Updated by sycamoreone about 11 years ago
How should the tails-press@ PGP key be documented?
It would be consistent to add it to doc/about/openpgp_keys
but this would also make the page more complicated.
I could splice the new key into the section about the tails@boum.org list key,
but OTOH I rather wouldn’t advertise that tails-press is a mailing-list internally.
Any suggestions? At the moment the press page doesn’t mention PGP at all.
#7 Updated by intrigeri about 11 years ago
> OTOH I rather wouldn’t advertise that tails-press is a mailing-list internally.
Just my 2cts: it’s obvious in the key UIDs that it’s a list.
#8 Updated by sajolida about 11 years ago
I think it should be documented directly on the press page.
The OpenPGP keys pages needs to be at least partly rewritten and linked
better if we want it to be more efficient.
I’m also considering creating a page listing all the different options
to contact with our team or join our community, and the scope of each
contact address or mailing list… But that will come later on.
#9 Updated by sycamoreone about 11 years ago
redmine@labs.riseup.net:
> I think it should be documented directly on the press page.
Ok. Then I will will leave the OpenPGP keys page alone and
just mention and link to the key on the press page for now.
#10 Updated by sycamoreone about 11 years ago
Done in frithjof/tails-press in http://git.tails.boum.org/frithjof/tails/commit/?h=tails-press&id=9f3ed71c6f7b98f74c751760d2261d3ff2794e7f
[tails-press 9f3ed71] Document the tails-press list.
Should I ask for review on the list now, or is it enough to change the status of the ticket and wait?
#11 Updated by sycamoreone about 11 years ago
sycamoreone wrote:
> Should I ask for review on the list now,
> or is it enough to change the status of the ticket and wait?
I guess I already know.
#12 Updated by intrigeri about 11 years ago
- Assignee changed from sycamoreone to sajolida
- % Done changed from 0 to 30
- QA Check set to Ready for QA
#13 Updated by intrigeri about 11 years ago
- Target version set to Tails_1.1.1
#14 Updated by intrigeri about 11 years ago
- Status changed from Confirmed to In Progress
#15 Updated by intrigeri about 11 years ago
- blocks
Feature #7655: Include our new OpenPGP keys in Tails added
#16 Updated by sajolida about 11 years ago
- related to
Feature #7698: Create a place to gather information about the different mailing lists, and their scope and policy added
#17 Updated by sajolida about 11 years ago
- Feature Branch set to frithjof/tails-press
#18 Updated by sajolida about 11 years ago
- Status changed from In Progress to Resolved
- Assignee deleted (
sajolida) - QA Check deleted (
Ready for QA)