From: Dennis F. <de...@co...> - 2002-07-06 10:45:44
|
Hi Marshall, I've designed it for use on our lan-party organisation as you can read in the install files. We have 3 specific groups. (Well 4 if you count the site-admins in) - organisation - webdev - crew Some tasks must be shared between org and webdev, some only webdev and crew gets to see the least amount of tasks. So we use groups to hide tasks for just a single group. Example: - financials should only be accessible by the organisation - web and database passwords should only be accessible by the webdev So it's more of an mix-and-match stratgy then to use the taskgroups for further grouping above usegroups. It's just a handy way of giving people access. Taskgroups are more a cosmetial function (a nice way to sort tasks) then a real strategy. Greets, Dennis ----- Original Message ----- From: "Marshall Rose" <mr...@db...> To: <cor...@li...> Sent: Friday, July 05, 2002 7:43 PM Subject: [Core-lan-org-devel] task groups and user groups, part deux > so, i think i understand how the code treats task groups and user groups, so let me ask another question: > > what strategy do administrators use for allocating the different kind of groups? > > for example, say i have a company with four groups: administration, development, operations, and sales. do folks create a user group for each one of these, and then create multiple task groups for each category (e.g., development -> db, www, sec, and so on). > > i realize that the administrator can utilize whatever works best for them, so i'm asking what strategies are people using. > > thanks, > > /mtr > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Bringing you mounds of caffeinated joy. > http://thinkgeek.com/sf > _______________________________________________ > Core-lan-org-devel mailing list > Cor...@li... > https://lists.sourceforge.net/lists/listinfo/core-lan-org-devel > |