Commit ec62911e authored by Thibault Saunier's avatar Thibault Saunier Committed by Thibault Saunier

doc: Update HACKING file to reflect our move to gitlab

And recommend to follow the GNOME newcomer guide
parent 8e86c8d0
......@@ -532,7 +532,7 @@ class PitiviFlatpak: # pylint: disable=too-many-instance-attributes
venv.create(venv_path, with_pip=True)
activate_script = os.path.join(venv_path, "bin", "activate")
pip_modules = "git-phab pre-commit git-pylint-commit-hook git_pep8_commit_hook pylint"
pip_modules = "pre-commit git-pylint-commit-hook git_pep8_commit_hook pylint"
Console.message("Installing development tools in the Python virtual env: %s", pip_modules)
subprocess.check_call(
". %s && pip install -U %s" % (activate_script, pip_modules),
......
......@@ -4,21 +4,32 @@ short-description: Using the Pitivi development environment
# Hacking on Pitivi
*The easy way to setup the development environment is to follow the*
*[GNOME Newcomers guide](https://wiki.gnome.org/Newcomers/).*
*Make sure to use the right git repository:*
> **https://gitlab.gnome.org/GNOME/pitivi.git**
## Setting up advanced development environment
> NOTE: This way of setting the development environment is sensibly more complex
> but also more flexible than the one for newcomers. If you are a beginner
> or if you usually use [gnome-builder](https://wiki.gnome.org/Apps/Builder)
> as your main IDE, follow, as previously adviced, the
> [GNOME Newcomers guide](https://wiki.gnome.org/Newcomers/)
The official way of getting your environment up and running is by using
[flatpak](http://flatpak.org/). For this you need to
[install flatpak](http://flatpak.org/getting.html) on your system,
along with flatpak-builder. Note flatpak-builder might be provided by an
additional package on some distributions (such as Archlinux).
## Setting up the development environment
Create a development environment folder and get the [Pitivi source code](https://git.gnome.org/browse/pitivi/tree/) into it:
Create a development environment folder and get the [Pitivi source code](http://gitlab.gnome.org/GNOME/pitivi) into it:
```
$ mkdir pitivi-dev
$ cd pitivi-dev
$ git clone https://git.gnome.org/browse/pitivi
$ git clone https://gitlab.gnome.org/GNOME/pitivi.git
```
Whenever you want to hack on Pitivi, enter the development environment:
......@@ -42,7 +53,6 @@ By entering the development environment, you get:
for the dependencies, in `pitivi-dev/pitivi-prefix`
- a [Python virtual environment](http://docs.python-guide.org/en/latest/dev/virtualenvs/)
with development tools, such as
[git-phab](https://phabricator.freedesktop.org/diffusion/GITPHAB/#description) and
[pre-commit](http://pre-commit.com),
in `pitivi-dev/pitivi/build/flatpak/pyvenv`
- the [Meson build directory](http://mesonbuild.com/Quick-guide.html),
......
......@@ -20,7 +20,7 @@ we would recommend building from version control.
<homepage rdf:resource="http://www.pitivi.org/" />
<mailing-list rdf:resource="https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi" />
<download-page rdf:resource="http://ftp.gnome.org/pub/GNOME/sources/pitivi/" />
<bug-database rdf:resource="https://phabricator.freedesktop.org/tag/pitivi/" />
<bug-database rdf:resource="https://gitlab.gnome.org/GNOME/pitivi" />
<category rdf:resource="http://api.gnome.org/doap-extensions#apps" />
<programming-language>Python</programming-language>
......
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