> Why would you give up? In this task of defining what > needs to be done, it is contrary views that are > important, it is differences that are important...
We could be discussing this 'till we're all blue in the face, but that won't get us anywhere. Code talks. Graphics talk. Audio talks. Documentation talks. Test suites talk. > What would you come up with if you work on the code > without understanding what ought to be the outcome ? This is not a paid-for effort, nor do people here sit and wait for someone to tell them what to do, or even better *demand* that X, Y or Z be performed in A, B, or C way. OpenSolaris is a vibrant community, but we have a realtively high "user" to developer ratio, disproportionally tipped in the "user" favor. The simple state of affairs is, we need more code and less discussion. > The problem with a long thread as this in a forum is > that no one seems to have the time to read through > the exchanges in an order, in the order in which the > discussion progressed, so most people react to bits > and pieces of the overall subject, rather than to > what is emerging as a whole. So the comments on what > one writes are not always fair. The problem is that this particular topic has been chewed over and over, and it basically comes down to users or would-be users of OpenSolaris *demanding* OpenSolaris deliver this, that or the other. And there also seems to be a tendency that those who are the most vocal in this particular demographics group happen to be the least willing to write some code, produce some graphics, audio or documentation, things that OpenSolaris needs and could really use and benefit from. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
