Hi all. A concept for a feature under BugId 359251

[Charlie Powell]

Although I don't know the too much of the internals of the app, I would be in favor of doing some minor database updates, including creating group and group_membership tables. This would be a more 'standard' approach, and should easily allow for adding users to the email queue. The drawback to this approach is anytime the user field is provided to the user, it would have to pull from two tables. 


----- Original Message ----- 
From: "Leon KUKOVEC" <leon.kukovec at gmail.com> 
To: developers at bugzilla.org 
Sent: Thursday, July 9, 2009 2:28:26 AM GMT -05:00 US/Canada Eastern 
Subject: Hi all. A concept for a feature under BugId 359251 

Hi all, 

My name is Leon. I'm working on a patch that will make 
Bugzilla 'email distribution list' aware. The same has 
been discussed under https://bugzilla.mozilla.org/show_bug.cgi?id=359251 

The idea is to use 'group membership' and regular 'user registration forms' 
and keep the changes to the DB schema minimal or if possible, 
avoid changes at all. 

Brief concept: 

Bugzilla Administration required: 
1. a new group 'email_list' is created to indicate that certain 
login_names are actually an email distribution lists 
2. a new login_name 'group1 at email.com' is created and given 
'email_list' group membership 
3. a new group 'group1 at email.com' is created to function as a 
container for all members in the list 
4. user 'john.doe at email.com' is granted a group membership of 
'group1 at email.com' group, indicating he's a member of the list 

Just with that, anyone can select 'group1 at email.com' and add it to 
Assignee, QA, CC or anywhere we put users. But this results 
duplicate e-mails if the members of the 'group1 at email.com' are 
also on CC, or. To avoid that, the code-base needs to be 
changed as described below. 

Bugzilla codebase changes: 
1. adjust the code in a way to "unroll/resolve" the login_names 
(e.g. group1 at email.com), which are actually mailing lists, 
to the list of login_names belonging to the group with the same name. 
2. when unrolled/resolved, make a union of all affected 
login_names to remove duplicates before sending e-mail 

Based on the current investigation this would have to be done in 
whine.pl and processbug.cgi and some 
helper method in Bugzilla::Group, etc. 

Please let me know whether the described idea seems reasonable or not and 
whether I should continue working on it or if something else is queued for 
the BugId 359251. 

Thanks. 

-- 
Best Regards, 
Leon 
- 
To view or change your list settings, click here: 
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=powellc@powelltechs.com> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20090709/79c0eb45/attachment.html>