Get Help / User Support
- join the development team!
- help translating the language packs
- test KompoZer, report bugs and suggest new features
- contact the team on the #kompozer IRC channel
- Fabien Cazenave aka Kazé
- Cédric Corazza
- Frédéric Chateaux
Special thanks to…
- Daniel Glazman and Linspire for developing Nvu, without which KompoZer would not exist;
- the whole Mozilla team for developing Composer, without which Nvu would not exist;
- Vivien Nicolas (Fennec contributor) for his phpStreamConverter component;
- Motohiko for fixing the extension manager in the 0.7 branch;
- Paul Hammant for setting up the SVN tree;
- Tony Yarusso and the MOTU team for helping me with the Ubuntu package;
- Giuseppe Iuculano for hosting the mailing lists and providing security fixes;
- all localization teams and support forum members;
- all users who donated to keep this project running.
Why call it «KompoZer» instead of «Nvu»?
Because “Nvu and the Nvu logo are trademarks of Linspire Inc.”
As Linspire stopped the development of Nvu, there is no legal way to correct any bug in Nvu.
Why is it only a 0.x version?
Because for 99% of the developers in the world, including myself, a «1.0» version means it's ready for professional use. Nvu was very far from that.
KompoZer is already much more stable than Nvu, but there are some bugfixes and features that are necessary before we can decently call it a 1.0 version.
Is there a development roadmap?
- 0.7 branch: fix most of the CSS editor's bugs;
- 0.8 branch: implement a decent site manager;
- 0.9 branch: fix most bugs of the HTML editor, especially the code output.
Sorry, no ETA. KompoZer 1.0 will be released when it’s ready.
How can I help this project?
- provide support in user forums;
- report bugs of suggest requests for enhancements (RFE);
- contribute code patches or binary builds (a steady MacOS X contributor is wanted);
- translate KompoZer and contribute langpacks;
and of course, you can donate to support KompoZer's development.
Please copy these files on your website, rather than using them from here.
You can reach KompoZer contributors in the #kompozer IRC channel.
You can also drop a message to the lead developer on his weblog.