Here are a few more thoughts on requirements, after spending 20 minutes or so looking through the Bugster functional specs.
* automated account creation (conditional requirement?). It should be possible to use one's opensolaris.org account to access the BTS. Example implementation techniques: (1) the BTS has an extensible authentication mechanism, so that we can write a plugin that talks to the opensolaris.org authentication service; (2) the BTS's account table is open enough that the opensolaris.org webapp can update it. * multi-release support (optional requirement?). It should be easy to match up a bug with the releases that the bug appears in, and to track backports. * audit trails. I know that US government regulations require a certain level of audit trail capability for the source (if you want to get the code security-certified). I don't know if there's a similar requirement for the BTS. I'd be faintly surprised if there were, but we should find out. mike _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
