加入我們
如何幫忙 Kate 開發
If you want to help us develop Kate, KWrite or KatePart, you should join our mailing list. Contacting us at #kate on irc.libera.chat is also a good idea, we are always happy to help you get started.
如何編譯 Kate
在已更新的 Linux 發行版上編譯 Kate 很容易，我們也專門為此提供了編譯 Kate 及必要的依賴關係的教學。對於其他作業系統，同一個頁面上也有更多資訊的連結。
貢獻程式碼
For contributions, the best way to hand them in is via our GitLab instance invent.kde.org.
How to set it up and use it is documented in the invent.kde.org documentation.
Just open a new merge request there for Kate. For more details about this, refer to this blog post.
If you want to get an overview about already accepted patches to get a feel how the process works, take a look at our merge requests page. Visiting some of these accepted requests might help to have a better grasp of project's workings.
工作區域
主要的工作區域是程式的部分，但就算您不是程式開發者您也可以在其他區域幫助我們：
- 撰寫並維護說明文件。
- 撰寫並維護語法突顯檔案。
- 撰寫並維護指令稿。
- 維護錯誤報告。
- 提供我們有用的回饋。
- 透過幫助 KDE 來幫助我們。作為 KDE 的一部分，KDE 的進步也會使 Kate 改善，不只是 KDE 所提供的整合，來自 KDE 翻譯團隊的幫助也是極有意義的。
C/C++ 程式碼風格標準
The code in our repositories shall follow the style described for KDE Frameworks.
The CMake tooling we use will setup appropriate pre-commit hooks to ensure this style using clang-format.
為您的程式碼加上說明
We use Doxygen syntax to document code, and it’s nice to document everything, even private code, since other people than you might get to work on it or just try to understand it.
For comments inside of functions, C++ single-line comments are preferred over multi-line C comments.
Good starting points
You can take a look at our current list of issues, perhaps you are interested in taking care of one.