luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-03 17:56:17 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'contributing-fixes' into 'master'

Browse Source 
Remove mentions of mailing lists from the documentation

See merge request GNOME/glib!1002
This commit is contained in:
Philip Withnall 2019-08-05 10:20:40 +00:00
commit 37b2093f28
6 changed files with 25 additions and 70 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:
- the `#gtk` IRC channel on irc.gnome.org
- the [gtk](https://mail.gnome.org/mailman/listinfo/gtk-list) mailing list,
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
- the [`glib` tag on GNOME's Discourse](https://discourse.gnome.org/tags/glib)
You can also look at the [`glib` tag on Stack
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.
If proposing a large feature or change, it’s better to discuss it (on the
`#gtk` IRC channel or on the
[gtk-devel](https://mail.gnome.org/mailman/listinfo/gtk-devel-list) mailing
list) before putting time into writing an actionable issue — and certainly
before putting time into writing a merge request.
`#gtk` IRC channel or on [Discourse](https://discourse.gnome.org) before
putting time into writing an actionable issue — and certainly before putting
time into writing a merge request.
## Your first contribution
@ -180,9 +176,9 @@ of each commit between at least two people.
With each code review, we intend to:
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
mailing list) already, so that effort isn’t wasted on putting together merge
requests which will be rejected.
features this will have been discussed (in an issue, on IRC, or on Discourse)
already, so that effort isn’t wasted on putting together merge requests
which will be rejected.
0. Check the design of any new API.
0. Provide realistic estimates of how long a review might take, if it can’t
happen immediately.

20
README.md
View File

@ -1,24 +1,16 @@
General Information
===================
GLib is the low-level core
library that forms the basis for projects such as GTK+ and GNOME. It
provides data structure handling for C, portability wrappers, and
interfaces for such runtime functionality as an event loop, threads,
dynamic loading, and an object system.
GLib is the low-level core library that forms the basis for projects such
as GTK and GNOME. It provides data structure handling for C, portability
wrappers, and interfaces for such runtime functionality as an event loop,
threads, dynamic loading, and an object system.
The official download locations are:
ftp://ftp.gtk.org/pub/glib
http://download.gnome.org/sources/glib
https://download.gnome.org/sources/glib
The official web site is:
http://www.gtk.org/
Information about mailing lists can be found at
http://www.gtk.org/mailing-lists.php
To subscribe, send mail to gtk-list-request@gnome.org
with the subject "subscribe".
https://www.gtk.org/
Installation
============

49
docs/reference/glib/resources.xml
View File

@ -53,8 +53,8 @@ under those terms.
</para>
<para>
If you want to discuss your branch before or after developing it, mail
<ulink url="mailto:gtk-devel-list@gnome.org">gtk-devel-list@gnome.org</ulink>.
If you want to discuss your branch before or after developing it, open a
topic on <ulink url="https://discourse.gnome.org/tags/glib">Discourse</ulink>.
But be sure to create the GitLab merge request as well; if the branch is only
on the list and not in GitLab, it's likely to slip through the cracks.
</para>
@ -62,48 +62,13 @@ on the list and not in GitLab, it's likely to slip through the cracks.
</refsect1>
<refsect1>
<title>Mailing lists</title>
<title>Discussions and user questions</title>
<para>
There are several mailing lists dedicated to GTK+ and related
libraries. Discussion of GLib generally takes place on these lists.
You can subscribe or view the archives of these lists on
<ulink url="http://mail.gnome.org">http://mail.gnome.org</ulink>.
</para>
<para>
<variablelist>
<varlistentry>
<term><ulink url="mailto:gtk-list@gnome.org">gtk-list@gnome.org</ulink></term>
<listitem><para>
gtk-list covers general GTK+ (and GLib) topics; questions about using GLib
in programs, GLib from a user standpoint, announcements of GLib-related projects
would all be on-topic. The bulk of the traffic consists of GTK+ programming
questions.
</para></listitem>
</varlistentry>
<varlistentry>
<term><ulink url="mailto:gtk-devel-list@gnome.org">gtk-devel-list@gnome.org</ulink></term>
<listitem><para>
gtk-devel-list is for discussion of work on GTK+ (and GLib) itself, it is
<emphasis>not</emphasis> for asking questions about how to use GTK+ (or GLib)
in applications. gtk-devel-list is appropriate for discussion of branches,
bugs, proposed features, and so on.
</para></listitem>
</varlistentry>
<varlistentry>
<term><ulink url="mailto:gtk-doc-list@gnome.org">gtk-doc-list@gnome.org</ulink></term>
<listitem><para>
gtk-doc-list is for discussion of the <application>gtk-doc</application>
documentation system (used to document GTK+ and Glib), and for work on the GTK+
(and GLib) documentation.
</para></listitem>
</varlistentry>
</variablelist>
The <ulink url="https://gitlab.gnome.org/GNOME/glib/issues">GLib issue tracker</ulink>
is meant for discussions with actionable topics. If you want to ask a question
about using GLib, or discuss new features, you should use
<ulink url="https://discourse.gnome.org/tags/glib">the glib tag on Discourse</ulink>.
</para>
</refsect1>

2
glib.doap
View File

@ -16,7 +16,7 @@
<license rdf:resource="http://usefulinc.com/doap/licenses/lgpl" />
<bug-database rdf:resource="https://gitlab.gnome.org/GNOME/glib/issues/new"/>
<download-page rdf:resource="http://download.gnome.org/sources/glib/" />
<mailing-list rdf:resource="mailto:gtk-devel-list@gnome.org" />
<mailing-list rdf:resource="https://discourse.gnome.org/tags/glib/" />
<category rdf:resource="http://api.gnome.org/doap-extensions#core" />
<programming-language>C</programming-language>

2
gobject/gsignal.c
View File

@ -126,7 +126,7 @@
*/
#define REPORT_BUG "please report occurrence circumstances to gtk-devel-list@gnome.org"
#define REPORT_BUG "please report occurrence circumstances to https://gitlab.gnome.org/GNOME/glib/issues/new"
/* --- typedefs --- */
typedef struct _SignalNode SignalNode;

4
gobject/gtype.h
View File

@ -198,7 +198,9 @@ G_BEGIN_DECLS
/* Reserved fundamental type numbers to create new fundamental
* type IDs with G_TYPE_MAKE_FUNDAMENTAL().
* Send email to gtk-devel-list@gnome.org for reservations.
*
* Open an issue on https://gitlab.gnome.org/GNOME/glib/issues/new for
* reservations.
*/
/**
* G_TYPE_FUNDAMENTAL_SHIFT: