| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Dan Meltzer wrote: |
| 5 |
> This time I'll say something useful :) |
| 6 |
> |
| 7 |
> Nathan, you seem to be misunderstanding open source. You get the "I |
| 8 |
> can ask for features or suggest things" part, but not that "I can add |
| 9 |
> features or do things part". No one is stopping you, or me, or an |
| 10 |
> average joe, or George W. Bush, from "peer reviewing". You can see |
| 11 |
> the basic things that are commonly wrong by looking at a few |
| 12 |
> "resolved""wontfix" bugs with ciaranm as the commenter. Most make the |
| 13 |
> same mistakes. After seeing this, what is to stop you from either |
| 14 |
> manually looking through the tree, or writing a script to check for |
| 15 |
> you, and fixing some of the problems, submitting them as bugs when |
| 16 |
> they are fixed. |
| 17 |
|
| 18 |
No, I understand what you're saying completely. I've been using F/OSS |
| 19 |
for about 10 years now, and I've been an engineer/programmer for about 5 |
| 20 |
of those. So I know a little bit about both sides of the story. And I've |
| 21 |
actually submitted an ebuild for thunderbird (although it was really |
| 22 |
just an integration job of a couple of existing versions), so I'm |
| 23 |
certainly not unwilling to get my hands dirty. |
| 24 |
|
| 25 |
> I cannot imagine any developer would say no to a |
| 26 |
> well written ebuild, they may wait for a version bump to switch to it, |
| 27 |
> but they most likely would not ignore it all together. |
| 28 |
> |
| 29 |
> Hell, maybe if you do a good enough job, and show enough devotion, the |
| 30 |
> gentoo guru's will even think about making you a developer in charge |
| 31 |
> of fixing those things. who knows? |
| 32 |
> |
| 33 |
|
| 34 |
My experience with Gentoo is that certain developers ignore user |
| 35 |
submitted ebuilds, bugs fixes, etc. and claim its a manpower/time issue. |
| 36 |
Yet they fail to court the user submitting the ebuild into becoming a |
| 37 |
developer too (thus helping relieve the manpower/time issue). And this |
| 38 |
isn't me wanting to get noticed, mind you; I'm talking about other users |
| 39 |
who regularly submit ebuilds and get ignored. So you end up with the "in |
| 40 |
crowd" capable of making Gentoo better and the rest forced to either |
| 41 |
fork or just go away. Chris even told Ciaran to not look at a user |
| 42 |
submitted ebuild because it was the games group's territory. Yet the |
| 43 |
games group 'FAQ' complains about how little time all of those dev's |
| 44 |
have. Wouldn't it make more sense to recruit those folks and make your |
| 45 |
team more capable of handling the load? THERE is your cathedral. |
| 46 |
|
| 47 |
And again, thats just one example and not indicative of the entire |
| 48 |
Gentoo dev team (or the entire games team for that matter). |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
-----BEGIN PGP SIGNATURE----- |
| 53 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 54 |
|
| 55 |
iD8DBQFDCIW92QTTR4CNEQARAvPuAJwPipryDRbAo/j7IrZCfavIbUP8HQCgglUt |
| 56 |
j51c5mPa0SyDZezeGg+FJJ0= |
| 57 |
=rHOS |
| 58 |
-----END PGP SIGNATURE----- |
| 59 |
-- |
| 60 |
gentoo-dev@g.o mailing list |
Archives