Bug #7535

Add new Tails UX mailing-list information to the documentation

Added by Anonymous 2014-07-09 16:46:36 . Updated 2014-09-22 03:05:46 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_1.1.1
Start date:
2014-07-09
Due date:
% Done:

50%

Feature Branch:
451f doc/uxml
Type of work:
End-user documentation
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

A mailinglist for tails-ux@boum.org has been created.

The scope and information for that ML should be added to the documentation (contribute/design?)

Subtasks

Related issues

Related to Tails - Bug #7676: Update contribute/how/user_interface/ Rejected 2014-07-28
Related to Tails - Feature #7698: Create a place to gather information about the different mailing lists, and their scope and policy Resolved 2014-07-31

History

#1 Updated by BitingBird 2014-07-09 17:01:38

  • Status changed from New to Confirmed

#2 Updated by intrigeri 2014-07-10 07:14:35

It seems that this task is looking for an assignee.

IMO, it’s the responsibility of the team who requested the list to ensure it’s documented (at least, producing a first draft-ish pull request), as they’re the best placed to define its scope and target audience.

#3 Updated by intrigeri 2014-07-11 14:51:37

  • Subject changed from Add new Tails UX mailinglist information to the documentation to Add new Tails UX mailing-list information to the documentation
  • Assignee set to alant
  • Priority changed from Normal to Elevated

Raising priority, as we should not get into the habit of starting using new lists before they are properly documented. For the same reason, assigning to a random person who’s on the UX list, so that this is on at least one radar and the question of “who does it” is raised.

#4 Updated by alant 2014-07-17 11:27:32

  • Assignee deleted (alant)

#5 Updated by alant 2014-07-17 11:34:09

  • Assignee deleted (None)

#6 Updated by Anonymous 2014-07-17 16:27:10

UX mailinglist scope and policy
===
The UX mailinglist shall facilitate the implication of new contributors
- designers, UX experts, users - who might not necessarily want to
follow the technical discussions on tails-dev.
We shall focus on user experience (UX) and user interface (UI) issues.
This can involve Tails custom software (tails-greeter, for example),
as well as work on the website, or graphics for the documentation.

Website content, documentation and development should still be managed
over tails-dev@boum.org.

Devs can and should be implicated in conception processes early enough by
crossposting. Mailing list moderators shall also take care of forwarding
interesting subjects from tails-dev to tails-ux and vice versa.

Policy:

- unencrypted

- public archives
- moderators should report back monthly if there is progress

#7 Updated by Anonymous 2014-07-23 14:00:01

  • Assignee deleted ()
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to 451f doc/uxml

#8 Updated by intrigeri 2014-07-24 10:25:36

  • Assignee set to sajolida
  • Target version set to Tails_1.1.1

#9 Updated by intrigeri 2014-07-25 08:10:45

  • Status changed from Confirmed to In Progress

#10 Updated by Anonymous 2014-07-28 21:46:09

  • related to Bug #7676: Update contribute/how/user_interface/ added

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

  • related to Feature #7698: Create a place to gather information about the different mailing lists, and their scope and policy added

#12 Updated by sajolida 2014-08-08 13:34:35

  • Status changed from In Progress to Resolved

Assignee:

#13 Updated by sajolida 2014-09-22 03:05:46

  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)