Commit bb4444cc authored by Emmanuele Bassi's avatar Emmanuele Bassi

docs: Update the links for Clutter resources

We moved to GitLab.
parent 369de5f4
......@@ -12,61 +12,61 @@ Requirements
Clutter currently requires:
* [GLib](http://git.gnome.org/browse/glib)
* [JSON-GLib](http://git.gnome.org/browse/json-glib)
* [Atk](http://git.gnome.org/browse/atk)
* [Cairo](http://cairographics.org)
* [Pango](http://git.gnome.org/browse/pango)
* [Cogl](http://git.gnome.org/browse/cogl)
* [GLib](https://gitlab.gnome.org/GNOME/glib)
* [JSON-GLib](https://gitlab.gnome.org/GNOME/json-glib)
* [Atk](https://gitlab.gnome.org/GNOME/atk)
* [Cairo](http://cairographics.org)
* [Pango](https://gitlab.gnome.org/GNOME/pango)
* [Cogl](https://gitlab.gnome.org/GNOME/cogl)
On X11, Clutter depends on the following extensions:
* XComposite
* XDamage
* XExt
* XInput 2.x
* XKB
* XComposite
* XDamage
* XExt
* XInput 2.x
* XKB
If you are building the API reference you will also need:
* [GTK-Doc](http://git.gnome.org/browse/gtk-doc)
* [GTK-Doc](https://gitlab.gnome.org/GNOME/gtk-doc)
If you are building the additional documentation you will also need:
* xsltproc
* jw (optional, for generating PDFs)
* xsltproc
* jw (optional, for generating PDFs)
If you are building the Introspection data you will also need:
* [GObject-Introspection](http://git.gnome.org/browse/gobject-introspection)
* [GObject-Introspection](https://gitlab.gnome.org/GNOME/gobject-introspection)
Resources
---------
The official Clutter website is:
http://www.clutter-project.org/
- https://www.clutter-project.org/
The API references for the latest stable release are available at:
https://developer.gnome.org/clutter/stable/
- https://developer.gnome.org/clutter/stable/
The Clutter Cookbook is available at:
https://developer.gnome.org/clutter-cookbook/
- https://developer.gnome.org/clutter-cookbook/
New releases of Clutter are available at:
https://download.gnome.org/sources/clutter/
- https://download.gnome.org/sources/clutter/
To subscribe to the Clutter mailing lists and read the archives, use the
Mailman web interface available at:
https://mail.gnome.org/mailman/listinfo/clutter-list
- https://mail.gnome.org/mailman/listinfo/clutter-list
New bug page on Bugzilla:
New bugs should be filed on GitLab:
https://bugzilla.gnome.org/enter_bug.cgi?product=clutter
- https://gitlab.gnome.org/GNOME/clutter/issues/new
Clutter is licensed under the terms of the GNU Lesser General Public
License, version 2.1 or (at your option) later: see the `COPYING` file
......@@ -78,9 +78,11 @@ Building and Installation
To build Clutter from a release tarball, the usual autotool triad should
be followed:
1. ./configure
2. make
3. make install
```sh
$ ./configure
$ make
# make install
```
To build Clutter from a Git clone, run the `autogen.sh` script instead
of the configure one. The `autogen.sh` script will run the configure script
......@@ -109,40 +111,40 @@ only used on the Git repository.
Contributing
------------
If you want to hack on and improve Clutter check the `HACKING` file for
general implementation guidelines, and the `HACKING.backends` for
backend-specific implementation issues.
If you want to hack on and improve Clutter check the
[HACKING](./docs/HACKING) file for general implementation guidelines, and
the [HACKING.backends](./docs/HACKING.backends) for backend-specific
implementation issues.
The `CODING_STYLE` file contains the rules for writing code conformant to
the style guidelines used throughout Clutter. Remember: the coding style
is mandatory; patches not conforming to it will be rejected by default.
The [CODING STYLE](./docs/CODING_STYLE) file contains the rules for writing
code conformant to the style guidelines used throughout Clutter. Remember:
the coding style is mandatory; patches not conforming to it will be rejected
by default.
The usual workflow for contributions should be:
1. Fork the repository
2. Create a branch (`git checkout -b my_work`)
3. Commit your changes (`git commit -am "Added my awesome feature"`)
4. Push to the branch (`git push origin my_work`)
5. Create an [Bug][bugzilla-clutter] with a link to your branch
6. Sit back, relax and wait for feedback and eventual merge
1. Fork the repository
2. Create a branch (`git checkout -b my_work`)
3. Commit your changes (`git commit -am "Added my awesome feature"`)
4. Push to the branch (`git push origin my_work`)
5. Open a new merge request
6. Sit back, relax and wait for feedback and eventual merge
Bugs
----
Bugs should be reported to the Clutter Bugzilla at:
Bugs should be reported here:
https://bugzilla.gnome.org/enter_bug.cgi?product=clutter
You will need a Bugzilla account.
- https://gitlab.gnome.org/GNOME/clutter/issues/new
In the report you should include:
* what system you're running Clutter on;
* which version of Clutter you are using;
* which version of GLib and OpenGL (or OpenGL ES) you are using;
* which video card and which drivers you are using, including output of
glxinfo and xdpyinfo (if applicable);
* how to reproduce the bug.
* what system you're running Clutter on;
* which version of Clutter you are using;
* which version of GLib and OpenGL (or OpenGL ES) you are using;
* which video card and which drivers you are using, including output of
glxinfo and xdpyinfo (if applicable);
* how to reproduce the bug.
If you cannot reproduce the bug with one of the tests that come with Clutter
source code, you should include a small test case displaying the bad
......@@ -152,4 +154,3 @@ If the bug exposes a crash, the exact text printed out and a stack trace
obtained using gdb are greatly appreciated.
[building-clutter]: https://wiki.gnome.org/Projects/Clutter/Building
[bugzilla-clutter]: https://bugzilla.gnome.org/enter_bug.cgi?product=clutter
......@@ -15,7 +15,7 @@
<homepage rdf:resource="http://www.clutter-project.org" />
<license rdf:resource="http://usefulinc.com/doap/licenses/lgpl" />
<bug-database rdf:resource="http://bugzilla.gnome.org/enter_bug.cgi?product=clutter"/>
<bug-database rdf:resource="https://gitlab.gnome.org/GNOME/clutter/issues"/>
<download-page rdf:resource="http://download.gnome.org/sources/clutter" />
<mailing-list rdf:resource="mailto:clutter-devel-list@clutter-project.org" />
......@@ -85,8 +85,8 @@
<repository>
<GitRepository>
<browse rdf:resource="http://git.gnome.org/browse/clutter/"/>
<location rdf:resource="git://git.gnome.org/clutter"/>
<browse rdf:resource="https://gitlab.gnome.org/GNOME/clutter"/>
<location rdf:resource="https://gitlab.gnome.org/GNOME/clutter.git"/>
</GitRepository>
</repository>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment