1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Jim Northrup wrote: |
5 |
| Joshua Baergen wrote: |
6 |
| |
7 |
| |
8 |
|>>2) There are gentoo.org references to #gentoo-dev, but the process of |
9 |
|>>interfacing, mentoring, and recruiting are self-referential beginning |
10 |
|>>with a bootstrap of being on the good side of an existing developer. So |
11 |
|>>for those of us who do not establish favorable dialogues by filing a |
12 |
|>>bug, the door starts out closed. |
13 |
|>> |
14 |
|>> |
15 |
|> |
16 |
|>In reference to the difficulties outlined regarding becoming a |
17 |
|>developer above, I am in the process of becoming a dev without any |
18 |
|>contact with developers beforehand except for filing a bug that |
19 |
|>probably annoyed devs more than helped :P I contacted the recruiting |
20 |
|>group in response to a requirement for developers and they were glad |
21 |
|>to get the process started provided that I showed evidence that I |
22 |
|>would be an asset, mainly through input on bugs currently open. |
23 |
|> |
24 |
|>I doubt that I am the only one who has this story, but that doesn't |
25 |
|>mean your claim in #2 could not have happened to other people. Did |
26 |
|>you have any specific situations you were referring to when you wrote |
27 |
|>that? |
28 |
|> |
29 |
|> |
30 |
| |
31 |
| I was up late on a friday evening hacking up a nifty addition to my |
32 |
| system and in my excitement and exuberance jumped on IRC to the dev |
33 |
| channel to get pointers to the best "official" references to ebuild |
34 |
| crafting and submission. |
35 |
| |
36 |
| As it was absolutely silent, I waited a few minutes and requested voice |
37 |
| from the first notice of motion i saw in the channel.. "re", or some |
38 |
| similar indication of important offical business commencing. I was |
39 |
| informed that the bottom line was voice was only granted to developers, |
40 |
| period, end of story, no exceptions, and I was obviously misinformed and |
41 |
| should be elsewhere. Instead of anything like assistance I wound up |
42 |
| being told |
43 |
| 1) (condescension) it was people like me who try to skirt the gentoo |
44 |
| process which are actually the problem even if we think it's contributing, |
45 |
| 2)these important people in this channel are only here so that they can |
46 |
| occasionally ping each other and see thier nickname had been highlighted. |
47 |
| 3) that under no circumstance was I going to get an audience in |
48 |
| #gentoo-dev, now or in future context, because it was for developers, |
49 |
| and regardless of 20 years coding experience or working on linux since |
50 |
| 0.99, I was not a developer |
51 |
| 4) I could feel free to file a bug if I thought there was an issue, or |
52 |
| talk to a recruiter about something to help out with. |
53 |
| |
54 |
|
55 |
First, let me say i am sorry you had this experience, i freuqntly voice |
56 |
people in #gentoo-dev if they seem to have the need to speak there, the |
57 |
reasons could be many, maybe someone uses icewm and finds it way |
58 |
outdated, and helps the maintainer by testing for him, being a quasi |
59 |
maintainer a while dow the road and eventually becoming a gentoo dev |
60 |
(might i add <imho>i would say we have more maintainers than |
61 |
developers</imho>?) and taking care of icewm completely then and making |
62 |
it a habit to apply the many gcc 3.4 patches who have been submitted to |
63 |
bugzilla, and lay dead and dusty there for no dev to be touched (ok so |
64 |
now it would be gcc4.0 but that dev might have brought on a guy who |
65 |
takes care of those by now |
66 |
|
67 |
ok enough stories about how use having +v in #gentoo-dev is possible, is |
68 |
normal, and can lead to things |
69 |
|
70 |
|
71 |
| my reply was that I enter #gentoo-dev, and request voice when it seems |
72 |
| helpful and important, without incident in all previous occasions |
73 |
| the response was that these developers were obviously in error and it |
74 |
| was irrelevant to the discussion. |
75 |
| |
76 |
| I said I'm willing to take my chances as being perceived as noise. |
77 |
| the response was an unceremonious kick. |
78 |
| |
79 |
| This developer was possessed with zeal and determination. to be sure. |
80 |
| |
81 |
| Anyways, it happened, it's over. the order and exact words may have |
82 |
| been different but the tone and the impression stuck. I spent the due |
83 |
| dillegence perfecting my system hack, but I did not succeed in making it |
84 |
| available, or finding a likely benefactor project for voip qos |
85 |
| settings. This was beneath the involvment of #gentoo-dev at the time i |
86 |
| made the approach. I spent several hours researching volumes of gentoo |
87 |
| info alternating between the recruitment process and the ebuild process, |
88 |
| on a busy weekend i had planned to spend apart from a console. |
89 |
| |
90 |
| so.. as an aside, is there a package with an interest in iptable |
91 |
| configuration for broadband voip qos configs? |
92 |
what i really replied for is to ask, if i can forward your email to a |
93 |
friend of mine who happens to be involved with telephony with his |
94 |
company, i know zero about that, i do know he does use VoIP, so maybe he |
95 |
finds your hack nifty |
96 |
|
97 |
| |
98 |
| Jim |
99 |
|
100 |
hope you better luck next time in #gentoo-dev |
101 |
|
102 |
Daniel |
103 |
-----BEGIN PGP SIGNATURE----- |
104 |
Version: GnuPG v1.4.1 (GNU/Linux) |
105 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
106 |
|
107 |
iD8DBQFCqlguUpKYMelfdYERAtt8AJ4p937DdhoHGKuhgKEO8V6QLfM+gwCdHCeJ |
108 |
d226J9epAw42oIsGkj0+5r8= |
109 |
=QAsX |
110 |
-----END PGP SIGNATURE----- |
111 |
-- |
112 |
gentoo-dev@g.o mailing list |