On Tue, 2007-08-07 at 15:35 +0200, Milan Jurik wrote: > Hi Matthew, > > V út, 07. 08. 2007 v 14:40, Kaiwai Gardiner pÃÅ¡e: > > On Tue, 2007-08-07 at 08:25 +0200, Milan Jurik wrote: > > > > > > But this happend, the responsible engineer took related RFE and you > > > could see that on bugs.opensolaris.org. I agree with one thing - bugster > > > is very good tool, but its public interface is not very useful in case > > > that you want to monitor some CR. > > > > Hence my leaning towards Bugzilla - people give it a hard time but it is > > easy to keep track of favourite bugs etc. etc. Much more > > 'collabortative' - you can actually update submissions etc. etc. all of > > that should be available on the bugster. > > > > It is in bugster, in very good way (in my oppinion). But bugster is not > open and that is the root cause of many issues, missing open CR > management.
If its available, how do I keep track of it? how do I update submitted bug reports? > > > > > And I don't know why File Events Notification API - PSARC/2007/027 is > > > > > not public. You can see who made the putback - ask him, maybe he is > > > > > not > > > > > reading this list. > > > > > > > > Its very hard to know when there is no name attached to the put back as > > > > far as I see. > > > > > > > > > > http://mail.opensolaris.org/pipermail/onnv-notify/2007-April/007227.html > > > > > > -> 6381975 solaris need centrino ipw3945 wifi support > > > > > > http://bugs.opensolaris.org/view_bug.do?bug_id=6381975 > > > > But these are hardly 'visable' forms of communication; its like saying, > > 'yes, there is documentation, read the source code'. > > > > I said it is possible, you must be more active. > > > > -> now you know ;-) > > > > > > And I think that Brian is very active even in community to help people > > > with this driver :-) He just worked hard to release something and even > > > at that time he was ready to communicate with those who wrote e-mail to > > > him (I know it :-) ). > > > > Then maybe its the opensolaris.org website maintainers not willing to > > create some buzz about what is being worked on. > > > > It is not osol.org website maintainers responsibility. > > > > That's typically PSARC and sometimes updates in Bugster. E.g. manpage is > > > written after driver completition. Which docu? > > > > The SPARC information before putting the code in. When it appears on the > > ONNV change, I want to be able to read about it straight away. > > > > Push on exact PSARC authors. > > > > > Communication doesn't have to go overboard, but a quick, 'this what > > we're doing now' would suffice - atleast show there is some pulse in the > > body - I go past parts of opensolaris.org and wonder if any of the > > people involved are alive because its so quiet. > > > > I think there is good pulse in the body and you can see that in many > projects on osol.org, you should monitor more than just > opensolaris-discuss list. > > This is open source world, nobody should dictate to others on which > level they are communicating. I came from open source world and know the > difference. I'm not dictating, just fed up with the whining that Linux gets all the mindshare and yet there is a lack of cheerleading pulling in the developers - sometimes you need to have some 'temptations' hanging on the outside to bring people in. To get customers/endusers and developers, you actually have to do something - when a new user or developer asks a question, don't abuse him to buggery and claim he is the one with the problem. Listen, absorb and converse. Solaris isn't an 'extension' of ones inner being, its an operating system. So when someone does criticise Solaris, take it on board. Matthew
_______________________________________________ opensolaris-discuss mailing list [email protected]
