CZ:Proposals/New: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Jitse Niesen
(move Teaming with Young Authors to Driverless queue)
imported>John Stephenson
(Romanization proposal)
Line 76: Line 76:
|Notes =   
|Notes =   
}}
}}
== Romanization ==
{{proposal
|Brief descriptive title = Romanization
|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.
|Name and date of original proposer = [[User:John Stephenson|John Stephenson]] 02:25, 4 March 2008 (CST)
|Username of driver = [[User:John Stephenson|John Stephenson]]
|Next step = Develop proposal page and request feedback from other contributors
|Target date for next step = 11 March 2008
|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.
}}
<!-- PLACE YOUR NEW PROPOSAL JUST ABOVE THIS LINE! -->
<!-- PLACE YOUR NEW PROPOSAL JUST ABOVE THIS LINE! -->
{{Proposals navigation}}
{{Proposals navigation}}

Revision as of 03:25, 4 March 2008

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

Here's the template:

== 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 =  
}}

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 goes in the == Heading ==, 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 recently moved proposals page.

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

Citizendium Mobile

Summary: Provide Citizendium pages automatically reformatted for mobile devices.
Original proposer: Graham Proud 12:05, 23 February 2008 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
Notes: Perhaps this is a 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.
Complete proposal


A new subpage for translations of approved articles

Summary: 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.
Original proposer: Jens Mildner 03:01, 23 February 2008 (CST) Next step: Write implementation list.
Driver: Jens Mildner To be done by: Mar 2, 2008
Notes: I see this as the perfect preparation for the international CZ.
Complete proposal


Create workgroup style guides

Summary: To promote coherent style and subsections within each workgroup, aid new users with examples of equations, drawings and other how-to items
Original proposer: David E. Volk 11:33, 29 February 2008 (CST) Next step: Get a volunteer from each group to volunteer as the lead author
Driver: Driver needed (i.e., someone familiar with the proposals system who will move it through the system) To be done by: March 15, 2008
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.
Complete proposal


Redirection creation bot

Summary: 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.
Original proposer: Christian Kleineidam 10:51, 1 March 2008 (CST) 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
Complete proposal


Romanization

Summary: 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.
Original proposer: John Stephenson 02:25, 4 March 2008 (CST) Next step: Develop proposal page and request feedback from other contributors
Driver: John Stephenson To be done by: 11 March 2008
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.
Complete proposal


Proposals System Navigation (advanced users only)

Proposal lists (some planned pages are still blank):