CZ:Proposals/New: Difference between revisions
Jump to navigation
Jump to search
imported>Larry Sanger |
imported>Larry Sanger |
||
| Line 25: | Line 25: | ||
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! | 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! | ||
'''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 = | ||
Revision as of 13:51, 13 February 2008
Instructions
To start a new proposal or issue, please give us six short pieces of information:
- Brief descriptive title. The exact same title you used on this page. Note, this goes in the
== Heading ==, too. - Summary of proposal. Limited to 100 words.
- Name and date of original proposer: write four tildes
~~~~ - 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. - Next step. The next thing you need to do to move the proposal toward reality. Not sure what to write? Hints here.
- 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.
- (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.
Put this information in this blank template:
== 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 =
}}
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!
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
Pilot to allow Citizens to take credit for pages
Summary: By popular demand, we would, to a limited extent, allow Citizens to take authorship credit of articles. This would (for now) take the form of a template placed at the bottom of the page, which would, in small and unobtrusive print, list the contributors to an article in alphabetical order. Contributors would add themselves. Names would appear only if there were three names in the list. To avoid issues about what counts as an "important" edit, a person could take co-authorship credit for the very smallest of edits (e.g., removing commas). We would try this out in just one or two workgroups (the template would be removed from articles in any other workgroup).
| ||||||
| Complete proposal | ||||||
Should history articles be named with general terms first?
| Summary: 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:
etc.
| ||||||
| Complete proposal | ||||||
Enable external feedback
Summary: 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.
| ||||
| Complete proposal | ||||
Article Content Request help
Summary: 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.
| ||||||
| Complete proposal | ||||||
How should we classify and index recipes?
Summary: 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.
| ||||||
| Complete proposal | ||||||
CZ Community pages should be revised for simplicity
Summary: Part of what is keeping our "elitism shield" up is that many (if not all) of the community pages are overly complex in terms of what they describe. A campaign to heavily review and edit the pages will give us leaner, easy-to-comprehend documentation and improve our external appearance.
| ||||
| Complete proposal | ||||
| Proposals System Navigation (advanced users only) | |
|
Proposal lists (some planned pages are still blank):
|