1 |
Hi together, |
2 |
|
3 |
since i am not able to get any real argument or even discussion on IRC nor on this mailing list from |
4 |
Arfrever (main person behind those changes), i would like to raise the following points now on this |
5 |
mailing list as told on IRC, so he gets the chance to answer those points and to clear the issues: |
6 |
|
7 |
-major changes to python eclasses have been done without peer review on this mailing list. This |
8 |
includes pulling in python-3* versions, even when they are not required nor used on the user system |
9 |
|
10 |
Our policy is, that major changes to main eclasses should previously shown and discussed publically |
11 |
on this mailing list, this did not happen for the python eclass. I think, he was already told about |
12 |
it, but i still did not see any RFC about those eclass changes. |
13 |
Additionally, those changes now pull in python-3 for every user, also no package does require |
14 |
python-3 nor will it be used, since the main python version still has to be python-2. This results |
15 |
in vasted time for additional compilation (both for python-3 and every python module, which is able |
16 |
to work with python-3) and vasted space on the user system, since those files are not used anywhere. |
17 |
Additionally, every additional package raises the security risks since it raises the amount of code |
18 |
around, also this is nothing python specific. |
19 |
Since python-3 is totally optional, it should be an option to pull it in, not a forced pull, where |
20 |
users have to know, that is is optional and could be masked. |
21 |
|
22 |
-A news item, which is only shown, once python-3* is installed. |
23 |
|
24 |
It is only shown _after_ installation of python-3. |
25 |
It just suggests to not set python-3 as main python version and to run the python-updater, but it |
26 |
does not tell the user, that python-3 is still completly optional and not needed for him. |
27 |
|
28 |
-Arfrever also said, he would add a seperate news item, when python-3 gets stabilized. |
29 |
|
30 |
Now the stabilisation bug is open, the first arch is stabilized and i still dont see any news item, |
31 |
which does prepare the users in advance. |
32 |
|
33 |
|
34 |
Beside those points, one additional main issue is, that i and others dont seem to be able to have a |
35 |
discussion with Arfrever about this topics. He says, he has no time for it or says, that he already |
36 |
had shown arguments, but cannot show any evidence or just stops responding without any note. |
37 |
|
38 |
Even if all those changes would have good reasons for them, the way, how they are done and |
39 |
communicated is not very well chosen. And since i dont seem to be able to get any discussion with |
40 |
Arfrever about those points, i will also CC devrel. For now, to inform them and, also in the hope, |
41 |
that it is not needed and those issues can be resolved, in preparation for a discussion and decision |
42 |
on those topics, if needed later one. |
43 |
|
44 |
|
45 |
So for Arfrever: I also CCed you, so that i can be sure, that you get the mail. Please answer to all |
46 |
of my above points with arguments. Choose whatever way you prefer for that (public mail, private |
47 |
mail, public IRC discussion or private message via IRC). If you missed some points or others appear, |
48 |
i will answer and ask about those. |
49 |
If you do not answer at all or do not answer with arguments to my satisfaction within 14 days, i |
50 |
will escalate those issues to devrel. |
51 |
|
52 |
-- |
53 |
Thomas Sachau |
54 |
|
55 |
Gentoo Linux Developer |