CZ:Proposals/Driverless/Archive 1: Difference between revisions
< CZ:Proposals | Driverless
Jump to navigation
Jump to search
imported>Jitse Niesen (archive) |
imported>Jitse Niesen (fix archive box) |
||
| Line 1: | Line 1: | ||
{{archive box}} | {{driverless proposals archive box}} | ||
Every active proposal must have a driver, somebody who drives it along. Proposals without drivers end up in the "driverless" pile, which is split among several pages (see the box to the right). These proposals can at any time be resurrected if somebody volunteers to adopt it and become its driver. Simply put your name in the ''driver'' field of the proposal record, review [[CZ:Proposals/Policy|the rules for drivers]], and you're ready to go. | Every active proposal must have a driver, somebody who drives it along. Proposals without drivers end up in the "driverless" pile, which is split among several pages (see the box to the right). These proposals can at any time be resurrected if somebody volunteers to adopt it and become its driver. Simply put your name in the ''driver'' field of the proposal record, review [[CZ:Proposals/Policy|the rules for drivers]], and you're ready to go. | ||
Revision as of 07:57, 10 March 2009
Every active proposal must have a driver, somebody who drives it along. Proposals without drivers end up in the "driverless" pile, which is split among several pages (see the box to the right). These proposals can at any time be resurrected if somebody volunteers to adopt it and become its driver. Simply put your name in the driver field of the proposal record, review the rules for drivers, and you're ready to go.
Article task and notification list
Summary: 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.
| ||||||
| 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 | ||||||
Subpages for watchknow videos
| Summary: I propose that the editorial council welcomes the new watchknow project.
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.
| ||||
| 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 | ||||
Need a Subpage for Topic Informants
Summary: 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 [1]. 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?
| ||||||
| 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 | ||||||
Create a page for all notable genes in the human genome
Summary: We are interested in creating one page for all notable genes in the human genome. Each stub would be seeded using content which is harvested from publicly available sources. The resulting "Gene Wiki" would be a relatively unique resource compared to popular gene portals used by researchers and students. Given the expected number of created pages (5000-10000), an automated bot would be created/modified to perform the stub creation.
| ||||||
| 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 | ||||||
Standard naming of biomedical (and other) articles
Summary: Encourage and facilitate usage of the National Library of Medicine's MeSH browser (browser 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 'Brain concussion' with a separate page called 'Cerebral concussion' that redirects to this page.
| ||||||
| 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.
| ||||
| Complete proposal | ||||
Citizendium Mobile
Summary: Provide Citizendium pages automatically reformatted for mobile devices.
| ||||||
| Complete proposal | ||||||
Teaming with Young Authors
Summary: Two of the lesser-used Subpage options appear to be the Student Level and Tutorial pages, both seemingly directed at younger readers. The proposal would be to pair subject-matter author/editors with younger (under 18) authors in areas of joint interest for the specific purpose of creating Student Level and Tutorial pages.
| ||||||
| 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 | ||||||
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 | ||||||