Please refer all followups to this thread over to the [EMAIL PROTECTED] list.
On Fri, 2006-06-23 at 11:27 -0700, Stephen Hahn wrote: > * Erik Trimble <[EMAIL PROTECTED]> [2006-06-23 11:15]: > > It is a good start (yes, I know it's an interface to Bugster, just as > > the Java one I pointed out is too - in fact, it's probably the same > > code). And, I'm certainly not complaining about how well people have > > been taking to and addressing bugs. > > > > However, there are some significant shortcomings with the interface that > > need to be fixed. And, yes, this is true w/r/t the OpenSolaris community > > as a whole. Basically, the problem is that the OpenSolaris portal > > itself is extremely primitive, and really needs a big overhaul to make > > the information we have easily accessible in a coherent manner. > > Please come to either of website-discuss or tools-discuss and share > your thoughts for improvement (or at least de-primitivization). > > > And, in addition, the bug portal isn't really useful for helping manage > > external (to Sun) contributors work. And it doesn't given any real > > insight into who's working on what, and what schedules might be. > > I am not sure whether you are commenting on the lack of publication > from the internal database (which may have this information), or the > lack of this information more generally. > > - Stephen As several others have pointed out, the current Bug/RFE interface is seriously broken for non-Sun users, and is missing quite a bit of functionality (both in the interface and in the data being stored) even for internal Sun folks. Off the top of my head: 1. The categories for bug submission and searching really need to be rethought. At the minimum, the search function should probably be more in line with the various communities on OS.org. That is, you probably should have main categories which line up with each of the O.S. communities, with subcategories being more specific. 2. Viewing bugs is a mess - access varies widely across external and internal users, bugs aren't consistently found/displayed, etc. 3. There is no development schedule information stored/available. e.g. when a particular Bug/RFE is expected to be fixed/included. 4. Who is working on a bug/RFE isn't available. 5. External users are effectively shut out of the bug/RFE database. It should be possible for a (properly authorized) external user to both update a bug status, and/or take ownership of the bug/RFE. 6. A better community-centric bug/RFE prioritization method needs to be developed. 7. Bug/RFE bounties need to be considered, along with a method of funding and payout for them 8. The UI for the whole Bug/RFE setup needs a drastic overhaul to make it simpler to view multiple/related bugs. -- Erik Trimble Java System Support Mailstop: usca14-102 Phone: x17195 Santa Clara, CA Timezone: US/Pacific (GMT-0800) _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
