ebase Software Review & Testing

Welcome, and thanks for your interest in testing ebase software. As you may have heard, ebase is an all-volunteer effort. We're very appreciative of (and actually entirely reliant upon!) contributions from people like you. (If you'd like an evaluation copy of ebase so you can learn more about its features, please get one from the downloads page).

Our testing program has three goals:

  • Identify places where ebase can be improved, and gather community input on how improvements can best be made.
  • Develop online documentation (at this website), beginning with a comprehensive list of features, for users & future testers.
  • Enlarge our community of expert users, implementers, and developers who can support others in using ebase.

Resources you will need:

  • If you haven't done so already, get in touch with the review program coordinator, Allen Poole, to let him know you'll be providing input.
  • You'll need an account on the ebase community web site. If you don't have an account, contact the review program coordinator to get one. Only by logging in to your account at ebase.org will you be able to contribute content or comments to product documentation.
  • To file bug reports, you'll need an account on our bug tracking software, Bugzilla. If you don't have an account, contact the review program coordinator to get one. Once you're logged in to Bugzilla, you'll be able to generate bug reports automatically from within ebase.
    You may also use Bugzilla as a forum to describe new features you'd like to see added to ebase.
  • To communicate by email with other ebase reviewers, implementers, and developers, you'll need an account on the ebase developers' listserv. (Note that this is not the same as the ebase users' listserv.) If you're not subscribed to the developers@ebase.org list already, contact the review program coordinator to be added to the listserv. The developers' listserv is the forum for general discussion of ebase products from developers' & implementers' perspectives; posts there reach a wider audience than details tracked in Bugzilla.
  • Finally, you'll need an up-to-date version of the ebase material you'll review. If you're reviewing our new web site, you've arrived! This is it.
    Ordinarily, ebase software file downloads and installation instructions are available at the downloads page, but for alpha test versions, please email the review program coordinator for a private download link.

Once you have everything you need to participate in the review process, please proceed to the review procedures page below for specific instructions:

Resources you will need - draft comments

I know these instructions are tailored to be broad enough to include those of us who are not as technical, so...
1)In the second bullet, some folks may not know what a "feature request" might be. It took me a minute.
2)In the third bullet, how would I know if I need to communicate with other reviewers, developers, etc.? How do I know if I am subscribed to the list already? This is not only a comment for the draft instructions, but also a real question - I think I'm subscribed because I get emails with questions regarding ebase - is that what that means?

Made some changes

Thanks for your questions... please take a look & let me know if it's clearer now.

changes

much clearer now

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.