Help others to learn
There are many ways that you can contribute to Kom and the community. Fortunately most of these require little more than an interest in Kom and helping other members of the community.
Partecipate in Mailing lists
There are community mailing lists you can join to discuss Kom. The lists are an excellent source for users and contributors interested in having technical discussions, answering questions, or resolving potential issues for newcomers.
Help promote Kom by using your blog, Twitter, Facebook, or submitting an article to your favorite local magazine. If you are a member of a different open source community, why not mention Kom on their discussion forums or at conferences? If you love Kom, don't hold back — speak up! The more developers use Kom, the more bugs will be caught, the more features will be added, the more visible the project, and the more benefits the community will get.
Link to kom.kaeilos.com
The success of any open source project depends on the number of people who use the product and contribute back to the project. By linking to kom.kaeilos.com, you increase the chances of a new user or contributor finding out about the project and joining the community.
File a bug report
Bug reports take little time to file and are very helpful to developers. This is one of the easiest contributions you can make. When you discover a problem with Kom, please report it. Our preference as a community is to have you first report the bug to the mailing list (coming soon) so that other community members can provide some first-level help and triage. Often times there may already be a solution or answer to your problem.
Help us triage existing bug reports
Kom gets a pretty steady stream of bug reports. While we do our best to validate each report as comes in, we can't possibly prevent every instance of duplicated bug reports, bugs that have been fixed without anybody noticing, and so on in our issue tracker. One way you can help us is by cruising through some of our issues in need of triage, reading the bug reports, and attempting to verify that the bug still exists in Kom. If you discover some additional information along the way that you think will be useful to the developers, annotate the issue and share what you've learned.
Write a test or reproduction script
A well-written bug report is invaluable to developers. A reproduction recipe script, however, is worth a hundred well-written reports. Nothing helps developers understand what you were doing when something went wrong better than being able to do exactly that something themselves and see the same results.
Submit a patch
The open-source adage "Patches welcome" may show up most frequently as a thread-killing retort to mailing list trolls, but at the heart of the statement are two quite genuine ideals: software code doesn't write itself, and projects generally really do want as many people as possible to help write that code. The Kom project is no different. We've accepted and applied countless patch contributions, and we hope to always have a constant stream of them.
Become a committer and commit code directly
Developers with a long history of submitting high-quality patches can gain direct commit rights. This is obviously beneficial to the developer community — where quality developers are concerned, "the more, the merrier"! But never underestimate how valuable this experience can be to you personally and professionally, too.