1 |
Alec Ten Harmsel <alec <at> alectenharmsel.com> writes: |
2 |
|
3 |
> > I think the concept of "Projects" will persist, but herds have |
4 |
> > to become active and request to become "Projects" as defined |
5 |
> > on the gentoo wiki or they will be erased. Like many others, |
6 |
> > I have been burned in the past with trying to get directly involved |
7 |
> > with Gentoo (been here since 2004). That's all water under the bridge. |
8 |
> > So I am "tip_toeing" behind the scenes willing to be a grunt |
9 |
> > and clean up some of the java mess, participate in clustering and |
10 |
> > contribute to the science project. We'll see just how long it lasts |
11 |
> > before I get "bitch_slapped" like my previous attempts........ |
12 |
|
13 |
> There is a large discussion on the Spark mailing list right now about |
14 |
> having groups of maintainers for different areas: |
15 |
> |
16 |
> |
17 |
http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Designating-maintainers-for-some-Spark-components-td9115.html |
18 |
> |
19 |
> I'm not sure how relevant that is, but it's interesting. |
20 |
> |
21 |
> My own viewpoint is that there should be no individual maintainers; |
22 |
> packages should be assigned on a herd level, and the herds can |
23 |
> self-regulate and know who has expertise with each package. Just my two |
24 |
> cents; best to not have a single point of failure. |
25 |
|
26 |
|
27 |
The spark post is relevant to the discussion. But spark is one (large) |
28 |
code_set and we have thosands of different codes at Gentoo as a distro. |
29 |
So some of our softwares, such as Python, are like spark and there |
30 |
are multiple maintainers, like spark. We also have many smaller softwares |
31 |
(ebuilds) that need someone (anyone?) to step forward and maintain that |
32 |
singular package. Routine on Gentoo dev, there are packages up for |
33 |
grabs that need a maintainer. Spark is in the luxury postion of having |
34 |
many, very talented coders all working on one (large) piece of software. |
35 |
|
36 |
Beside, I think the the "projects" will provide that group effort |
37 |
that you admire in the current gentoo herds and the spark community for very |
38 |
important codes (like gcc, python, perl etc). |
39 |
|
40 |
But there will also be many useful softwares that we should keep around |
41 |
that just need a single maintainer. How it shakes out as to what the devs |
42 |
will allow for those sorts of packages, like "elvis" for example of a |
43 |
package that is not in anyone's critical path, but are cool to keep around. |
44 |
|
45 |
We, gentoo, have a wide variety of codes to maintain, and we'll need |
46 |
everyone from the very talented coders to capable_users to maintain |
47 |
these ebuilds, as our distro grows. We're going to have dozens if not |
48 |
hundreds of codes (ebuilds) just to fluff out the clustering codes |
49 |
necessary for a robust set of ebuilds for gentoo_clustering, imho. |
50 |
|
51 |
We need more devs and responsible users to help maintain and grow the base |
52 |
of ebuilds, imho. But I do agree, spark is going to need a very |
53 |
talented maintainer...... with quite a bit of java and gentoo expertise? |
54 |
|
55 |
Beside I think the decision, from what I've read, to terminate herds |
56 |
is pretty much a "done deal". Think of projects and maintainers and others, |
57 |
as you formulate gentoo's path forward. |
58 |
|
59 |
|
60 |
James |