Home

Hi Folks,

This is the wiki for the official bugtracker and development hub for the KVIrc project.

Here you can report bugs or propose a new feature by submitting a new ticket, browse or check the git commits, and most importantly you can submit your code contributions via pull requests.

Bugreport (tickets)

We definitely moved our development efforts to the new 4.3 branch based on Qt4/Qt5; KVIrc 3.4.2 has been deprecated and is no longer officially supported.

We decided to introduce some policy rules on tickets, too; every bug reported by one user will have to be confirmed or reproduced by other users in an initial period (usually 3/4 weeks). If a ticket is not reproducible by nobody after that time, it will be closed as "works for me".

So, the first need for us is being able to reproduce the bug: take care to describe the necessary steps needed to trigger the fault condition.

In order to make things clear, please add the right labels to the report, so the ticket will be cataloged and we'll know which ticket takes the precedence over others.

If you are reporting a bug against a development version (currently KVIrc 4.3), please add in the description of the bug the number of the git revision.

While reporting a crash, please tell us ''what you did to cause'' the crash. A ''list of steps on how to reproduce'' it would be really helpful. It would also be nice for us ''if you can attach a backtrace'' of the crash. This will speed up our work in solving the bug. If you don't know how to create a backtrace, you can get some useful information to start here: Useful backtrace

When including a stack trace, use this syntax to make the report readable:

```
stack trace goes here
```

If you're going to ask for a new feature, please remember that we're going to implement feature requests only in the current development version, so any already existing, or new feature requests will be automatically re-targeted accordingly.

Ticket Validity

If your ticket matches one of these cases, it will be closed immediately as "invalid":

• Duplicate report: the bug has already been reported in another ticket; if the ticket was already closed, reopen it
• Old KVIrc version: the bug is reported against an old KVIrc version (not the last official released 4.2 or a recent development snapshot)
• Bogus/without information: the ticket is as short as "I can't make it work" and offers no useful informations
• Foreign languages: we accept tickets in English only.

Documentation

• It's still a work-in-progress, where we'll keep some questions often asked in the IRC channel. FAQ
• The shortcuts are changed. If you're stuck with them, keep an eye on Keyboard Shortcuts
• If you're searching for some info about the new KVIrc 4's KVS syntax: Porting Scripts To KVIrc 4

Submitting pull requests

As an independent developer or KVIrc user, you are encouraged to submit features, bugfixes, documentation changes, scripts, themes or other enhancements to be included in KVIrc's or associated repositories' source code by making a pull request.

Contributing code to KVIrc's repository contains a simplified set of guidelines to help you get started.