1 |
On Mon, 2021-07-12 at 09:33 -0400, Aaron Bauman wrote: |
2 |
> On Mon, Jul 12, 2021 at 11:38:18AM +0100, Marek Szuba wrote: |
3 |
> > On 2021-07-11 21:54, Michał Górny wrote: |
4 |
> > |
5 |
> > > My gut feeling is that having this distinction is useful. However, it |
6 |
> > > has been pointed out that we've probably never really had to use it |
7 |
> > > (i.e. use the "banned" argument to stop someone from using old EAPI) |
8 |
> > > and that the switch from "deprecated" to "banned" state did not really |
9 |
> > > affect porting away from old EAPI. |
10 |
> > |
11 |
> > For the benefit of those not interested in sifting through the logs of |
12 |
> > Council meetings, here is a quick reiteration of my take on this: |
13 |
> > |
14 |
> > 1. Maybe it's my professional bend speaking but it feels to me like we |
15 |
> > really should establish a clear, GLEP-documented EAPI life cycle with |
16 |
> > well-defined meaning of individual stages. I will work on preparing a |
17 |
> > suitable proposal; |
18 |
> > |
19 |
> > 2. Until the above has introduced a (hopefully) better system, I am all for |
20 |
> > removing step 2 because it makes the procedure less bureaucratic. |
21 |
> > |
22 |
> > |
23 |
> > On 2021-07-12 02:11, Aaron Bauman wrote: |
24 |
> > |
25 |
> > > Just officially ban it, send out a message, and use the best judgement |
26 |
> > > when enforcing it (should it even need to be enforced). |
27 |
> > |
28 |
> > And the point of establishing a policy doomed from start to be enforced |
29 |
> > weakly or not at all is? Other than making the Council look like we care |
30 |
> > more about theatrics than actual governance, that is. |
31 |
> > |
32 |
> > -- |
33 |
> > Marecki |
34 |
> > |
35 |
> |
36 |
> It is not theatrics. It is a policy that was effective in the past and |
37 |
> is used in lieu of a technical measure. Albeit, it is unlikely to be |
38 |
> enforced because most people abide by the deprecation warnings. |
39 |
> |
40 |
|
41 |
That's the whole point. Do we need a two-step deprecation/ban if 'most' |
42 |
people abide by deprecation warnings? |
43 |
|
44 |
I'm wondering if the two-step deprecation/ban isn't a symptom of a wider |
45 |
problem. After all, we want people to stop using old EAPIs after |
46 |
they're deprecated, not after they're explicitly forbidden to use them. |
47 |
|
48 |
Maybe the whole point is that we should stop trying to draw explicit |
49 |
lines everywhere and instead assume -- per common sense -- that |
50 |
deprecating is enough for people to eventually stop using them. |
51 |
|
52 |
-- |
53 |
Best regards, |
54 |
Michał Górny |