1 |
El mar, 05-05-2009 a las 18:28 +0100, George Prowse escribió: |
2 |
> Thomas Sachau wrote: |
3 |
> > George Prowse schrieb: |
4 |
> >> Thomas Sachau wrote: |
5 |
> >>> For those, who can work with IRC and are interested in working with |
6 |
> >>> ebuilds, there is already an option: |
7 |
> >>> |
8 |
> >>> Join #gentoo-dev-help or even better #gentoo-sunrise and read the |
9 |
> >>> documentation from the topic. The |
10 |
> >>> Sunrise Overlay (with the #gentoo-sunrise IRC channel) is open for |
11 |
> >>> everyone willing to learn and |
12 |
> >>> contribute to it. Even normal users can get access, learn how to |
13 |
> >>> create ebuilds, how to improve them |
14 |
> >>> and how to maintain them. |
15 |
> >>> As a starting point, this is a central overlay, where ebuilds are |
16 |
> >>> maintained, that dont get a |
17 |
> >>> developer as maintainer because of missing manpower. Additionally, all |
18 |
> >>> contributors learn the ebuild |
19 |
> >>> development work themselves. |
20 |
> >>> |
21 |
> >>> And if you are willing to learn and do continuously good work, there |
22 |
> >>> is a good chance that you may |
23 |
> >>> level up to a developer yourself someday. You want an example? This |
24 |
> >>> was my way to become a full |
25 |
> >>> Gentoo developer. ;-) |
26 |
> >>> |
27 |
> >>> So at least for ebuild maintainence, there are good starting points |
28 |
> >>> (probably other projects also |
29 |
> >>> have training grounds like the java or kde herds), the bigger problem |
30 |
> >>> may be the communication |
31 |
> >>> between potential new developers and the current developer base and |
32 |
> >>> our options to become a new |
33 |
> >>> developer. |
34 |
> >>> |
35 |
> >> I think you are missing the point. If you sit and wait for them to join |
36 |
> >> you will always be understaffed. |
37 |
> >> |
38 |
> >> Go on a big dev drive! Announce it all over all the Gentoo's normal |
39 |
> >> communication channels and other generic linux places! Email some linux |
40 |
> >> magazines, talk to distrowatch, message some large LUGs. Get people |
41 |
> >> talking about it. Whatever happens, dont just sit on your hands. Tell |
42 |
> >> the users that Gentoo needs them and that they can make a difference! |
43 |
> >> |
44 |
> >> If you make it a big and special occasion which is planned correctly |
45 |
> >> with a sufficient number of current developers who are willing to walk |
46 |
> >> people through how and what it means to be a Gentoo Developer then the |
47 |
> >> influx could create a new backbone of new developers who will hopefully |
48 |
> >> be here for years to come. |
49 |
> >> |
50 |
> >> |
51 |
> > |
52 |
> > Such a campaign would need quite some time and i dont have this free time. So if anyone is willing |
53 |
> > to do the needed work, i can try to help a bit, but cannot take the work and time myself. |
54 |
> > |
55 |
> > The only thing i can do and currently do whenever possible is pointing people to the sunrise project |
56 |
> > and helping them there. And thats what i did with my mail. |
57 |
> > |
58 |
> I also fear that any sustained campaign would be bogged down in Gentoo's |
59 |
> red tape. |
60 |
> |
61 |
|
62 |
I feel it's necessary to clear that it's not mandatory to be a full time |
63 |
developer to help improve Gentoo. Many users want to help but they don't |
64 |
feel ready for such a compromise. Then there is Sunrise, and the |
65 |
overlays from the herds, where the prospective users can learn first and |
66 |
take the following step when they feel they're ready. I think there are |
67 |
at least 2 recent new developers who made it this way. |
68 |
|
69 |
There are several (much?) understaffed projects in Gentoo, the |
70 |
developers who are responsible of this areas could take some time to |
71 |
write a guide for users on how to help, with steps to commit patches to |
72 |
the overlays, wishes and needs... and then publish it in the project web |
73 |
page. |
74 |
|
75 |
Also, there could be a page similar to the 'staffing-needs' one, but |
76 |
listing links to the 'Help Us' pages of the projects. |
77 |
|
78 |
Just my 2c... |
79 |
|
80 |
And sorry for any spell/grammar error... |