ISFDB:Beta

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.

Bugs to fix before beta exit

This section lists bugs which must be fixed before the beta can be completed.

Showstopper Bug Fixes

• None.

Wiki

The following tasks within the wiki should be completed before we go live on the beta.

• Agree on landing page for beta recruits; write that page.

Remaining features

There are no features remaining to be implemented prior to the beta.

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)