1 |
On Thu, May 24, 2012 at 6:01 PM, Dan Douglas <ormaaj@×××××.com> wrote: |
2 |
> But ok it's a good point. Github isn't a good central point of contact. People |
3 |
> have to use their discression. It's just uncommon these days for a project as |
4 |
> big as Gentoo to have ultra-centralized corporate-style procedures where |
5 |
> everything happens exclusively though official channels. And anyway you couldn't |
6 |
> "enforce" that sort of thing if you tried. |
7 |
> |
8 |
|
9 |
++ |
10 |
|
11 |
There is no policy that every commit in cvs needs to be referenced to |
12 |
a bug, and I doubt we're going to change that. So, if I call up |
13 |
another dev on the phone and tell them they have a typo in an ebuild, |
14 |
and they fix it and commit it, nothing has gone wrong. That isn't the |
15 |
most efficient way to work usually, but there is no policy against it. |
16 |
In general users should file bugs and not contact devs directly, but |
17 |
if somebody has a private arrangement otherwise, no harm no foul. |
18 |
|
19 |
Github is just another overlay. If in the course of working on the |
20 |
next kde release the kde team makes 385 changes to their overlay, we |
21 |
don't make them log and close 385 bugs on b.g.o before they merge in |
22 |
the files from the overlay. |
23 |
|
24 |
So, if a team wants to use non-official tools, by all means go ahead. |
25 |
The QA standards apply to anything hitting the main tree, and must be |
26 |
followed at that point in time. We should keep our tools working |
27 |
well, but if in some case there is a better way of working, or a small |
28 |
team has some other preference, well, have at it! |
29 |
|
30 |
Rich |