CZ:Proposals/New: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Chris Day
No edit summary
m (Text replacement - "CZ:Proposals/Policy" to "Archive:Proposals/Policy")
 
(10 intermediate revisions by 7 users not shown)
Line 6: Line 6:
# <code>Summary of proposal</code>.  Limited to 100 words.
# <code>Summary of proposal</code>.  Limited to 100 words.
# <code>Name and date of original proposer</code>: write four tildes <code><nowiki>~~~~</nowiki></code>
# <code>Name and date of original proposer</code>: write four tildes <code><nowiki>~~~~</nowiki></code>
# <code>Username of [[CZ:Proposals/Policy#The proposal driver|driver]]</code>. If you, write three tildes <code><nowiki>~~~</nowiki></code>; if someone else, specify.  This is the person who makes sure the proposal moves along from step to step in its development.  If the "driver" is left blank, and no one volunteers to be driver, your proposal may be moved to the "discarded" queue.  The driver should get familiar with [[CZ:Proposals/Policy|the proposals system policy page]].
# <code>Username of [[Archive:Proposals/Policy#The proposal driver|driver]]</code>. If you, write three tildes <code><nowiki>~~~</nowiki></code>; if someone else, specify.  This is the person who makes sure the proposal moves along from step to step in its development.  If the "driver" is left blank, and no one volunteers to be driver, your proposal may be moved to the "discarded" queue.  The driver should get familiar with [[Archive:Proposals/Policy|the proposals system policy page]].
# <code>Next step. </code>  The next thing you need to do to move the proposal toward reality.  Not sure what to write?  [[CZ:Proposals/Policy#Keeping the proposal moving along|Hints here]].
# <code>Next step. </code>  The next thing you need to do to move the proposal toward reality.  Not sure what to write?  [[Archive:Proposals/Policy#Keeping the proposal moving along|Hints here]].
# <code>Target date for next step</code>.  A date the driver commits to, for completing the next step.  If you drop the ball, the proposal may become [[CZ:Proposals/Driverless|driverless]].
# <code>Target date for next step</code>.  A date the driver commits to, for completing the next step.  If you drop the ball, the proposal may become [[CZ:Proposals/Driverless|driverless]].
# (Optional) <code>Notes</code>.  Brief salient remarks.  Bear in mind the bulk of the info about the proposal doesn't go here but on the (much bigger) proposal page.  A handy link to the proposal page will pop up after you save the template.
# (Optional) <code>Notes</code>.  Brief salient remarks.  Bear in mind the bulk of the info about the proposal doesn't go here but on the (much bigger) proposal page.  A handy link to the proposal page will pop up after you save the template.


