Calendar
Calendar application for GNOME
Contributing to Calendar is easy, and we really appreciate it. File bugs, attach patches, create mockups, and wait for review (ping the maintainers at #gnome-calendar if you think we took too long; note that multiple weeks can be normal to get a code review, however). There are no restrictions at all, and anyone can get involved with Calendar development. There are many ways to help:
Test, troubleshoot, triageWe have to ensure the quality of Calendar's code and behavior on a consistent basis, and we need to be able to have a clear "actionable" view of issues affecting the latest version. Can you easily find bugs? We certainly need testers! The very first step to help testing Calendar is installing the development version of Calendar. See the Download & Install page to get the nightly version (or to build it yourself). Then, to see what needs to be tested, see: issues tagged "needs retesting", "needs information", "needs diagnosis". |
CodeHave good coding abilities? We need you too! Calendar is written in C, and uses Evolution-Data-Server APIs. We highly recommend using GNOME Builder to develop Calendar. Use the Builder IDE to clone the repository and build the code, then start playing!See the issues tagged for newcomers and issues where extra help is wanted to find things to work on while getting accustomed to the project's codebase. For students looking for a GSoC project, you might also want to look at the GSoC tagged issues. Note that this does not necessarily mean we are able to participate in GSoC as a mentoring project in any given year (in 2023 we are not, for example). |
DesignThe Calendar team keeps constant contact with the Design team to ensure we always have a carefully crafted application. Sounds good? Help us with the design too! |
DocumentationNot everyone want to code. Do you perform well with the English language? Calendar surely needs your writing skills for documentation and translation! |