Difference between revisions of "ISFDB:Beta"
Jump to navigation
Jump to search
(→Showstopper Bug Fixes: Removed 10022) |
(→Showstopper Bug Fixes: Removed 10038) |
||
| Line 1: | Line 1: | ||
| + | Since we are not planning to limit editor activity, there are no recruitment goals for number of editors. We will simply open up for editing, and will remain in beta until we meet the exit criteria. | ||
| + | |||
| + | == Goals == | ||
| + | *Find outstanding bugs | ||
| + | *get confidence there are no dataloss bugs left | ||
| + | *understand how editors are actually going to focus -- are the project pages what they need to manage their data, for example, and will they need something like a watchlist. | ||
| + | *get input on prioritizing next features | ||
| + | *prove that data really does (a) get added, (b) gets cleaned up, and (c) stays cleaned up | ||
| + | ==Exit Criteria== | ||
| + | For the beta to conclude, there must be no known dataloss bugs, and no known bugs which cause software crashes. | ||
| + | |||
| + | In addition, consensus must be reached among editors that the software provides sufficient support for editors to be interested in contributing. The criteria the editors will use are to be determined by them, but are likely to include: | ||
| + | * The interface is sufficiently easy to use | ||
| + | * Help files and support are available to answer questions about how to achieve certain tasks | ||
| + | * The system is sufficiently reliable | ||
| + | * They are confident that the work they do is stable against vandalism, and incorrect edits. | ||
| + | |||
| + | "Sufficiently" in the criteria above means that the system is good enough that editors are not discouraged from being active by any flaws. | ||
| + | |||
| + | == Showstopper Bug Fixes == | ||
| + | [[Open_Editing_Bugs]] | ||
| + | * 10014 - Unicode hell. | ||
| + | * 10027 - Editing reviews and interviews loses data. | ||
| + | * 10032 - Variant title hilarity. | ||
| + | * 10039 - Chapterbook support. | ||
| + | |||
| + | == Wiki == | ||
| + | |||
| + | The following tasks within the wiki should be completed before we go live on the beta. | ||
| + | * Clean out old help files. ''Done''. | ||
| + | * Make a pass through the project pages and see if we can improve the usability of the overall organization. It's apparent from various messages on the portal that it is not always easy to locate the right project for a task or issue. ''Awaiting consensus this is complete''. | ||
| + | * Add remaining help pages; improve existing ones. Largely complete, but further improvements are certainly possible. ''Done'' as far as needed for Beta. | ||
| + | * Agree on landing page for beta recruits; write that page. | ||
| + | * Agree on remaining features to be implemented. ''In process; see below''. | ||
| + | |||
| + | ==Remaining features== | ||
| + | |||
| + | This section lists features that will be implemented prior to the beta. | ||
| + | * 90044 Have the "Recent Edits" submission lists include a link to the same display used for approval, in order to view the change made or proposed. | ||
| + | |||
| + | ==[[ISFDB:Policy]]== | ||
| + | Review and clean up our [[ISFDB:Policy|Policy statement]] to see if there are any major outstanding issues that may result in new editors trying to add "wrong" data to the database. [[User:Ahasuerus|Ahasuerus]] 11:05, 30 Nov 2006 (CST) | ||
Revision as of 12:31, 16 December 2006
Since we are not planning to limit editor activity, there are no recruitment goals for number of editors. We will simply open up for editing, and will remain in beta until we meet the exit criteria.
Goals
- Find outstanding bugs
- get confidence there are no dataloss bugs left
- understand how editors are actually going to focus -- are the project pages what they need to manage their data, for example, and will they need something like a watchlist.
- get input on prioritizing next features
- prove that data really does (a) get added, (b) gets cleaned up, and (c) stays cleaned up
Exit Criteria
For the beta to conclude, there must be no known dataloss bugs, and no known bugs which cause software crashes.
In addition, consensus must be reached among editors that the software provides sufficient support for editors to be interested in contributing. The criteria the editors will use are to be determined by them, but are likely to include:
- The interface is sufficiently easy to use
- Help files and support are available to answer questions about how to achieve certain tasks
- The system is sufficiently reliable
- They are confident that the work they do is stable against vandalism, and incorrect edits.
"Sufficiently" in the criteria above means that the system is good enough that editors are not discouraged from being active by any flaws.
Showstopper Bug Fixes
- 10014 - Unicode hell.
- 10027 - Editing reviews and interviews loses data.
- 10032 - Variant title hilarity.
- 10039 - Chapterbook support.
Wiki
The following tasks within the wiki should be completed before we go live on the beta.
- Clean out old help files. Done.
- Make a pass through the project pages and see if we can improve the usability of the overall organization. It's apparent from various messages on the portal that it is not always easy to locate the right project for a task or issue. Awaiting consensus this is complete.
- Add remaining help pages; improve existing ones. Largely complete, but further improvements are certainly possible. Done as far as needed for Beta.
- Agree on landing page for beta recruits; write that page.
- Agree on remaining features to be implemented. In process; see below.
Remaining features
This section lists features that will be implemented prior to the beta.
- 90044 Have the "Recent Edits" submission lists include a link to the same display used for approval, in order to view the change made or proposed.
ISFDB:Policy
Review and clean up our Policy statement to see if there are any major outstanding issues that may result in new editors trying to add "wrong" data to the database. Ahasuerus 11:05, 30 Nov 2006 (CST)