luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-01-25 21:46:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: The mailing lists are no more

Browse Source 
Don't send people to mailing lists that do not exist any more. We moved
to Discourse.
This commit is contained in:
Emmanuele Bassi 2019-07-23 11:05:17 +01:00
parent 8c5a14adf3
commit 11715d17db
1 changed files with 7 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
CONTRIBUTING.md
View File

@ -23,10 +23,7 @@ Please, do not use the issue tracker for support questions. If you have
questions on how to use GLib effectively, you can use: questions on how to use GLib effectively, you can use:
- the `#gtk` IRC channel on irc.gnome.org - the `#gtk` IRC channel on irc.gnome.org
- the [gtk](https://mail.gnome.org/mailman/listinfo/gtk-list) mailing list, - the [`glib` tag on GNOME's Discourse](https://discourse.gnome.org/tags/glib)
for general questions on GLib
- the [gtk-devel](https://mail.gnome.org/mailman/listinfo/gtk-devel-list)
mailing list, for questions on developing GLib itself
You can also look at the [`glib` tag on Stack You can also look at the [`glib` tag on Stack
Overflow](https://stackoverflow.com/questions/tagged/glib). Overflow](https://stackoverflow.com/questions/tagged/glib).
@ -101,10 +98,9 @@ full branch coverage of the new code. GLib’s CI system generates code coverage
reports which are viewable for each merge request. reports which are viewable for each merge request.
If proposing a large feature or change, it’s better to discuss it (on the If proposing a large feature or change, it’s better to discuss it (on the
`#gtk` IRC channel or on the `#gtk` IRC channel or on [Discourse](https://discourse.gnome.org) before
[gtk-devel](https://mail.gnome.org/mailman/listinfo/gtk-devel-list) mailing putting time into writing an actionable issue — and certainly before putting
list) before putting time into writing an actionable issue — and certainly time into writing a merge request.
before putting time into writing a merge request.
## Your first contribution ## Your first contribution
@ -180,9 +176,9 @@ of each commit between at least two people.
With each code review, we intend to: With each code review, we intend to:
0. Identify if this is a desirable change or new feature. Ideally for larger 0. Identify if this is a desirable change or new feature. Ideally for larger
features this will have been discussed (in an issue, on IRC, or on the features this will have been discussed (in an issue, on IRC, or on Discourse)
mailing list) already, so that effort isn’t wasted on putting together merge already, so that effort isn’t wasted on putting together merge requests
requests which will be rejected. which will be rejected.
0. Check the design of any new API. 0. Check the design of any new API.
0. Provide realistic estimates of how long a review might take, if it can’t 0. Provide realistic estimates of how long a review might take, if it can’t
happen immediately. happen immediately.