| 1 |
On Wed, Apr 3, 2013 at 1:05 PM, Ciaran McCreesh |
| 2 |
<ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
> On Wed, 03 Apr 2013 19:06:31 +0200 |
| 4 |
> hasufell <hasufell@g.o> wrote: |
| 5 |
>> That is not possible without the agreement of the eclass maintainers. |
| 6 |
>> So you cannot just "ban" an eclass. |
| 7 |
> |
| 8 |
> QA certainly can, and should. Or failing that, the Council can step in. |
| 9 |
> |
| 10 |
|
| 11 |
No need to have a fight. |
| 12 |
|
| 13 |
If there are reasons not to move everything into the EAPI they should |
| 14 |
be discussed. It takes months to implement a new EAPI in general so |
| 15 |
the eclass maintainers will be involved I'm sure and everybody can |
| 16 |
coordinate nicely. |
| 17 |
|
| 18 |
And the Council already approves all EAPIs, so if for whatever reason |
| 19 |
there is a need to make a call they can do so. |
| 20 |
|
| 21 |
There is no need to argue about hypothetical domains of authority. |
| 22 |
Let's instead focus on what is the best way to move forward, hope for |
| 23 |
consensus, and then deal with disagreement only when that time comes. |
| 24 |
|
| 25 |
Rich |
Archives