On Sun, 2005-08-21 at 10:10 -0400, Nathan L. Adams wrote:
> I'm starting to do just that. I've even asked Ciaran to review a
> particular ebuild I was interested in so that I could learn from it.

That's still not *you* doing the actual work - that's you requesting
someone else to review your work - which is good, but a totally
different topic which doesn't really belong in this thread, imho.


> That is handy, thanks. I don't see the IRC channel listed here:
> 
> http://www.gentoo.org/main/en/irc.xml
> 
> So I've emailed [EMAIL PROTECTED] and asked to have it added. :)

Ok.

> > If you so desperately want code review in Gentoo, why don't you do what
> > every other open source software developer has to do to get his ideas
> > through: put some work into it yourself?
> 
> See above.

See above what? The part about you requesting someone to review your
ebuild?

> Of course not. But the IEEE *is* all about peer review (as all
> scientists have been for the last few hundred years). And here is a nice
> high-level article about the benefits of peer review while developing
> software for the non-believers :)

I'm confident that most Gentoo developers agree that peer review is a
nice concept - but... I think you need to sit down and participate in an
open source project to fully understand how it works. You can't just
step forward and say "this is good, you need to do this" as a bystander
- that's not how the open source spirit works.

If you on the other hand step forward and say something like "I've spent
the last x months reviewing your code and developed a small set of
utilities for doing so, would you be interested in a wider use of
these?" I think you'd get a much better welcome.

In the open source community this is also known as "show me the code" as
in: if you want something done, you'd better be ready to back it up with
code and/or actions. Basically, you'll need to put more than words into
this, if you want to see it happen.

Regards,
Brix
-- 
Henrik Brix Andersen <[EMAIL PROTECTED]>
Gentoo Metadistribution | Mobile computing herd

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to