CZ:Proposals/New: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Larry Sanger
m (Text replacement - "CZ:Proposals/Policy" to "Archive:Proposals/Policy")
 
(158 intermediate revisions by 32 users not shown)
Line 1: Line 1:
=Instructions=
=Instructions=
'''To start a new proposal or issue,''' please give us six short pieces of information:
'''To start a new proposal or issue,''' simply click [http://en.citizendium.org/wiki?title=CZ:Proposals/New&action=edit&section=new&preload=Template:Proposal_blank 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.


# <code>Brief descriptive title</code>. The exact same title you used on [[CZ:Proposals/Titles|this page]]. '''Note,''' this goes in the <code>== Heading ==</code>, too.
Here's how to fill it out:
# <code>Brief descriptive title</code>. 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 <code>Subject/headline</code> box, too.
# <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:''' 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.


Put this information in this blank template:
'''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]].)
<pre>
 
== Brief descriptive title ==
=New proposals=
{{proposal
<big>Looking for your proposal, which used to be here?  Check the [[CZ:Proposals/All|list of all proposals]].</big>
|Brief descriptive title =
|Summary of proposal =
|Name and date of original proposer =
|Username of driver =  
|Next step =  
|Target date for next step =
|Notes = 
}}
</pre>


Simply copy and paste that at the bottom of this page, fill it out, and save. Then you've finished creating your new proposal/issue!
If a proposal here does not have a "driver," it may be moved to [[CZ:Proposals/Driverless|the driverless proposals queue]] a week after being proposed.


'''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]].)
<!-- This is here, and not at the bottom of the page as before, because the 'auto-add-new-section' stuff can't deal with putting the new sections *above* it. -->
{{Proposals navigation}}


= New proposals =
== Extension:FormatDates ==
== Pilot to allow Citizens to take credit for pages ==
Moved to [[CZ:Proposals/Editorial Council]].


== Should history articles be named with general terms first? ==
{{proposal
{{proposal
|Brief descriptive title = Should history articles be named with general terms first?
|Brief descriptive title = Add the FormatDates extension (http://www.mediawiki.org/wiki/Extension:FormatDates).
|Summary of proposal = Should general article names be written as [[France, history]] as preferred to [[History of France]] or [[French History]]?  The central points of contention is whether general articles (e.g [[France, history]]) should be called [[History of France]] or even [[French history]]. The idea is that the keyword should be first in an article such as this, with people searching for [[France]] in a general search will see a list of articles, e.g:
|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.
*[[France]]
|Name and date of original proposer = [[User:Caesar Schinas|Caesar Schinas]] 13:31, 3 May 2009 (UTC)
*[[France, history]]
*[[France, politics]]
*[[France, literature]]
etc.  
|Name and date of original proposer = [[User:Denis Cavanagh|Denis Cavanagh]] 11:29, 8 February 2008 (CST)
|Username of driver =  
|Username of driver =  
|Next step =  
|Next step =  
|Target date for next step =  
|Target date for next step =  
|Notes= This has been discussed before but deserves a fuller debate. I don't really have an opinion on the issue despite the history workgroup handily being my most active one.[[User:Denis Cavanagh|Denis Cavanagh]] 11:29, 8 February 2008 (CST)
|Notes =  
}}
}}


==Enable external feedback==
== Add Java applet support ==
 
{{proposal
{{proposal
|Brief descriptive title = Enable external feedback
|Brief descriptive title = Java applet support
|Summary of proposal = Each article should have a link for non-citizens to submit feedback. Feedback can be read and acted upon by any Citizen. To make the feedback system easier to use for both readers and Citizens, feedback can be in the form of a machine-readable proposed edit.
|Summary of proposal = Allow to upload and use Java applets in articles
|Name and date of original proposer = [[User:Warren Schudy|Warren Schudy]] 13:34, 9 February 2008 (CST)
|Name and date of original proposer = Audrius Meskauskas
|Username of driver = [[User:Warren Schudy|Warren Schudy]]
|Username of driver = [[User:Audrius Meskauskas|Audrius Meskauskas]] 11:23, 30 September 2009 (UTC)
|Next step = Ensure proposal page summarizes community views
|Next step = Implement Wiki language extensions, allowing to embed Java applet into article. Allow to upload .jar files into repository.
|Target date for next step = Feb 20
|Target date for next step =  
|Notes =  
|Notes =
}}
}}
==Article Content Request help==


{{proposal
{{proposal
|Brief descriptive title = Article Content Request help
|Brief descriptive title = Trending Citizendium Growth
|Summary of proposal= [[CZ:ACR|Article Content Request]] should exist in order for authors to request article assistance on particular topics within a subject.  This is '''not''' intended to be a request for editorial review, rather, it is a system devised to empower citizens to help out on subjects that they might know about.  It is meant to spur activity and input from those who might have knowledge in a discipline.
|Summary of proposal = Provide an automated tool to graph the gorwth of
|Name and date of original proposer= --[[User:Robert W King|Robert W King]] 14:09, 11 February 2008 (CST)
|Name and date of original proposer = [[User:Graham Proud|Graham Proud]] 12:40, 17 October 2009 (UTC)
|Username of driver = Some User
|Username of driver = [[User:Graham Proud|Graham Proud]]
|Next step = This should be in the username of driver field.
|Next step = I have no idea how to implement this!
|Target date for next step= Near future
|Target date for next step =  
|Notes = Theoretical page located at [[CZ:ACR]] using [[template:request]].
|Notes =
}}
}}


== How should we classify and index recipes? ==
{{proposal
{{proposal
|Brief descriptive title = How should we classify and index recipes?
|Brief descriptive title = Enforce One Style for Professional Web Presence
|Summary of proposal = A new subpage type should be created [[CZ:Recipes]]. Anyone interested may take the lead in creating CZ:Recipes and then  the Recipe subpage support should be added to the subpage system. The subpage may be bilaterally linked with the [[Cooking]] page.
|Summary of proposal = Enforce 1 skin, 1 set of approved, complimentary colors
|Name and date of original proposer = [[User:Hayford Peirce|Hayford Peirce]] 16:50, 12 February 2008 (CST)
|Name and date of original proposer = [[User:David E. Volk|David E. Volk]] 16:32, 1 November 2009 (UTC)
|Username of driver = [[User:Supten Sarbadhikari|Supten Sarbadhikari]]
|Username of driver = [[User:David E. Volk|David E. Volk]] 16:32, 1 November 2009 (UTC)
|Next step = Discussion and a firm decision after consensus is reached
|Next step = Drive to write proposal; awaiting CZ input
|Target date for next step = February 20, 2008.
|Target date for next step = Nov. 15, 2009
|Notes = What should we do about listing, and/or cataloging, and/or indexing the recipes that I am beginning to put into various preexisting articles. Various people discussed this in the talk page of [[Bolognese sauce]] but nothing concrete appears to have come of that discussion. Even without any definitive policy being put into place in the near future, I will continue to add recipes to various articles. I imagine that it will not be difficult to catalog, or subpage them, or whatever, when the time comes. [[User:Hayford Peirce|Hayford Peirce]]
|Notes =
}}
}}
== Change to reversion policy ==
Moved to [[CZ:Proposals/Constabulary]].
{{Proposals navigation}}

Latest revision as of 03: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