| 1 |
On 2018-12-20 03:50, Nils Freydank <nils.freydank@××××××.de> wrote: |
| 2 |
> Hi Danny, |
| 3 |
> |
| 4 |
> first I want to thank you for submitting your ebuild, and I'm quite sorry to |
| 5 |
> see another contributor who doesn't get responses for a long while. This is no |
| 6 |
> evil intention, just a lack of manpower and the lack of someone maintaining |
| 7 |
> your "new" package. (This was what jstein meant with his response[1]). |
| 8 |
> |
| 9 |
I do understand the situation of lacking manpower, also I realized made |
| 10 |
some mistakes in my ebuild file, so you do not have to apologize. :-) |
| 11 |
|
| 12 |
> Additionally bugzilla is seen as too impractical to use for new packages that |
| 13 |
> many don't get much attention there, only on github.com. |
| 14 |
> |
| 15 |
Well the Gentoo Wiki https://wiki.gentoo.org/wiki/Submitting_ebuilds |
| 16 |
suggested that new ebuilds should be submitted via Bugzilla. |
| 17 |
|
| 18 |
Could you please tell me if it is still the recommended way? |
| 19 |
If not, IMHO it is better to change Wiki as well to prevent further |
| 20 |
misunderstanding. |
| 21 |
|
| 22 |
> However, within Gentoo every package needs a maintainer to avoid dead packages |
| 23 |
> inside our tree (which then get no security nor "normal" bug fixes). Packages |
| 24 |
> with "maintainer needed" state had one, but he or she just dropped the work. |
| 25 |
> If you have some spare time you can become a proxied maintainer, meaning you |
| 26 |
> maintain the package without being a Gentoo dev. As git distinguishs author |
| 27 |
> and commiter you get also a proper attribution for your work. |
| 28 |
> |
| 29 |
> The workflow in general is that you clone the git repo and create branch, add |
| 30 |
> your ebuild, open a git PR on github.com[2] and get reviews from devs. You can |
| 31 |
> find more details in some wiki articles[3]. |
| 32 |
> |
| 33 |
This is the "correct" way to submit a new ebuild I suppose? |
| 34 |
|
| 35 |
> Unfortunately it takes a bunch of time until packages are merged, because of |
| 36 |
> the mentioned lack of manpower on the devs' side, aswell as plenty mistakes |
| 37 |
> new proxied maintainers tend to implement in ebuilds (myself included here). |
| 38 |
> |
| 39 |
> I hope that helps you, |
| 40 |
> Nils |
| 41 |
> |
| 42 |
> |
| 43 |
> [1] https://bugs.gentoo.org/638446#c1 |
| 44 |
> [2] https://github.com/gentoo/gentoo/pulls?q=is%3Aopen+is%3Apr |
| 45 |
> [3] https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide |
| 46 |
> and https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers |
| 47 |
|
| 48 |
I love Gentoo and I want to contribute. |
| 49 |
I will read through the docs and have a try. Time to step forward as an |
| 50 |
"end user"! |
| 51 |
|
| 52 |
Thanks for helping. |
| 53 |
|
| 54 |
Danny |
Archives