search for: insular

...lunteers who preen through bug reports for the ones that are truly new and valid. They can request reporters to do further tests, and so on, before actually contacting the first line developers. More bugs will get reported more quickly, even if with a bit of redundancy, if you remove the emotional insularity toward reporting; while the first-line developers don't get overloaded, by using intermediaries. BTW, building this on FreeBSD 4.6-RELEASE resulted in several complaints of the form: (though, it built, and appears to work.) checking net/if_tap.h usability... no checking net/if_tap.h presen...

...externally? But that I think is more the exception than the rule & perhaps not worth including in the general practices document. But if you've seen several instances of this sort of issue that seem worth addressing through this mechanism - yeah, I'd be OK with an encouragement to avoid insular project areas where possible (especially where there's strong overlap) - seek external/long-term contributor input especially on design documents and early/foundational patches, and in general err on the side of seeking more input from code owners than not. If you ask too often for trivial thin...

The following construct is an ActiveSupport-ism: returning(Foo.new) do |foo| ... end I don''t especially like it, since it''s both more verbose and less efficient than the direct alternative: foo = Foo.new ... foo It doesn''t occur many times in Merb, so does anyone agree with me that it should be removed? I tried doing this (patch attached) and I find

...I > think is more the exception than the rule & perhaps not worth including in > the general practices document. But if you've seen several instances of > this sort of issue that seem worth addressing through this mechanism - > yeah, I'd be OK with an encouragement to avoid insular project areas where > possible (especially where there's strong overlap) - seek > external/long-term contributor input especially on design documents and > early/foundational patches, and in general err on the side of seeking more > input from code owners than not. If you ask too of...

...nowledge available at sites such as UBL.com and AllMusic.com make it much easier for newbies to get in the know and up to speed. Exclusion is out, and everything else is in; the sooner people let go of the idea of the exclusive contract, exclusive distribution agreements, exclusionary formats, and insular music scenes, the more they'll get out of this heady collision of music and the Internet. Eliot Van Buskirk, Senior Editor, CNET Music Center http://Music.CNET.com ------------------------------------------------------------------- --- >8 ---- List archives: http://www.xiph.org/archives/...

Yeah, +1 that people from the same organization are sometimes the only ones working on a certain feature/area. (certainly I'd expect some discussion about the feature in general to be discussed outside that group if it's in any way contentious - but some stuff's clear enough (I think I implemented debug_types years ago, likely with only Eric's approval, both of us being at Google