CZ:Managing Editor/2010/004 - Simplification of application procedure
Statement of problem
Please be brief and specific in your request (polar questions are best) and add relevant links if available. Please state a time frame in which you expect a decision.
The current application procedure is too complex. --Daniel Mietchen 12:38, 23 November 2010 (UTC)
- Rephrased as a question: Can the current registration process be simplified without compromising essential functionalities?
- Time frame: Days - Weeks.
- --Daniel Mietchen 01:40, 24 November 2010 (UTC)
- See section #Essential functions of the registration process. --Daniel Mietchen 00:32, 11 April 2011 (UTC)
Essential functions of the registration process
Feel free to edit.
| Function | Currently included | Comment |
|---|---|---|
| Provide new users with an account to contribute | yes | Necessary if we want neither IP contributions nor an account with public password. |
| Verify email of new user | yes | Necessary for email notifications |
| Verify real name of new user | yes | Necessary for the real name policy mentioned in both the preamble and Article 2 of the Charter. |
| Name account after real name of new user | yes | Not strictly necessary under the real name policy above, yet practical. |
| Verify link between email and real name of new user | yes | Could be less restrictive in terms of allowable domain names |
| Ask for biography of new user | yes | Biography may be the wrong word, yet some form of experience, expertise and interests is necessary at some point, and doing so at signup is practical. [Perhaps: Request Biosketch, to include summary of relevant educational and work experience, list of particular interests, and list of areas of expertise. Anthony.Sebastian 03:39, 11 April 2011 (UTC)] |
| Ask for workgroups of interest to new user | yes | Not necessary at signup; could be handled as a separate step after account creation |
| Test command of English | yes | Not necessary at signup; better handled as a separate step after account creation, or even after the first edits. Also, this requirement keeps non-native speakers away (who may well contribute good content if someone else brushes their English), and contributions to the project may not even require high levels of writing in English (think of technical aspects like coding, templates, skins, categories, or images and multimedia). |
| For Editor applicants, ask for qualifications | yes | Not necessary at signup; better handled as a separate step after account creation |
Formal restatement of problem
This section defines the section structure of the decision.
Existing applicable policy
Charter
Decisions by the governing bodies
Auxiliary policy
Draft decision
The text below is what I plan to decide in this case. Feel free to edit the text if you think this improves it. If your edits require discussion, please use the dedicated section below. Editing and discussion in this "Draft decision" section shall stop 24h after my last edit to it.'
Discussion of Draft decision
When reading or editing this section, please keep in mind that the current version of the draft decision might be different from the one referred to by previous commenters.