Archive:Project Home/Launch Requirements: Difference between revisions
Jump to navigation
Jump to search
imported>ZachPruckowski No edit summary |
imported>ZachPruckowski No edit summary |
||
Line 3: | Line 3: | ||
==Technical== | ==Technical== | ||
===Hardware=== | ===Hardware=== | ||
Selected servers requested from Steadfast (need to be set up): | |||
Current Server will be database master | |||
:2 x dual-core Xeon 51x0 (unknown clockspeed) | |||
:4 GB RAM | |||
:??? hard drives | |||
Web Server: | |||
:Centos 4.4 | |||
:Frontend for Database Server. | |||
:Core 2 Duo E6600 2.4Ghz 4MB Cache Core 2 Duo (Dual Core) | |||
:100 GB SATA II Hard Drive | |||
:2 GB ECC DDR2 SDRAM | |||
Application Server: | |||
:Fedora Core 6/maybe VMware Server on top of | |||
:DNS, Load Balancing, Static WWW, Mysql server, email and lists (also blog) | |||
:Core 2 Duo E6600 2.4Ghz 4MB Cache Core 2 Duo (Dual Core) | |||
:250 GB SATA II Hard Drive | |||
:4 GB ECC DDR2 SDRAM | |||
Development Server: | |||
:Fedora Core 6 | |||
:Gforge, SVN, development www/SQL servers, playground. | |||
:Pentium D (unknown speed or model) | |||
:100 GB SATA II Hard Drive | |||
:1 GB ECC DDR2 SDRAM | |||
Backup WWW Server: | |||
:Centos 4.4 | |||
:Caching/Frontend for DB Server. | |||
:Core 2 Duo E6600 2.4Ghz 4MB Cache Core 2 Duo | |||
:100 GB SATA II Hard Drive | |||
:4 GB ECC DDR2 SDRAM | |||
===Software=== | ===Software=== | ||
# | #Migrate to MediaWiki 1.9.x or a pre-release of 1.10 | ||
#Design Wikipedia Update system | #Design Wikipedia Update system | ||
#Automate personnel tasks | #Automate personnel tasks | ||
#Design approval system <s>(at least a temporary version)</s> | #Design approval system <s>(at least a temporary version)</s> | ||
#Images. | #Images. | ||
##Scaling of Images | ##Scaling of Images | ||
##Import acceptable WP images | ##Import acceptable WP images | ||
==Administrative== | ==Administrative== | ||
#Reconnect with various foundations, etc., after we're in with Tides. | #Reconnect with various foundations, etc., after we're in with Tides. | ||
#Decrease email response time | #Decrease email response time | ||
Line 27: | Line 53: | ||
==Content== | ==Content== | ||
#Retool [[Main Page]] for readers, and put author or editor stuff | #Retool [[Main Page]] for readers, and put author or editor stuff to [[Citizendium_Pilot:Project Home]]. See [[Talk:Main Page]]. | ||
#Create ''Citizendium'' userspace, and begin migrating Citizendium_Pilot pages over to it | #Create ''Citizendium'' userspace, and begin migrating Citizendium_Pilot pages over to it | ||
#[[ | #[[CZ:Policy Outline|Policy Outline]] should be appropriately elaborated. | ||
##[[Citizendium_Pilot:Feasibility|Feasibility]] | ##[[Citizendium_Pilot:Feasibility|Feasibility]] | ||
##[[Citizendium_Pilot:Family Friendly Policy|Family Friendliness]] | ##[[Citizendium_Pilot:Family Friendly Policy|Family Friendliness]] | ||
Line 37: | Line 61: | ||
##high-priority items, including: approval process; dispute resolution; naming conventions and formatting; how to convert Wikipedia articles to Citizendium articles; the "Article Standards" detail pages; policy on content-based bans; policy on topic informants; policy on shared articles; policy on starting subgroups | ##high-priority items, including: approval process; dispute resolution; naming conventions and formatting; how to convert Wikipedia articles to Citizendium articles; the "Article Standards" detail pages; policy on content-based bans; policy on topic informants; policy on shared articles; policy on starting subgroups | ||
##Policies similar to Wikipedia's that we intend to mirror. | ##Policies similar to Wikipedia's that we intend to mirror. | ||
## | ##Image Policies - what licenses, formats, etc. | ||
#The [[Citizendium_Pilot:Author]], [[Citizendium_Pilot:Constable]] and [[Citizendium_Pilot:Editor]] pages need to be high-quality. | #The [[Citizendium_Pilot:Author]], [[Citizendium_Pilot:Constable]] and [[Citizendium_Pilot:Editor]] pages need to be high-quality. | ||
#Approved Articles: at least 10, with half of them coming from articles that were not featured articles or good articles on Wikipedia. | #Approved Articles: at least 10, with half of them coming from articles that were not featured articles or good articles on Wikipedia. | ||
==Staffing== | ==Staffing== | ||
#Consider adding more constables | #Consider adding more constables | ||
#Dramatically increase personnel administrators to prepare for higher signup rate post-launch; or else code a new and automated method of getting people on board. | #Dramatically increase personnel administrators to prepare for higher signup rate post-launch; or else code a new and automated method of getting people on board. | ||
#Increase size of volunteer tech support team from 3 to about 5-6 | #Increase size of volunteer tech support team from 3 to about 5-6 | ||
Revision as of 21:46, 5 March 2007
This page outlines the requirements for a public launch of the project. The target launch date has not been announced, but will fall in the early part of 2007.
Technical
Hardware
Selected servers requested from Steadfast (need to be set up):
Current Server will be database master
- 2 x dual-core Xeon 51x0 (unknown clockspeed)
- 4 GB RAM
- ??? hard drives
Web Server:
- Centos 4.4
- Frontend for Database Server.
- Core 2 Duo E6600 2.4Ghz 4MB Cache Core 2 Duo (Dual Core)
- 100 GB SATA II Hard Drive
- 2 GB ECC DDR2 SDRAM
Application Server:
- Fedora Core 6/maybe VMware Server on top of
- DNS, Load Balancing, Static WWW, Mysql server, email and lists (also blog)
- Core 2 Duo E6600 2.4Ghz 4MB Cache Core 2 Duo (Dual Core)
- 250 GB SATA II Hard Drive
- 4 GB ECC DDR2 SDRAM
Development Server:
- Fedora Core 6
- Gforge, SVN, development www/SQL servers, playground.
- Pentium D (unknown speed or model)
- 100 GB SATA II Hard Drive
- 1 GB ECC DDR2 SDRAM
Backup WWW Server:
- Centos 4.4
- Caching/Frontend for DB Server.
- Core 2 Duo E6600 2.4Ghz 4MB Cache Core 2 Duo
- 100 GB SATA II Hard Drive
- 4 GB ECC DDR2 SDRAM
Software
- Migrate to MediaWiki 1.9.x or a pre-release of 1.10
- Design Wikipedia Update system
- Automate personnel tasks
- Design approval system
(at least a temporary version) - Images.
- Scaling of Images
- Import acceptable WP images
Administrative
- Reconnect with various foundations, etc., after we're in with Tides.
- Decrease email response time
- Create "Total Idiot's Guides" for Citizendium and MediaWiki functions. We need some method of helping people who have no prior MW (and possibly little computer) experience do things like use wikitext and deal with templates/images.
Content
- Retool Main Page for readers, and put author or editor stuff to Citizendium_Pilot:Project Home. See Talk:Main Page.
- Create Citizendium userspace, and begin migrating Citizendium_Pilot pages over to it
- Policy Outline should be appropriately elaborated.
- Feasibility
- Family Friendliness
- Article standards
- high-priority items, including: approval process; dispute resolution; naming conventions and formatting; how to convert Wikipedia articles to Citizendium articles; the "Article Standards" detail pages; policy on content-based bans; policy on topic informants; policy on shared articles; policy on starting subgroups
- Policies similar to Wikipedia's that we intend to mirror.
- Image Policies - what licenses, formats, etc.
- The Citizendium_Pilot:Author, Citizendium_Pilot:Constable and Citizendium_Pilot:Editor pages need to be high-quality.
- Approved Articles: at least 10, with half of them coming from articles that were not featured articles or good articles on Wikipedia.
Staffing
- Consider adding more constables
- Dramatically increase personnel administrators to prepare for higher signup rate post-launch; or else code a new and automated method of getting people on board.
- Increase size of volunteer tech support team from 3 to about 5-6