User talk:CMBJ/Sandbox

Wikipedia:Plan B(eta)

This plan is to be considered in the event that the project is facing significant, unique challenges that strain its resources or hinder its ability to operate optimally. Theoretical scenarios include but are not limited to:


 * Acute development demand
 * Infrastructure disruption
 * Financial hardship
 * Natural disaster
 * Other unforeseeable circumstances or functional incapacitation

While the process is intended primarily for deployment by the Foundation, it may also be invoked by the community as per the decree of a closing administrator in a reasonably judicious request for comment.

Requests for aid
In the event that additional resources are deemed necessary for optimal operation, a list of specific needs will be promptly created and distributed publicly at the soonest possible time. This decree will be accompanied by a basic framework designed and maintained to help facilitate ease of coordination between Foundation staff, previously unengaged volunteers and the community in general. Example details include a list of up-to-date mirrors for the project's data will be maintained for ease of re-deployment. Accessible formats should be used. Sensitive information, such as server access and certain project permissions, should be issued only if necessary and only to those who can be held accountable for their actions. All associated material must be clear, concise and designed with bootstrapping in mind.

Blueprints

 * Software
 * Chart: Operating system(s), server daemons, software libraries, special configurations
 * Notes: Nagging issues that frequently require manual intervention


 * Systems
 * Chart: Approximate processor, memory, storage, I/O and bandwidth requirements to handle traffic at 75%, 100% and 125% current daily max load
 * Diagram: Networking infrastructure
 * Notes: Scaling information, approximate power requirements (if hosted on-site)


 * Project
 * Diagram: Files likely to be of interest to external developers
 * Diagram: Basic database structure
 * Diagram: Default site theme
 * Notes: Known limitations and what overcoming them might entail

Coordination

 * Communication
 * Notes: Designated IRC channel, emergency technical and legal contacts


 * Collaborative tools
 * Notes: Repository information

Paperwork

 * Copyright waivers
 * OTRS-esque waivers for creative works


 * Liability waivers
 * For liability reasons as determined by the Foundation


 * Non-disclosure agreements
 * Only for server credentials and matters of oversight