CZ:Proposals/New: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Lee R. Berger
(citation of authors)
m (Text replacement - "CZ:Proposals/Policy" to "Archive:Proposals/Policy")
 
(78 intermediate revisions by 19 users not shown)
Line 1: Line 1:
=Instructions=
=Instructions=
'''To start a new proposal or issue,''' simply copy the template below, click the edit link at the top of this page, paste the copied template into the text box at the ''bottom'' underneath the other proposals, fill out the details in the template, and press save! That's it—it's very easy. (Hint: you might want to open a copy of this page in a new window so that you can follow the instructions as you fill out 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.
 
Here's the template:
<pre>
== Brief descriptive title ==
{{proposal
|Brief descriptive title = ADD TITLE HERE
|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>. 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 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.


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


== Citizendium Mobile ==
<!-- 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}}
 
== Extension:FormatDates ==
 
{{proposal
{{proposal
|Brief descriptive title = Citizendium Mobile
|Brief descriptive title = Add the FormatDates extension (http://www.mediawiki.org/wiki/Extension:FormatDates).
|Summary of proposal = Provide Citizendium pages automatically reformatted for mobile devices.
|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:Graham Proud|Graham Proud]] 12:05, 23 February 2008
|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 = Perhaps this is a [http://www.mediawiki.org MediaWiki] question, and not for Citizendium?  An example of how this could work may be seen in Microsoft's SharePoint Server, where the identical content is provided automatically in a layout more suited to small screens.
|Notes =  
}}
}}


== A new subpage for translations of approved articles ==
== Add Java applet support ==
{{proposal
{{proposal
|Brief descriptive title = Allow translations of approved articles
|Brief descriptive title = Java applet support
|Summary of proposal = Adopt and encourage translations of approved English CZ articles to other languages. This could be done with a new article subpage called "Other languages". The pagename would be Biology/Translations/German for instance.
|Summary of proposal = Allow to upload and use Java applets in articles
|Name and date of original proposer = [[User:Jens Mildner|Jens Mildner]] 03:01, 23 February 2008 (CST)
|Name and date of original proposer = Audrius Meskauskas
|Username of driver = [[User:Jens Mildner|Jens Mildner]]
|Username of driver = [[User:Audrius Meskauskas|Audrius Meskauskas]] 11:23, 30 September 2009 (UTC)
|Next step = Write implementation list.
|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 = Mar 2, 2008
|Target date for next step =  
|Notes = I see this as the perfect preparation for the international CZ.
}}
 
== Create workgroup style guides  ==
{{proposal
|Brief descriptive title = Create workgroup style guides
|Summary of proposal =  To promote coherent style and subsections within each workgroup, aid new users with examples of equations, drawings and other how-to items
|Name and date of original proposer = [[User:David E. Volk|David E. Volk]] 11:33, 29 February 2008 (CST)
|Username of driver =
|Next step = Get a volunteer from each group to volunteer as the lead author
|Target date for next step = March 15, 2008
|Notes =   
|Notes =   
A style guide, specific for each workgroup, while also fitting the general CZ formatting and qualities, would promote harmony and coherence within a workgroup.  It would point out what information and templates should always be included for a given workgroup.  Such pages should be listed in the Core Articles page for each workgroup.  An example of such a style guide, that still needs work, can be found at [[Chemistry style guide]].
}}
}}


== Redirection creation bot ==
{{proposal
{{proposal
|Brief descriptive title = Redirection creation bot
|Brief descriptive title = Trending Citizendium Growth
|Summary of proposal = I propose to create a bot that creates some redirects automatically to save users time that they could better use to create new articles instead of creating redirects and to increase the amount of redirects to make it easier for users to find the article they are looking for.
|Summary of proposal = Provide an automated tool to graph the gorwth of  
|Name and date of original proposer = [[User:Christian Kleineidam|Christian Kleineidam]] 10:51, 1 March 2008 (CST)
|Name and date of original proposer = [[User:Graham Proud|Graham Proud]] 12:40, 17 October 2009 (UTC)
|Username of driver =  
|Username of driver = [[User:Graham Proud|Graham Proud]]
|Next step =  
|Next step = I have no idea how to implement this!
|Target date for next step =  
|Target date for next step =  
|Notes =   
|Notes =   
}}
}}


== Romanization ==
{{proposal
{{proposal
|Brief descriptive title = Romanization
|Brief descriptive title = Enforce One Style for Professional Web Presence
|Summary of proposal = Create a page called [[CZ:Romanization]] to deal with issues of how to romanize foreign words, placenames etc. that are normally written in other scripts, with subpages for individual languages, e.g. [[CZ:Romanization/Japanese]]. These pages would initially be for interested parties to discuss which romanization systems to adopt, eventually leading to official policy.
|Summary of proposal = Enforce 1 skin, 1 set of approved, complimentary colors
|Name and date of original proposer = [[User:John Stephenson|John Stephenson]] 02:25, 4 March 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:John Stephenson|John Stephenson]]
|Username of driver = [[User:David E. Volk|David E. Volk]] 16:32, 1 November 2009 (UTC)
|Next step = Develop proposal page and request feedback from other contributors
|Next step = Drive to write proposal; awaiting CZ input
|Target date for next step = 11 March 2008
|Target date for next step = Nov. 15, 2009
|Notes =  I foresee a series of rows about this in the future because, for example, Japanese words can be rendered in the Latin alphabet in several different ways even within the same system, and there is more than one romanization system in use anyway.
}}
 
== Citation of Authors ==
{{proposal
|Brief descriptive title = Citing CZ article by authors|Summary of proposal =
|Name and date of original proposer = [[User:Lee R. Berger|Lee R. Berger]] 01:44, 5 March 2008 (CST)
|Username of driver = [[User:Lee R. Berger|Lee R. Berger]] 01:44, 5 March 2008 (CST)
|Next step = Create Proposal
|Target date for next step = Today
|Notes =   
|Notes =   
}}
}}
<!-- PLACE YOUR NEW PROPOSAL JUST ABOVE THIS LINE! -->
{{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