CZ:Proposals/New: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Gareth Leng
m (Text replacement - "CZ:Proposals/Policy" to "Archive:Proposals/Policy")
 
(139 intermediate revisions by 32 users not shown)
Line 1: Line 1:
=Instructions=
=Instructions=
'''To start a new proposal or issue,''' copy the template below, paste it on the ''bottom'' of this page, fill it out, and save!  That's it--it's very easy.  (Hint: you might want to open a copy of this page in a new window, so you can see the instructions as you fill out the template.)  Here's the template:
'''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.
<pre>
== Brief descriptive title ==
{{proposal
|Brief descriptive title =
|Summary of proposal =
|Name and date of original proposer =
|Username of driver =
|Next step =
|Target date for next step =
|Notes = 
}}
</pre>


Here's how to fill it out:
Here's how to fill it out:
# <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.
# <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</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.


If you haven't added your "Brief descriptive title" to the [[CZ:Proposals/Titles|titles page]], please do so now.
'''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]].)
 
'''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]].)


=New proposals=
=New proposals=
<big>Looking for your proposal, which used to be here?  Check the [[CZ:Proposals/Recently moved|recently moved proposals page]].</big>
<big>Looking for your proposal, which used to be here?  Check the [[CZ:Proposals/All|list of all proposals]].</big>


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.
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.


== Should history articles be named with general terms first? ==
<!-- 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. -->
{{proposal
{{Proposals navigation}}
|Brief descriptive title = Should history articles be named with general terms first?
 
|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:
== Extension:FormatDates ==
*[[France]]
*[[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 =
|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)
}}


==Article Content Request help==
{{proposal
{{proposal
|Brief descriptive title = Article Content Request help
|Brief descriptive title = Add the FormatDates extension (http://www.mediawiki.org/wiki/Extension:FormatDates).
|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 = 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:Robert W King|Robert W King]] 14:09, 11 February 2008 (CST)
|Name and date of original proposer = [[User:Caesar Schinas|Caesar Schinas]] 13:31, 3 May 2009 (UTC)
|Username of driver =  
|Username of driver =  
|Next step =  
|Next step =  
|Target date for next step =  
|Target date for next step =  
|Notes = Theoretical page located at [[CZ:ACR]] using [[template:request]].
|Notes =  
}}
}}


== Internationalisation sandbox ==
== Add Java applet support ==
{{proposal
{{proposal
|Brief descriptive title = Internationalisation sandbox
|Brief descriptive title = Java applet support
|Summary of proposal = There have been many requests for CZ pilots to begin in other languages, but so far nothing has gotten off the ground.  Inasmuch as 1) we are losing competent authors whose first language is not English but 2) we do not have the time, personnel or expertise to begin complete CZs in other languages, I propose a sandbox type setup in which those who will can go ahead and begin articles in other languages, but these will be hidden from public view until a bona fide project can be set up in that language.  Note that unlike the "sandbox" we have now, these drafts would not be discarded when the user signs off.
|Summary of proposal = Allow to upload and use Java applets in articles
|Name and date of original proposer = [[User:Aleta Curry|Aleta Curry]] 21:10, 13 February 2008 (CST)
|Name and date of original proposer = Audrius Meskauskas
|Username of driver =
|Username of driver = [[User:Audrius Meskauskas|Audrius Meskauskas]] 11:23, 30 September 2009 (UTC)
|Next step =  
|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 =  
|Target date for next step =  
|Notes =  There is a forum called Internationlization.  Or Internationalisation.  Something like that.  There is also a page on the wiki on which people are to enter the languages they are fluent in besides English.  I would direct you to it if I could.
}}
== Standard naming of biomedical articles ==
{{proposal
|Brief descriptive title = Standardizing the naming of biomedical articles.
|Summary of proposal = Encourage and facilitate usage of the [http://www.nlm.nih.gov/ National Library of Medicine]'s [http://www.nlm.nih.gov/mesh/MBrowser.html MeSH browser] (browser [[CZ:Searching#Internet_browser_search_plugins|search plugins]] are available) in order to select canonical terms to be used as titles (when such terms are available). The benefits of this are: 1) reduce the chance of two authors independently writing two articles in parallel on the same content (but with different titles), 2) offer standardized definitions of terms that can be used at the beginning of articles, 3) anticipate common alternative terms that can be set up as redirects when the article is written, 4) facilitate the linking to CZ from other biomedical databases when web 2 arrives. As an example, we have an article titled [[Concussion of the brain]] which according to MeSH, might be better titled '[http://www.ncbi.nlm.nih.gov/sites/entrez?cmd=Search&tool=cz&db=mesh&term=Brain%20concussion Brain concussion]' with a separate page called 'Cerebral concussion' that redirects to this page.
|Name and date of original proposer = [[User:Robert Badgett|Robert Badgett]] 00:23, 14 February 2008 (CST)
|Username of driver = [[User:Robert Badgett|Robert Badgett]] 00:23, 14 February 2008 (CST)
|Next step = Vet this proposal to see if worth carrying forward.
|Target date for next step = 3/1/2008
|Notes =   
|Notes =   
}}
}}


== Simplifying and improving CZ guidance pages ==
{{proposal
{{proposal
|Brief descriptive title = Approval system for CZ: pages
|Brief descriptive title = Trending Citizendium Growth
|Summary of proposal = Briefly, we have a logjam. The guidance pages are important and often sensitive, but need simplifying and improving. This intimidates editors (fear of introducing an error). I propose that we have an Approved version of all CZ pages, and a Draft version that is clearly open to all suggestions and contributions. The Approval process should be as that for other articles, except that the relevantly qualified "editors" are the Executive Committee. |Name and date of original proposer = [[User:Gareth Leng|Gareth Leng]] 07:08, 14 February 2008 (CST)
|Summary of proposal = Provide an automated tool to graph the gorwth of
|Username of driver =  
|Name and date of original proposer = [[User:Graham Proud|Graham Proud]] 12:40, 17 October 2009 (UTC)
|Next step =  
|Username of driver = [[User:Graham Proud|Graham Proud]]
|Next step = I have no idea how to implement this!
|Target date for next step =  
|Target date for next step =  
|Notes =   
|Notes =   
}}
}}
== Involving authors in approvals==
 
{{proposal
{{proposal
|Brief descriptive title =  
|Brief descriptive title = Enforce One Style for Professional Web Presence
|Summary of proposal = There are two aspects: 1) I see no reason why anyone should not feel able to ''nominate'' an article for approval (even their own article). Indeed I see every reason why all contributors to Citizendium should feel encouraged to read articles with potential approval in mind.
|Summary of proposal = Enforce 1 skin, 1 set of approved, complimentary colors
2) To approve articles requires the support of relevant editors. But I see no reason why authors should not also be able (and indeed be encouraged) to express their support or otherwise for approval, and indeed as Citizendium values fluency and style then the opinions of non-expert readers are very important too.
|Name and date of original proposer = [[User:David E. Volk|David E. Volk]] 16:32, 1 November 2009 (UTC)
|Name and date of original proposer = [[User:Gareth Leng|Gareth Leng]] 07:57, 14 February 2008 (CST)
|Username of driver = [[User:David E. Volk|David E. Volk]] 16:32, 1 November 2009 (UTC)
|Username of driver =  
|Next step = Drive to write proposal; awaiting CZ input
|Next step =  
|Target date for next step = Nov. 15, 2009
|Target date for next step =  
|Notes =   
|Notes =   
}}
}}
<!-- PLACE YOUR NEW PROPOSAL JUST ABOVE THIS LINE! -->
{{Proposals navigation}}

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