Websites/Taskforce/Proposals/Abandoned Sites/Retire: Difference between revisions

no edit summary
mNo edit summary
No edit summary
Line 3: Line 3:
Retired Mozilla websites will be made remembered in the website-archive blog.  
Retired Mozilla websites will be made remembered in the website-archive blog.  


= Product Owner Actions =
= Privacy Concerns =
 
This is the short list of data points we are concerned about expunging during the retirement process:
 
* username
* password
* full name
* email address
* IP address
* any profile data
* user provided data
* Web Logs
* Primary db store
* Backup copies of data
 
= Process =
 
== Product Owner Actions ==


The following actions will be performed by the product owner of a website:
The following actions will be performed by the product owner of a website:
Line 9: Line 26:
* Writeup details about the website that should be included in the retirement blog post.
* Writeup details about the website that should be included in the retirement blog post.
* Provide web dev with any relevant urls that visitors should be pointed to in the blog post.
* Provide web dev with any relevant urls that visitors should be pointed to in the blog post.
* Identify any places in the website where the site collected personal information:
* Identify any places in the website where the site collected personal information as identified above.
** ip address
** email address
** full name
** username
** anything stored a user profile
* Remove profile from Webtrends
* Remove profile from Webtrends


= Web Dev Actions =
== Web Dev Actions ==


The following actions will be performed by a member of the web development team.
The following actions will be performed by a member of the web development team.


== Prep Work ==
=== Prep Work ===
* File a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=website-archive.mozilla.org Bugzilla].
* File a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=website-archive.mozilla.org Bugzilla].
* Perform an [http://mxr.mozilla.org/ MXR] search ensure that the site is not being referenced by any of our products
* Perform an [http://mxr.mozilla.org/ MXR] search ensure that the site is not being referenced by any of our products
** File bugs with each product to remove / redirect reference.
** File bugs with each product to remove / redirect reference.


== Blog Post ==
=== Blog Post ===


* Take a screenshot of the existing site.
* Take a screenshot of the existing site.
Line 37: Line 49:
** Any relevant links that the reader should follow.
** Any relevant links that the reader should follow.


== Database ==
=== Database ===


All of the user identifiable information, such as email addresses, ip addresses, and user names will need to be identified.
All of the user identifiable information, such as email addresses, ip addresses, and user names will need to be identified.


1. Examine the database schema and identify where the website is collecting user identifiable data:
1. Examine the database schema and identify where the website is collecting user identifiable data as identified above.
* ip address
* email address
* full name
* username


2. Write queries for ops to run against the database to expunge user information from the database.
2. Write queries for ops to run against the database to expunge user information from the database.
Line 56: Line 64:
** Expunge the data
** Expunge the data
** Drop the database
** Drop the database
** Delete expunged data from backup tape.
* Website
* Website
** Disable any cron jobs for the site
** Disable any cron jobs for the site
Line 63: Line 72:
= Open Items =
= Open Items =
* Ops - How do we handle backed-up data?
* Ops - How do we handle backed-up data?
* Webdev - Add to ticket - delete this data from a backup tape
1,241

edits