Kexi/Junior Jobs: Difference between revisions

From KDE Community Wiki
Line 17: Line 17:
*[open, needs specification] Look at competing software, note down all possible features, prioritize them, define dependencies between them, requirements, development cost, feasibility/risks.
*[open, needs specification] Look at competing software, note down all possible features, prioritize them, define dependencies between them, requirements, development cost, feasibility/risks.
*[open, needs specification] Unit tests, using the QtTest module
*[open, needs specification] Unit tests, using the QtTest module
*[assigned] [[/Improve handling permission error on database creation/]]
*[done] <strike>[[/Improve handling permission error on database creation/]]</strike>
*[assigned] [[/Ask for password when Test Connection/|Ask for password when Test Connection is clicked]]
*[done] <strike>[[/Ask for password when Test Connection/|Ask for password when Test Connection is clicked]]</strike>
*[open, needs specification] [[/Use KWallet for password storage/]]
*[open, needs specification] [[/Use KWallet for password storage/]]



Revision as of 22:51, 18 November 2014

Introduction

If you want to join the Kexi project by trying your luck in simpler tasks, junior jobs are for you. Tasks listed here is not the full list. Please contact the Kexi team) before start hacking. Tasks have to be assigned for you to make sure no two contributors perform the same work. Have fun!

We try to explain the tasks in details but you may have extra questions. That is great, send us the questions via email, chat with us, or use the forums.

And you can propose tasks for you of course, remember!

Note: Entries at bugs.kde.org marked as Junior Jobs: [1]

Alternatively, see the list of all unresolved Kexi bugs+wishes+tasks.

Below we categorized some larger tasks:

General

Tables

Queries

Forms

Reports

Migration

Other

Non-programming

Links