1 |
On Fri, Nov 21, 2014 at 7:13 PM, <wireless@×××××××××××.com> wrote: |
2 |
> On 11/21/14 17:10, Rich Freeman wrote: |
3 |
>> |
4 |
>> On Fri, Nov 21, 2014 at 5:40 PM, <wireless@×××××××××××.com> wrote: |
5 |
>>> |
6 |
>>> Interesting perspective that I had not considered... still, I think there |
7 |
>>> is |
8 |
>>> more at play here. It sounds as if a few "chosen" old guard |
9 |
>>> are going to kick out more of the progressive and newer devs |
10 |
>>> so that these few. control the core distro. That way they can agree |
11 |
>>> and do what they want. |
12 |
>> |
13 |
>> |
14 |
>> Where are you getting this stuff? People seem to talk about "old |
15 |
>> guard" Gentoo devs blocking contributions, but the very few times |
16 |
>> anything remotely resembling this gets pointed out the Council has |
17 |
>> stepped in to remove obstructions. |
18 |
>> |
19 |
> |
20 |
> I have repetitively ask why java is treated like a second class citizen here |
21 |
> at gentoo. Is anyone close any of those old deprecated java bugs? |
22 |
> |
23 |
> I just wonder why the rank and file devs do not like java? |
24 |
> Why the devs do not celebrate Java? |
25 |
|
26 |
If nobody is maintaining Java it is because nobody wants to maintain |
27 |
Java. You suggested that established developers were preventing new |
28 |
ones from doing some things. The problem with Java is that there |
29 |
simply aren't that many developers interested in it at all. |
30 |
|
31 |
Gentoo devs work on whatever they want to work on. They aren't paid employees. |
32 |
|
33 |
|
34 |
> I just like to wrap all of this in a conspiracy flavouring; hopefully some |
35 |
> devs will jump into java, fix it up and let's give it a proper place in the |
36 |
> gentoo structure? What if somebody wants to develop a PM or PMS using java |
37 |
> on gentoo. You think that person would receive a 'warm welcome' as in lots |
38 |
> of help, code snippets and partners among the gentoo elites? |
39 |
|
40 |
If you want to write a java PM just do it. You seem to be complaining |
41 |
that nobody is writing one for you. I'm sure there are plenty of |
42 |
Gentoo devs and non-devs who would be happy to talk to you about |
43 |
writing one if you're willing to pay them for their time. Otherwise, |
44 |
this is a volunteer effort and people work on what they want to work |
45 |
on. |
46 |
|
47 |
That isn't some kind of evil conspiracy. Nobody is going to prevent a |
48 |
Gentoo developer from putting a java-based package manager in the tree |
49 |
as long as it doesn't contain security bugs/etc. They may or may not |
50 |
get any help with doing it, and that just reflects that people work on |
51 |
what they want to. |
52 |
|
53 |
> |
54 |
> How does your council feel about that? How many council member have added |
55 |
> java packages or closed java bugs? Sure they have work on other things they |
56 |
> do not like, but hell no to java? How about a 'java week" where the |
57 |
> brightest java devs devote just one week to java? (gnashing of teeth?). |
58 |
|
59 |
Well, I can speak only for myself (as a Council member). I've never |
60 |
worked on java packages or closed java bugs (well, maybe I've done a |
61 |
stable request or two as part of an arch team, but that isn't really |
62 |
what you're talking about). |
63 |
|
64 |
Like most other devs I work on the things that interest me or which I |
65 |
care about. For the most part, java is not among them, though I do |
66 |
maintain the android sdk which is java-based. |
67 |
|
68 |
> How about authorizing a few dozen folks to close java bugs. Why |
69 |
> do you have to be a dev to close bugs in BGO? |
70 |
|
71 |
So, first you'll need to find a few dozen folks who are interested in |
72 |
closing java bugs. Second, you don't have to be a dev to close bugs |
73 |
in BGO, but you do need to be given access, and that does mean that |
74 |
you'll have to work with somebody with some kind of guidelines around |
75 |
what you'll be doing. Arch testers have editbugs privs and they |
76 |
aren't devs, for example, but they follow rules like everybody else. |
77 |
|
78 |
> It sure looks like a duck, quacks like a duck, smells like a duck |
79 |
> and I believe I hear quacking from this latest wacky (dev) idea to move most |
80 |
> devs and most packages to second class status; as pure quackery. Medically, |
81 |
> from a medical dictionary that is about 50 years old, the |
82 |
> most correct diagnostic is "imbecilic". |
83 |
|
84 |
Well, go take that up with the dev proposing this. I'm not suggesting |
85 |
that anything should be excluded from the main tree, and so far I've |
86 |
only seen a single Gentoo dev suggest that. I do support making it |
87 |
easier to maintain stuff outside the tree. |
88 |
|
89 |
Devs are allowed to post on the lists. When one dev posts an idea |
90 |
that doesn't mean that the entire distribution is going to reverse |
91 |
directions. |
92 |
|
93 |
> |
94 |
> I think that java and clustering on gentoo are dying, because the leadership |
95 |
> environment makes it difficult for them to proper. How many java bugs have |
96 |
> you close, during 2014? |
97 |
|
98 |
Zero. That's about as many as I'm likely to close in 2015. Nobody in |
99 |
the Gentoo leadership is keeping anybody from closing Java bugs. |
100 |
There just aren't that many devs interested in working on them. |
101 |
|
102 |
If you want to work on them, you might consider becoming a dev, or |
103 |
working on them in an overlay (which is a good way to become a dev, |
104 |
actually). |
105 |
|
106 |
You seem to be under the impression that Gentoo devs work on things |
107 |
that the Gentoo leadership tells them to work on. That is hardly the |
108 |
case, many of our most important packages are also the least |
109 |
maintained, because devs work on what they work on, and not on the |
110 |
stuff the leadership considers important. If a Gentoo developer |
111 |
wanted to work on Java the leadership wouldn't interfere with that |
112 |
just as they didn't interfere with a couple of devs deciding to fork |
113 |
udev. |
114 |
|
115 |
-- |
116 |
Rich |