Difference between revisions of "ISFDB:Beta"

From ISFDB
Jump to navigation Jump to search
(→‎Wiki: Remove landing page task)
(changed a "which" to "that")
Line 24: Line 24:
  
 
==Exit Criteria==
 
==Exit Criteria==
For the beta to conclude, there must be no known dataloss bugs, and no known bugs which cause software crashes.
+
For the beta to conclude, there must be no known dataloss bugs, and no known bugs that 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:
 
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:

Revision as of 13:52, 1 January 2007

Beta participation

Welcome to the beta release of public editing of the ISFDB database.

With this release, the ISFDB is available for anyone to edit. If you have sf or fantasy books or magazines on your shelves, and a few minutes to spare, you can help expand and improve our coverage of the field.

The following links may be useful to you.

  • Help:Getting Started. A quick guide to getting started entering useful data.
  • Help:Contents. The main help page. Links to FAQs, "How to" pages, and detailed help.
  • Special:Listadmins. A list of moderators. Leave a message on the talk page of any of them, and you'll get help. You might wnat to check their contributions page to see who has been active recently, just so you'll get a quick response.
  • Bibliographic Projects in Progress. A good place to find ways to contribute.

The rest of this page is devoted to the beta itself; its goals and any current issues. Please feel free to contribute and ask questions anywhere on the ISFDB Wiki.

Goals

Note: 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.

  • Find outstanding software bugs
  • Get confidence there are no dataloss bugs left
  • Understand how editors are actually going to focus. For example, are the project pages what they need to manage their data? 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 that 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.

None.

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)