Mailing lists and bug reports 3 Mailing lists and bug reports Mailing lists and bug reports Getting help with GTK If you encounter a bug, misfeature, or missing feature in GTK, please file a bug report on our GitLab project. You should also file issues if the documentation is out of date with the existing API, or unclear. Don't hesitate to file a bug report, even if you think we may know about it already, or aren't sure of the details. Just give us as much information as you have, and if it's already fixed or has already been discussed, we'll add a note to that effect in the report. The bug tracker should definitely be used for feature requests, it's not only for bugs. We track all GTK development in GitLab, to ensure that nothing gets lost. If you develop a bugfix or enhancement for GTK, please open a merge request in GitLab as well. You should not attach patches to an issue, or describe the fix as a comment. Merge requests allow us to build GTK with your code applied, and run the test suite, on multiple platforms and architectures, and verify that nothing breaks. They also allow us to do proper code reviews, so we can iterate over the changes. You should follow the contribution guide for GTK, available on GitLab. If you want to discuss your approach before or after working on it, send and email to gtk-devel-list@gnome.org. You should not send a patch to the mailing list, as it will inevitably get lost, or forgotten. Always open a merge request. There are several mailing lists dedicated to GTK and related libraries. Discussion of GLib, Pango, and ATK in addition to GTK proper is welcome on these lists. You can subscribe or view the archives of these lists on http://mail.gnome.org. If you aren't subscribed to the list, any message you post to the list will be held for manual moderation, which might take some days to happen. gtk-list@gnome.org gtk-list covers general GTK topics; questions about using GTK in programs, GTK from a user standpoint, announcements of GTK-related projects such as themes or GTK modules would all be on-topic. The bulk of the traffic consists of GTK programming questions. gtk-app-devel-list@gnome.org gtk-app-devel-list covers writing applications in GTK. It's narrower in scope than gtk-list, but the two lists overlap quite a bit. gtk-app-devel-list is a good place to ask questions about GTK programming. gtk-devel-list@gnome.org gtk-devel-list is for discussion of work on GTK itself, it is not for asking questions about how to use GTK in applications. gtk-devel-list is appropriate for discussion of patches, bugs, proposed features, and so on. gtk-i18n-list@gnome.org gtk-i18n-list is for discussion of internationalization in GTK; Pango is the main focus of the list. Questions about the details of using Pango, and discussion of proposed Pango patches or features, are all on topic. gtk-doc-list@gnome.org gtk-doc-list is for discussion of the gtk-doc documentation system (used to document GTK), and for work on the GTK documentation.