I don't have any specific instances that could be moved on, the discussions in which I heard of this occured a while back (Early August?) and I wasn't directly involved, I just saw grumbling roll by and I mentally noted it.
At this point in time man page changes very well may not be an issue, I've not tried to make a change and therefore don't have a firsthand account. If the the processes are in place (and based on the reaction here, I would assume they are) then I'm glad to hear it. I'm really happy that your all taking just the mention of a problem with the process seriously. Thats reassuring and a sign of your commitment. :) Just to make us all aware of how best to handle man page changes, whats the best/proper way to submit them? Can we put that information on the Docs community page? benr. Susan Weber wrote: > Ben: > > I'm a little distressed to here that contributors have been frustated > by the ability to get code changes to man pages incorporated. While I > ackowledge that the path for change is far from clear right now, I > need to better understand the problem. > > So far, the ON C team has not flagged any of the OpenSolaris changes as > requiring man page changes. Can you send me some specific issues so > that we can flesh this out. I really want to make sure that our > processes address this going forward. > > -Sue Weber > Program Manager, OpenSolaris Documentation > (650) 786-5467 > >>> >> The man pages aren't of much interest to me, really, at least they >> are low on my personal list. But, I consider the man pages as >> something to fast-track because of the work being done on the code >> side. Some code contributors have been frustrated by the inability >> to get changes or corrections made to man pages, etc. Right now, >> today, they are the most important because they are already up and >> running and producing, and any barriers that can be removed from >> their paths, should be. Coders come first. >>
