1 |
On Thu, Aug 15, 2013 at 4:10 AM, Pacho Ramos <pacho@g.o> wrote: |
2 |
> El mié, 14-08-2013 a las 23:53 +0800, Patrick Lauer escribió: |
3 |
> [...] |
4 |
>> Well, it should reflect reality. |
5 |
>> |
6 |
>> PMS is still broken as much as it does not reflect the state of portage |
7 |
>> before PMS was written, and we've had to patch it up a few times to make |
8 |
>> it coherent, plus it is still lacking half the things that would make it |
9 |
>> useful as a standard. |
10 |
>> |
11 |
>> Your academic interpretation of standard as a platonic ideal |
12 |
>> disconnected from reality serves no purpose. |
13 |
>> |
14 |
> |
15 |
> On this topic I agree with Patrick: I don't fully understand why things |
16 |
> (like in_iuse from eutils.eclass) are missing from PMS. If that applies |
17 |
> to more features that were forgotten when writing PMS, we have a |
18 |
> problem :( |
19 |
|
20 |
Just picking a random spot to reply in this mess, but it could apply |
21 |
to many other posts. |
22 |
|
23 |
If somebody proposes a change and the PMS team is holding it up for an |
24 |
inappropriate reason, escalate it - don't stew over it and blow up on |
25 |
the mailing lists twice a year. |
26 |
|
27 |
However, from what I've seen in the past most "problems with PMS" are |
28 |
like most "problems with Gentoo" - they're things that people wish |
29 |
were different but which nobody bothers to fix. Nobody is getting |
30 |
paid to make PMS better, just as nobody is being paid to work on the |
31 |
dozen security GLEPs that came up 47 posts ago. When things don't |
32 |
happen in Gentoo 9 times out of 10 it is because nobody has put in the |
33 |
time to make them happen. In the 1 time out of 10 where some kind of |
34 |
bickering actually holds things up, that is the time to bring issues |
35 |
to the project lead or to the Council to get resolved. |
36 |
|
37 |
I won't speak for anybody but from my observations in the past in most |
38 |
cases where somebody rushes to defend portage against the evil forces |
39 |
of PMS we have a 75 post flamewar and then one of the portage |
40 |
maintainers steps up and basically explains that there is nothing |
41 |
wrong and things with PMS are going fine. |
42 |
|
43 |
I'm all for the Council being more proactive, but that doesn't mean |
44 |
asking infra to BCC us on every email sent through gentoo so that we |
45 |
can find and act on every one-off issue that two devs have a |
46 |
disagreement on. If there is a problem bring it up. We call for |
47 |
agenda items every month, and we already agreed that if issues are |
48 |
more critical that we would act on them in-between meetings if |
49 |
appropriate (just file a bug and/or ping the alias). |
50 |
|
51 |
However, if your request is going to be that we scrap PMS, honestly, I |
52 |
wouldn't waste your (and our) time - mine is only one vote but frankly |
53 |
I don't see it happening. By all means complain if the PMS team |
54 |
unfairly rejects a proposal, or make suggestions as to ways to improve |
55 |
how PMS is run. However, your suggested improvements need to come |
56 |
along with people willing to implement them. You can't just say "I |
57 |
wish this team that I have no interest in helping out worked |
58 |
differently" unless you can persuade them to go along with it. |
59 |
|
60 |
Oh, and as far as devrel leads treating people like children go - my |
61 |
sense is that most devs would like to see devrel taking a more active |
62 |
lead in dealing with nonsense on the lists, not less. If things get |
63 |
out of hand they can be dealt with, but frankly the main thing that |
64 |
seems to be out of hand here are personal attacks on the list. After |
65 |
that huge thread on -core a few months ago I think that we need to |
66 |
have more direct intervention when inappropriate behavior on the lists |
67 |
takes place - otherwise we just have an atmosphere where everybody |
68 |
feels like they have PTS. A wrist slap on the lists is better than |
69 |
rage-quit or bans. |
70 |
|
71 |
Rich |