1 |
On Wed, Dec 27, 2017 at 4:16 PM, Nils Freydank <holgersson@××××××.de> wrote: |
2 |
> Am Mittwoch, 27. Dezember 2017, 22:33:03 CET schrieb R0b0t1: |
3 |
>> On Wed, Dec 27, 2017 at 10:32 AM, William Hubbs <williamh@g.o> wrote: |
4 |
>> > As he said, he contactedd the maintainers in ample time, so I would say |
5 |
>> > that since they didn't respond he went ahead in good faith. I'll get the |
6 |
>> > link later, but as I recall, the dev manual recommends a 2-4 week wait |
7 |
>> > for maintainers not responding then we can assume that what we are doing |
8 |
>> > is ok. |
9 |
>> |
10 |
>> This assumes there is some pressing need for the change to take place, |
11 |
>> which I am not sure there is. I can understand wanting to make the |
12 |
>> change for consistency's sake, but the feature is important enough |
13 |
>> that I think a suitable replacement should explicitly be found before |
14 |
>> continuing. E.g. affirmative feedback from all affected packages. |
15 |
> |
16 |
> Often a fix timeline is the only way to achieve any responses - or at least |
17 |
> get stuff done, even if the matter itself is not urgent at all. In this |
18 |
> specific case the points Michael had were quite clear, and the timespan of |
19 |
> two month was long enough to react somehow (at least in the context of typical |
20 |
> periods in Gentoo, e.g. last rite/removal period of 30 days). |
21 |
> |
22 |
|
23 |
Yes, but as per past comments it seems some people think the action |
24 |
taken was slightly inappropriate. It feels like you didn't read what I |
25 |
said: in some cases, a fix timeline may not be appropriate. I don't |
26 |
know when that is. |
27 |
|
28 |
> On topic: There are some users including myself that find cracklib mostly |
29 |
> annoying. I use strong passwords (or ssh keys only) where I can, and cracklib |
30 |
> annoys me with the request to set "secure passwords" for a container |
31 |
> playground, where I want root:test as login credentials. |
32 |
> Beside that the point that profiles in general should contain as least USE as |
33 |
> possible (see the bug report for that). |
34 |
> |
35 |
|
36 |
I must be confused, because this is the only part of your message that |
37 |
is offtopic. |
38 |
|
39 |
>> Enforcement of rules or Gentoo development guidelines does not happen |
40 |
>> consistently, and the times when rules are enforced "for consistency's |
41 |
>> sake" seem completely arbitrary. There seems to be no extant problems |
42 |
>> caused by the flag as set, so why focus on this specifically? |
43 |
> |
44 |
> To me these times look as they're based upon agreement between the involved |
45 |
> parties, and in itself consistently, e.g. at least 30 days masking before |
46 |
> removal out of the tree, or in this case at least two to four weeks to let |
47 |
> others respond. |
48 |
> |
49 |
|
50 |
But why male models^H^H^H^H^H^H^H^H^H^H^Hfocus on this issue in |
51 |
particular? If I understand the situation, nothing is actually |
52 |
*broken.* That is why I was questioning consistency. |
53 |
|
54 |
>> There is a lot of discussion of not burdening developers with |
55 |
>> pointless talk or changes. If that is a goal, then why is this posting |
56 |
>> receiving so many replies? |
57 |
> |
58 |
> With all due respect, your posting didn't bring any new relevant aspects into |
59 |
> this thread on this mailing list with the explicit focus and topic of Gentoo |
60 |
> development, and might be exactly part of the "pointless talk" you mention. |
61 |
> |
62 |
> My one isn't better; I just want to point that out to you, because you tend to |
63 |
> write messages with this kind of meta questions about the cause of things. |
64 |
> |
65 |
> If you want to discuss this, I'd prefer another place than this list. |
66 |
> |
67 |
|
68 |
As someone watching from the outside I see this type of discussion |
69 |
crop up from time to time. All I am suggesting is thinking about |
70 |
actions before they are acted out. This isn't to say what was |
71 |
undertaken was not thought out - but the patterns of behavior I see |
72 |
that that decision exists within are what I am suggesting needs more |
73 |
careful consideration. |
74 |
|
75 |
If you can not see the utility in thinking about thinking, I am not |
76 |
sure we would have much to talk about. |
77 |
|
78 |
Respectfully, |
79 |
R0b0t1 |