Kexi/Getting Started: Difference between revisions

Revision as of 15:23, 9 August 2011

Ways for contribution

Tester
Developer
Promoter

Communication channels

See Contact.

Common tools

Reporting issues, wishes or bugs
Download Calligra to run it

Specific for Developers

Contributing a Patch (applies to all Calligra apps)
Calligra API reference
Building Kexi as part of Calligra (other Calligra apps can be built or only Kexi)
Junior Jobs

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.
Example databases on a database server (MySQL, PostgreSQL) useful to test server connections will be provided later after contributor provides a server space.
Beginner users may also want to use example database as a reference.

Other information

What do testing means?
- Identifying crashes or misbehaviour
- Locating places where Kexi is inefficient (e.g. for large data sets) or hangs
- Checking particular functionality and proposing extensions, e.g. data importing functions
- Comparing the application to the competition and identify the most desired features that Kexi currently lacks
- Testing for usability, e.g. identifying functions that are hard to use or locate
- Testing for accessibility, e.g. identify areas of the application that are not clearly visible on non-default color settings or cannot be used without mouse
- Testing for localisations issues, including support for right-to-left languages, etc. (note: errors in translations to other languages should be reported to a particular translation team)
- Locating 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)

How to Report Bugs

Use the wizard at <a href="http://bugs.kde.org/wizard.cgi">bugs.kde.org<img src="images/external.gif" align="top" alt="" border="0"/></a> (KDE Bug Tracking System) to submit a bug report or a wish. First check using <a href="http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kexi&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bugidtype=include&bug_id=&votes=&emailtype1=exact&email1=&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=all+kexi+bugs">this query tool<img src="images/external.gif" align="top" alt="" border="0"/></a> if there's already similar bug or wish reported. Carefully read advices on the wizard's pages. Specify your operating system version and Kexi version. Attach an example file (or paste a link to it if the file is large). This helps a lot, and you will get faster and more accurate response.
Related KDE Bug Tracking System's tools:
- <a href="http://bugs.kde.org/component-report.cgi?product=kexi">Report Count by Kexi's Component and Severity<img src="images/external.gif" align="top" alt="" border="0"/></a>
- <a href="http://bugs.kde.org/reports.cgi?product=kexi&output=most_doomed&datasets=NEW%3A&datasets=ASSIGNED%3A&datasets=REOPENED%3A&datasets=UNCONFIRMED%3A&links=1&banner=1&quip=0">Kexi chart for bugs ownership<img src="images/external.gif" align="top" alt="" border="0"/></a>
<a href="http://kexi-project.org/contact.html">Contact Kexi developers</a> by mail or by visiting #kexi and #koffice IRC channels.

@@ Line 29: / Line 29: @@
 *[http://techbase.kde.org/Contribute Contribution options described on KDE Techbase]
-What to Test?
+*What do testing means?
-<li> test for crashes or misbehaviour
+**Identifying crashes or misbehaviour
+**Locating places where Kexi is inefficient (e.g. for large data sets) or hangs
-<li> locate places where Kexi is ineffective (e.g. for large data sets) or hangs
+**Checking particular functionality and proposing extensions, e.g. data importing functions
-<li> test particular functionality and propose entensions, e.g. data importing functions
+**Comparing the application to the competition and identify the most desired features that Kexi currently lacks
-<li> compare the application to the competition and identify the most expected features that Kexi currently lacks
+**Testing for usability, e.g. identifying functions that are hard to use or locate
-<li> test for usability
+**Testing for accessibility, e.g. identify areas of the application that are not clearly visible on non-default color settings or cannot be used without mouse
-<li> test for accessibility
+**Testing for localisations issues, including support for right-to-left languages, etc. (note: errors in translations to other languages should be reported to a particular [http://i18n.kde.org/teams/ translation team])
-<li> 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>)
+**Locating 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)
-<li> 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)
 </ul>