On Thu, 29 Jan 2009, Glynn Foster wrote: > > On 29/01/2009, at 5:34 PM, Max Kanat-Alexander wrote: > >> On Wed, 28 Jan 2009 17:30:13 -0800 (PST) Valerie Bubb Fenwick >> <valerie.fenw...@sun.com> wrote: >>> Is it possible to share administrative ownership/rules across >>> products? That is, define it once & apply it to new "products" >>> as they are created? >> >> No, not really. Although you can define a group and just set >> that group as the "editcomponents" group for Products after they're >> created. > > We've been doing this for a number of other products currently on > defect.opensolaris.org, and after the initial setup, seems to work well.
Hi Glynn - What I'm really getting at is to see if there would be a way to set up a product or a group of products that only a subset of the administrators could modify. right now, as far as I can tell, all administrators can administer everything. For source in the actual production code base, Stephen, Scott & I had previously agreed on having limited administrators having access to that. Like how internally we have "product owners" in bugster who control what can & cannot be added as far as new subcategories and release/build values. What we have for bugster (internally) are essentially a set of administrators who will not allow changes w/out product owner approval. If we cannot actually set up administrative priveleges so that only "production" admins can control certain aspects, perhaps we'll just have to have a rigid set of administrative policy. Valerie -- Valerie Fenwick, http://blogs.sun.com/bubbva Solaris Security Technologies, Developer, Sun Microsystems, Inc. 17 Network Circle, Menlo Park, CA, 94025. _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
