1 |
Hi everyone, |
2 |
|
3 |
Am Donnerstag, 20. Dezember 2018, 12:28:17 CET schrieb Nuno Silva: |
4 |
> On 2018-12-20, YUE Daian wrote: |
5 |
> > On 2018-12-20 03:50, Nils Freydank <nils.freydank@××××××.de> wrote: |
6 |
> > [...] |
7 |
> >> Additionally bugzilla is seen as too impractical to use for new packages |
8 |
> >> that many don't get much attention there, only on github.com. |
9 |
> > |
10 |
> > Well the Gentoo Wiki https://wiki.gentoo.org/wiki/Submitting_ebuilds |
11 |
> > suggested that new ebuilds should be submitted via Bugzilla. |
12 |
> > |
13 |
> > Could you please tell me if it is still the recommended way? |
14 |
> > If not, IMHO it is better to change Wiki as well to prevent further |
15 |
> > misunderstanding. |
16 |
|
17 |
from my perspective it seems as only github.com is used and bugs.gentoo.org |
18 |
is more or less just kept as an official way for ebuild submission to keep |
19 |
a backup mechanism on the own infrastructure. |
20 |
|
21 |
Maybe in a perfect world someone trustworthy could provide a single-sign-on |
22 |
service for bugtrackers and a gitlab instance hosted by gentoo or stuff like |
23 |
that, but the current state is quite confusing, agreed. If you want to take |
24 |
care of your package become a proxied maintainer. If you go a step further |
25 |
later and become a gentoo dev you can also drop some workload from the proxied |
26 |
maintenance team and do you QA yourself and submit directly to the tree. |
27 |
|
28 |
> I would like to ask again for a clarification about this. Last month, I |
29 |
> asked if there was some rule against using bugzilla, but there were no |
30 |
> replies: |
31 |
> [...] |
32 |
No, as far as I know there is now rule, just a not so good usable platform and |
33 |
another one that is proprietary but works far better. |
34 |
|
35 |
|
36 |
A disclaimer in the end: I'm not a Gentoo developer, just another random user |
37 |
who maintains packages. |
38 |
|
39 |
Regards, |
40 |
Nils |
41 |
|
42 |
-- |
43 |
GPG fingerprint: '00EF D31F 1B60 D5DB ADB8 31C1 C0EC E696 0E54 475B' |
44 |
Nils Freydank |