CZ:Proposals/New: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Chunbum Park
(→‎Article task and notification list: rm proposal - i didnt know we had catalogs subpage)
m (Text replacement - "CZ:Proposals/Policy" to "Archive:Proposals/Policy")
 
(14 intermediate revisions by 9 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}}


== Need a Subpage for Topic Informants ==
== Extension:FormatDates ==
 
{{proposal
{{proposal
|Brief descriptive title = Need a Subpage for Topic Informants
|Brief descriptive title = Add the FormatDates extension (http://www.mediawiki.org/wiki/Extension:FormatDates).
|Summary of proposal = Topic Informants have been discussed off and on for months but nothing ever seems to be done about it. At Larry's suggestion, I once wrote a long TI about my relations with [[Robert A. Heinlein]]. Nothing has ever been done with it, even though I have brought up the topic from time to time, and the information is buried '''deep''' within my own user page at [http://en.citizendium.org/wiki/TI:Hayford_Peirce/Heinlein]. Why shouldn't there be an optional tab called Top. Inform. at the top of the Heinlein page, so that '''anyone''' who visits that page can review the info contained therein and then, if it is deemed qualified, put some of it into the article itself? If not, then why bother to have TI pages in the first place?
|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:Hayford Peirce|Hayford Peirce]] 14:01, 21 May 2008 (CDT)<br />
|Name and date of original proposer = [[User:Caesar Schinas|Caesar Schinas]] 13:31, 3 May 2009 (UTC)
|Username of driver = <br />
|Username of driver =  
|Next step = <br />
|Next step =  
|Target date for next step = 21 June 2008<br />
|Target date for next step =  
|Notes = I don't have a clue about how to be the Driver, but I would sure appreciate someone else taking up this thankless task!
|Notes =  
}}
}}


 
== Add Java applet support ==
 
{{proposal
== Subpages for watchknow videos ==
|Brief descriptive title = Java applet support
|Summary of proposal = Allow to upload and use Java applets in articles
|Name and date of original proposer = Audrius Meskauskas
|Username of driver = [[User:Audrius Meskauskas|Audrius Meskauskas]] 11:23, 30 September 2009 (UTC)
|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 =  
|Notes =
}}


{{proposal
{{proposal
|Brief descriptive title = Subpages for watchknow videos
|Brief descriptive title = Trending Citizendium Growth
|Summary of proposal = I propose that the editorial council welcomes the new watchknow project.
|Summary of proposal = Provide an automated tool to graph the gorwth of  
In addition we will create a new subpage for videos that explain the concepts behind an article. On default videos that get awarded the price money in watchknow should appear on that subpage of an appropriate article about the topic.
|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]] 16:59, 17 June 2008 (CDT)
|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 = Discussion
|Target date for next step =  
|Target date for next step = 01.08.2008
|Notes =   
|Notes =   
}}
}}
== Article task and notification list ==


{{proposal
{{proposal
|Brief descriptive title = Article task and notification list
|Brief descriptive title = Enforce One Style for Professional Web Presence
|Summary of proposal = I propose that we start a standardized list of tasks and notifications, which can be part of the metadata template.  The list would be by default unexpanded, but would be expandable from within the subpage template.  The article and each subpage might have its own task list, but at least we can begin with article lists.  Tasks would include items like "Add more wikilinks," and "Expand generally," and notifications would include items like "Article needs to be edited for neutrality" and "Article is controversial, please see talk page."  These notices would be generated by standard codes, and all the codes would be easily/instantly available in another collapsible/expandable list.  This would serve a similar purpose to WP's various top-of-page notices.  Of course, anyone would be able to edit the list--not just what notices are listed with which article, but also what notices are "standard."  There should also be support for some "ad hoc" notices as well.
|Summary of proposal = Enforce 1 skin, 1 set of approved, complimentary colors
|Name and date of original proposer = [[User:Larry Sanger|Larry Sanger]] 08:52, 21 June 2008 (CDT)
|Name and date of original proposer = [[User:David E. Volk|David E. Volk]] 16:32, 1 November 2009 (UTC)
|Username of driver =  
|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 = I hope someone will take this on--it seems like a great idea to me. --Larry
|Notes =
}}
}}

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