On 5/1/10 2:01 AM, Richard L. Hamilton wrote: > I would very much like to see someone compare the OpenSolaris section 3* > man pages to The Open Group Base Specifications Issue 7 / > IEEE Std 1003.1™-2008 > see what's what's missing, and get busy adding it.
It sounds like this is your particular itch, so ... > I would even do some of the research and coding myself. What I won't > do is spend a lot of time arguing about it and jumping through hoops. What arguing or hoops are you referring to? In general, trivial changes require trivial review. Want to add strnlen() or something like that? Cool. It'll take a couple of short email messages, and you're done. In more detail: one short email message to describe the function (or better, yet, *functions* -- no sense wasting people's time on one tiny bit at a time, if you can avoid it) for architectural purposes. Another to ask for code review from a competent reviewer. One more to get a sponsor. And that's it. None of these are complex. All of them should be very much shorter than _this_ reply. Non-trivial changes require more substantial review. If you're suggesting adding functions that (say) require every file system implementation to be modified to conform with some new feature set, then the implications of that (and of the ones that lag behind) will need to be explored. Perhaps most importantly, you have to go into any project with the expectation that the folks around you, though they may have different motivations and viewpoints, are fundamentally trying to do the right thing. If you start off by describing the process required to do engineering work on a large and complex product as "hoops" and "arguing," then I think you're probably already off on the wrong foot, and you're going to have a very tough time of it. -- James Carlson 42.703N 71.076W <carls...@workingcode.com> _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
