[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #21949 [User Experience/Website]: Identifying the requirements of the four torproject.org portals
#21949: Identifying the requirements of the four torproject.org portals
-------------------------------------+------------------------
Reporter: linda | Owner: linda
Type: defect | Status: closed
Priority: Medium | Milestone:
Component: User Experience/Website | Version:
Severity: Normal | Resolution: fixed
Keywords: | Actual Points:
Parent ID: #21222 | Points:
Reviewer: | Sponsor:
-------------------------------------+------------------------
Changes (by linda):
* status: assigned => closed
* resolution: => fixed
Old description:
> = Objective =
>
> Write user stories for all four portals to define the content
> requirements for each page.
>
> = Definition =
>
> * A user story describes the type of user, what they want and why. A user
> story helps to create a simplified description of a requirement. It is a
> description of a software feature from an end-user perspective.
>
> = Methodology =
>
> Talk with stakeholders of each portal, write user stories.
>
> = Results =
>
> HOME
> * Audience: first-time Tor users, people curious about Tor, press
> * Purpose: host critical first-user information and redirect people to
> the appropriate portals
>
> DEV
> * Audience: TPI devs, contract/volunteer devs, people who want to
> volunteer
> * Purpose: sync all the high-level information about work being done on
> Tor
>
> SUPPORT
> * Audience: first-time Tor users, relay operators, Tor users with issues
> * Purpose: help install Tor Browser, resolve common questions,
> troubleshoot common errors
>
> OUTREACH
> * Audience: Tor trainers, Tor speakers, Tor-evangelists on the ground
> * Purpose: give people excited about Tor what they need to energize more
> people about Tor
New description:
= Objective =
Write user stories for all four portals to define the content requirements
for each page.
= Definition =
* A user story describes the type of user, what they want and why. A user
story helps to create a simplified description of a requirement. It is a
description of a software feature from an end-user perspective.
= Methodology =
Talk with stakeholders of each portal, write user stories.
= Results =
'''torproject.org'''
* Audience: first-time Tor users, people curious about Tor, press
* Purpose: host critical first-user information and redirect people to the
appropriate portals
'''dev.torproject.org'''
* Audience: TPI devs, contract/volunteer devs, people who want to
volunteer
* Purpose: sync all the high-level information about work being done on
Tor
'''support.torproject.org'''
* Audience: first-time Tor users, relay operators, Tor users with issues
* Purpose: help install Tor Browser, resolve common questions,
troubleshoot common errors
'''outreach.torproject.org'''
* Audience: Tor trainers, Tor speakers, Tor-evangelists on the ground
* Purpose: give people excited about Tor what they need to energize more
people about Tor
--
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21949#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs