File: README.contributors

package info (click to toggle)
poppler 20.09.0-3.1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye, sid
  • size: 16,092 kB
  • sloc: cpp: 151,577; ansic: 30,155; python: 367; makefile: 42; sh: 36
file content (51 lines) | stat: -rw-r--r-- 2,192 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
If you want to become or are a poppler contributor, this is a README for you, keep reading!

Licensing
---------
Only send patches to poppler if you agree to license (or relicense) them under
GPLv2 and later (or something more permissive that can be "upgraded" to GPLv2
and later). If you do not agree to this license, please explain the problem / bug
and how you would solve it in words instead of code.

By default all patches attached to the gitlab instance or sent to the mailing list
will be assumed to agree with the licensing expressed here.

Channels of contact
-------------------
Poppler has three main channels of contact:
 * The poppler mailing list http://lists.freedesktop.org/mailman/listinfo/poppler
 * The poppler gitlab instance https://gitlab.freedesktop.org/poppler/poppler/
 * The #poppler channel at the IRC freenode network
Do not hesitate to drop by talk to people there.

clang-format
------------
We introduced clang-format mandatory usage in July 2020.
If you want git blame to ignore the revision in which we did the mass change you can do
   git config blame.ignoreRevsFile .git-blame-ignore-revs
on your clone

To get the clang-format warnings locally instead at CI time we recommend you
to copy the hooks/pre-commit to your .git
    cp hooks/pre-commit .git/hooks/

We are using clang-format 10 on CI. Unfortunately clang-format is not totally
compatible with older versions of itself. If CI gives you trouble but your local
clang-format disagrees, just apply the changes suggested by CI and then commit
with the --no-verify flag. If you get stuck, don't hesitate to ask the reviewer
to help and they will reformat your commits :)

Merge requests
--------------

When creating a new merge request on gitlab make sure it has a clear title and
the description includes any extra details that might be helpful for the
reviewer, such as what the aim of the change is and decisions made during
implementation.

Also, check "Allow commits from members who can merge to the target branch" as
that enables rebase on landing. See the gitlab docs for details:

https://docs.gitlab.com/ee/user/project/merge_requests/allow_collaboration.html

And keep hacking on poppler!