'''Optional next step for proposers.''' This is optional, and you can leave it to the [[CZ:Proposals/Policy#The proposal driver|driver]]. Follow the "complete proposal" link you'll find at the bottom of your new proposal box. On that page, you can elaborate the proposal or issue, link to pre-existing discussions, and generally say whatever you think needs to be said in order to get the proposal adopted (or the issue decided) and implemented. That's generally where to follow the progress of your proposal. ([[CZ:Proposals/Policy|Guidelines are available]].)
'''Optional next step for proposers.''' This is optional, and you can leave it to the [[Archive:Proposals/Policy#The proposal driver|driver]]. Follow the "complete proposal" link you'll find at the bottom of your new proposal box. On that page, you can elaborate the proposal or issue, link to pre-existing discussions, and generally say whatever you think needs to be said in order to get the proposal adopted (or the issue decided) and implemented. That's generally where to follow the progress of your proposal. ([[Archive:Proposals/Policy|Guidelines are available]].)


=New proposals=
=New proposals=
Line 21: Line 21:
{{Proposals navigation}}
{{Proposals navigation}}


== Standardizing nomenclature for wars/conflicts, with system to link in partisan names ==
== Extension:FormatDates ==


{{proposal
{{proposal
|Brief descriptive title = Article names for wars/conflicts
|Brief descriptive title = Add the FormatDates extension (http://www.mediawiki.org/wiki/Extension:FormatDates).
|Summary of proposal = We have had confusion, and some arguments, on the nomenclature for events involving "the extension of politics (group or national) through military or paramilitary means."  The confusion involves both semantics and syntax. We need standards.
|Summary of proposal = It's very annoying the way some dates on CZ are in UK format (3rd May 2009 or 03/05/2009), some in US format (May 3, 2009 or 05/03/2009), and some in "international" format (2009-05-03). The use of the FormatDates extension (http://www.mediawiki.org/wiki/Extension:FormatDates) would solve this problem.
|Name and date of original proposer = [[User:Caesar Schinas|Caesar Schinas]] 13:31, 3 May 2009 (UTC)
|Username of driver =
|Next step =
|Target date for next step =
|Notes =
}}


Semantic:
== Add Java applet support ==
*neutral name, with partisan and other names mentioned early in the article and with redirects to them (e.g., War Between the States, War of Yankee Aggression)
{{proposal
*Partisan names (e.g., Operation IRAQI FREEDOM, 2003 US invasion of Iraq).
|Brief descriptive title = Java applet support
*specialized (e.g., POLO STEP vice IRAQI FREEDOM)
|Summary of proposal = Allow to upload and use Java applets in articles
*high-intensity combat vs. occupation/nationbuilding/resistance
|Name and date of original proposer = Audrius Meskauskas
 
|Username of driver = [[User:Audrius Meskauskas|Audrius Meskauskas]] 11:23, 30 September 2009 (UTC)
Syntax means choosing the format of:
|Next step = Implement Wiki language extensions, allowing to embed Java applet into article. Allow to upload .jar files into repository.
*[location], conflict in [dates]
|Target date for next step =  
*conflict (war) in [location] [dates]
 
|Name and date of original proposer = [[User:Howard C. Berkowitz|Howard C. Berkowitz]] 09:58, 24 July 2008 (CDT)
|Username of driver = [[User:Howard C. Berkowitz|Howard C. Berkowitz]]
|Next step = Get feedback about need and methods
|Target date for next step = 31 July 2008
|Notes =   
|Notes =   
}}
}}
== Separate Author registration from Editor registration ==


{{proposal
{{proposal
|Brief descriptive title = Separate Author registration from Editor registration
|Brief descriptive title = Trending Citizendium Growth
|Summary of proposal = To make it easier for new people to register for Citizendium:
|Summary of proposal = Provide an automated tool to graph the gorwth of  
After this proposal is implement, there is a separate page for the registration of authors than there is for the registration of editors.
|Name and date of original proposer = [[User:Graham Proud|Graham Proud]] 12:40, 17 October 2009 (UTC)
|Name and date of original proposer = [[User:Christian Kleineidam|Christian Kleineidam]] 19:57, 30 November 2008 (UTC)
|Username of driver = [[User:Graham Proud|Graham Proud]]
|Username of driver = [[User:Christian Kleineidam|Christian Kleineidam]]
|Next step = I have no idea how to implement this!
|Next step = Get Feedback
|Target date for next step =  
|Target date for next step = 01.01.2009
|Notes =   
|Notes =   
}}
}}


{{proposal
{{proposal
|Brief descriptive title = Subgroups in addition to Workgroups?
|Brief descriptive title = Enforce One Style for Professional Web Presence
|Summary of proposal =Subgroups can represent a subset of editors and authors from a workgroup with a niche interest, be a vehicle for collaboration between different workgroups, a navigation tool or all of these concepts. They will function in a similar manner to workgroups but be smaller and only semi-autonomous since they must be affiliated to one or more workgroups.
|Summary of proposal = Enforce 1 skin, 1 set of approved, complimentary colors
|Name and date of original proposer = Chris Day, Jan 2009
|Name and date of original proposer = [[User:David E. Volk|David E. Volk]] 16:32, 1 November 2009 (UTC)
|Username of driver = [[User:Chris Day|Chris Day]]
|Username of driver = [[User:David E. Volk|David E. Volk]] 16:32, 1 November 2009 (UTC)
|Next step =  
|Next step = Drive to write proposal; awaiting CZ input
|Target date for next step =  
|Target date for next step = Nov. 15, 2009
|Notes =   
|Notes =   
}}
}}

Latest revision as of 02:01, 8 March 2024

Instructions

To start a new proposal or issue, simply click this edit link - it is recommended that you right-click the link, and select 'open in new window' to open it in a new window, so that you can continue to be able to read the instructions here in the old window. That link will provide an edit window containing a blank copy of the template which needs to be filled out in order to create a new proposal section here. Enter the details in the template, using the instructions below, and press save! That's it — it's very easy.

Here's how to fill it out:

  1. Brief descriptive title. Make this brief, because it will be part of a page title. If you are raising an issue (ask for a decision among two or more options), please word the title as a question. Note: this exact same text goes in the Subject/headline box, too.
  2. Summary of proposal. Limited to 100 words.
  3. Name and date of original proposer: write four tildes ~~~~
  4. Username of driver. If you, write three tildes ~~~; if someone else, specify. This is the person who makes sure the proposal moves along from step to step in its development. If the "driver" is left blank, and no one volunteers to be driver, your proposal may be moved to the "discarded" queue. The driver should get familiar with the proposals system policy page.
  5. Next step. The next thing you need to do to move the proposal toward reality. Not sure what to write? Hints here.
  6. Target date for next step. A date the driver commits to, for completing the next step. If you drop the ball, the proposal may become driverless.
  7. (Optional) Notes. Brief salient remarks. Bear in mind the bulk of the info about the proposal doesn't go here but on the (much bigger) proposal page. A handy link to the proposal page will pop up after you save the template.

Optional next step for proposers. This is optional, and you can leave it to the driver. Follow the "complete proposal" link you'll find at the bottom of your new proposal box. On that page, you can elaborate the proposal or issue, link to pre-existing discussions, and generally say whatever you think needs to be said in order to get the proposal adopted (or the issue decided) and implemented. That's generally where to follow the progress of your proposal. (Guidelines are available.)

New proposals

Looking for your proposal, which used to be here? Check the list of all proposals.

If a proposal here does not have a "driver," it may be moved to the driverless proposals queue a week after being proposed.

Proposals System Navigation (advanced users only)

Proposal lists (some planned pages are still blank):

Extension:FormatDates

Summary: It's very annoying the way some dates on CZ are in UK format (3rd May 2009 or 03/05/2009), some in US format (May 3, 2009 or 05/03/2009), and some in "international" format (2009-05-03). The use of the FormatDates extension (http://www.mediawiki.org/wiki/Extension:FormatDates) would solve this problem.
Original proposer: Caesar Schinas 13:31, 3 May 2009 (UTC) Next step: Fill in next step
Driver: Driver needed (i.e., someone familiar with the proposals system who will move it through the system) To be done by: Fill in target date for next step
To the proposer: please read the proposals system policy page if you want to fill out a complete proposal, not just this summary. If you don't, please ask around for someone (a "driver") to take over your proposal!
Start complete proposal


Add Java applet support

Summary: Allow to upload and use Java applets in articles
Original proposer: Audrius Meskauskas Next step: Implement Wiki language extensions, allowing to embed Java applet into article. Allow to upload .jar files into repository.
Driver: Audrius Meskauskas 11:23, 30 September 2009 (UTC) To be done by: Fill in target date for next step
Complete proposal


Summary: Provide an automated tool to graph the gorwth of
Original proposer: Graham Proud 12:40, 17 October 2009 (UTC) Next step: I have no idea how to implement this!
Driver: Graham Proud To be done by: Fill in target date for next step
To the proposer: please read the proposals system policy page if you want to fill out a complete proposal, not just this summary. If you don't, please ask around for someone (a "driver") to take over your proposal!
Start complete proposal


Summary: Enforce 1 skin, 1 set of approved, complimentary colors
Original proposer: David E. Volk 16:32, 1 November 2009 (UTC) Next step: Drive to write proposal; awaiting CZ input
Driver: David E. Volk 16:32, 1 November 2009 (UTC) To be done by: Nov. 15, 2009
Complete proposal