Websites/Taskforce/Proposals/End of Life: Difference between revisions

Websites/Taskforce/Proposals/End of Life (view source)

Revision as of 20:42, 1 March 2011

776 bytes added , 1 March 2011

no edit summary

Ryansnyder

1,241

edits

@@ Line 1: / Line 1: @@
 = Working Group =
@@ Line 6: / Line 5: @@
 = Status =
-Concept
+Proposal
 = Problem =
@@ Line 14: / Line 13: @@
 == Considerations ==
-All new websites should have an end of life process defined before they launch.
+Can we require that all new websites must have an end of life process defined before they launch?
 We have begun creating bugs to outline the end of life process for a couple websites.  You may see {{bug|636785}} as an example.
+Questions we are interested in covering include:
 * When will the campaign end?
 * When is the estimated date that we will retire this website?
@@ Line 23: / Line 23: @@
 ** Codebase?  Content?  Database?
 ** What will developers need to cleanse before turning off the site?
-* Security concerns
+* What are the security concerns for this website?
-* Website goals
+* What are the goals for this website?
-** Actions to take if website is not meeting desired goals
+** What actions to take if website is not meeting desired goals?
+Is a Bugzilla ticket the best place to record this information?  Would a wiki page for this site be a better solution?
 = Solution =
-To be determined.
+Require each new project creates a Bugzilla ticket] to identify and document any End of Life considerations we will need to be aware of.
+If at any time this website is nominated as a site destined for retirement, the product manager, web dev and ops will have a pre-determined list of all of the tasks they will need to take place.
 == Implementation ==
-To be determined.
+As part of each website's initiation project:
+. Create a new [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=website-archive.mozilla.org Bugzilla ticket] with the title "End of Life Plan - {Website Name}"