1 |
On 2018-12-20 09:18, Michael Orlitzky <mjo@g.o> wrote: |
2 |
> On 12/20/18 6:28 AM, (Nuno Silva) wrote: |
3 |
>>>> |
4 |
>>> Well the Gentoo Wiki https://wiki.gentoo.org/wiki/Submitting_ebuilds |
5 |
>>> suggested that new ebuilds should be submitted via Bugzilla. |
6 |
>>> |
7 |
>>> Could you please tell me if it is still the recommended way? |
8 |
>>> If not, IMHO it is better to change Wiki as well to prevent further |
9 |
>>> misunderstanding. |
10 |
>> |
11 |
>> I would like to ask again for a clarification about this. Last month, I |
12 |
>> asked if there was some rule against using bugzilla, but there were no |
13 |
>> replies: |
14 |
>> |
15 |
> |
16 |
> BugZilla is right place. If you open a PR on Github, you'll get an |
17 |
> automated message telling you to open an associated bug on BugZilla. |
18 |
> If Github ever goes away, all of the PR history it contains will be lost |
19 |
> forever. |
20 |
> |
21 |
> Since Github is proprietary, forcing people to use it is against our |
22 |
> social contract, and many developers completely ignore everything you |
23 |
> post there. |
24 |
> |
25 |
> On the other hand, casually reading the contents of a PR is easier on |
26 |
> Github than with patches on BugZilla. For best results, do both. |
27 |
|
28 |
Did anyone ever considered using GitLab? |
29 |
Its community edition is quiet enough I think. |
30 |
|
31 |
Being able to comment directly on ebuilds/patches would be a really nice |
32 |
feature. IMO It makes communication efficiency much higher compared to |
33 |
compared to Bugzilla. |
34 |
|
35 |
Also since the GitLab server is hosted by the community, no Micro$oft |
36 |
get involved... |