1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
I sometimes have the feeling the number of people directly |
5 |
contributing to gentoo is decreasing and the number of people with |
6 |
their own overlays is increasing. |
7 |
|
8 |
Q: "Why contribute? I have my own overlay." |
9 |
A: That is bad. There are several reasons: |
10 |
* most overlays don't get any reviews from any other person/dev and |
11 |
hence the quality is usually a lot lower than in the official tree |
12 |
(not necessarily because we are smarter, but because of more eyes) |
13 |
* overlays decentralize packaging which is a very bad thing and can |
14 |
cause so many problems that I cannot name them all here (most |
15 |
importantly overlay maintainers have no access to the trees profiles/ |
16 |
folder, cannot limit breakage that happened and cannot coordinate any |
17 |
delicate bumps of crucial system libs) |
18 |
* some overlay maintainers overwrite system libraries with their own |
19 |
versions, causing unnecessary bugs for users |
20 |
* user experience does not improve if he has to add a whole overlay |
21 |
for a single package |
22 |
* most overlays don't do pgp signing or even have thin manifests |
23 |
* many overlay maintainers do not even bother to communicate in bug |
24 |
reports about ebuild requests, so developers might not even notice |
25 |
that someone has already worked on an ebuild |
26 |
|
27 |
There is probably more. In the end the important thing is that an |
28 |
overlay is not a direct contribution to gentoo. Of course, direct |
29 |
contribution requires more work and more patience, but will solve all |
30 |
of the above problems. |
31 |
|
32 |
Q: What is direct contribution? |
33 |
A: There are many ways: |
34 |
* file a bug report with an ebuild request giving useful information |
35 |
about the package (I sometimes give up on working on an ebuild, |
36 |
because I don't use the software and have little knowledge about what |
37 |
users will expect from an ebuild) |
38 |
* file a bug report with an ebuild proposal, preferably after getting |
39 |
a review in #gentoo-dev-help or #gentoo-sunrise |
40 |
* communicate to devs that you are interested in becoming a proxy |
41 |
maintainer [1] |
42 |
* contribute to sunrise [2] the official user overlay (yes, also an |
43 |
overlay, but with very strict policy to ensure compatibility with the |
44 |
tree); here you also get a review in #gentoo-sunrise and we have |
45 |
mirrors on github and bitbucket to accept pull requests |
46 |
* start bothering the gentoo herds/projects directly, either in their |
47 |
IRC channel or in their official overlays (oh, an overlay again, |
48 |
yes... but most of the time the work done there flows directly into |
49 |
the tree with some delay); some are hosted on github etc |
50 |
* become a dev [3] |
51 |
|
52 |
Only do your own overlay if more than one of the contribution channels |
53 |
failed. As an example: if you propose binary ebuilds for software that |
54 |
is opensource, then devs will probably not like that. |
55 |
|
56 |
It is also fine to have your own overlay, e.g. for testing or for |
57 |
packages that are really alpha, but contributing directly is more |
58 |
awesome and benefits more users. |
59 |
|
60 |
|
61 |
- -- |
62 |
[1] http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml |
63 |
[2] http://www.gentoo.org/proj/en/sunrise/index.xml |
64 |
[3] |
65 |
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?full=1#book_part1_chap2 |
66 |
-----BEGIN PGP SIGNATURE----- |
67 |
Version: GnuPG v2.0.20 (GNU/Linux) |
68 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
69 |
|
70 |
iQEcBAEBAgAGBQJSMcfoAAoJEFpvPKfnPDWzIgEH/iOpSMzGMNW1Q+Kz4r3jC0e1 |
71 |
rsZd4YU+EgdCZrzcbYpYFyoJXdHkf4O7PxhBaMcRjLTZRMsuc5dy4l2MiyfWcV8m |
72 |
RJ2zeeu2ts99IQqkjncLwL3zuPT7xGt8hutwg8JRyvR47b3kvQqTO0XDq8uRdC8P |
73 |
6jUtYHwJAG4F/YRjk7+vsH8RmQ9jPWRUb9pe/k9puW0ltdFAgC9vTInJnZJAY7j4 |
74 |
SJLAkST14R7mxTs2Uaqsfq/AgRK0A3d5o4OISECOx40VKBup9HZQqKkHBmSnKUMv |
75 |
lwFtQpl6ZyhuSUUUAVTuPMYIAozO49nzrpJ/i7whZ1fuXapfXvFGKMJltp1ZfR8= |
76 |
=gxlp |
77 |
-----END PGP SIGNATURE----- |