Kexi/Getting Started

From KDE Community Wiki
Revision as of 15:16, 9 August 2011 by Jstaniek (talk | contribs)

Ways for contribution

  • Tester
  • Developer
  • Promoter

Communication channels

See Contact.

Common tools

Specific for Developers

Specific for non-Developers

  • Starting: "I am not developer, I cannot or do not like to program. How can I help?"
  • For testing, possibly the newest Kexi version should be used
  • After starting Kexi for the first time, a new empty database can be created. Handbook (old) can be used to get information how to do this.
  • To test support for server databases, access to a server is needed. It can be the same computer as the used desktop or laptop machine, but database server software have to be installed on it. Users that lack knowledge on how to do this should ask someone (e.g. a network administrator) to do so.
  • Beginner users may also want to use example database as a reference.

Other information

  • These databases are saved in self-contained files for your convenience:
  • Example databases on a database server (MySQL, PostgreSQL) useful to test server connections. Will be provided, more information is PLANNED here. Please offere a server space if you can. Please provide test databases if you have such (must be legal)..

<a class="totoc" href="[email protected]#__TOC">^ toc</a><a name="What_to_Test_"></a>

What to Test?

You can:

  • test for crashes or misbehaviour
  • locate places where Kexi is ineffective (e.g. for large data sets) or hangs
  • test particular functionality and propose entensions, e.g. data importing functions
  • compare the application to the competition and identify the most expected features that Kexi currently lacks
  • test for usability
  • test for accessibility
  • test for localizations issues, including support for right-to-left languages, etc. (note: errors in translations to other languages should be reported to a particular <a href="http://i18n.kde.org/teams/">translation team<img src="images/external.gif" align="top" alt="" border="0"/></a>)
  • locate errors in the <a href="[email protected]">Kexi Handbook</a>, report unclear or incomplete paragraphs, outdated or missing screenshots (the above note about translation teams also apply to translated documentation)

<a class="totoc" href="[email protected]#__TOC">^ toc</a><a name="How_to_Report_Bugs"></a>

How to Report Bugs