On Wed, Nov 29, 2006 at 05:25:13PM -0800, Stephen Lau wrote: > Danek Duvall wrote: > > > - add-gateling adds the address to two lists -- the notify alias and the > > announcement alias (note that we don't really have an internal > > discussion alias). It should probably do something similar here, > > unless we're expecting to send out flag-days on onnv-notify. > > Hrm... interesting question. Are people opposed to having flag > days/announcements go out to onnv-notify? We could still distinguish > them since the announcements won't have an X-scm-notification header. Or > we can just as easily create an onnv-announce list or something - but > it's going to have almost the exact same audience as onnv-notify.
I know people who are on onnv-gate but not on onnv-notify -- they don't care about each and every putback, because they're not regular developers, but they do like to keep track of what interesting is going on in the gate. I suppose such people could filter the putback notifications to /dev/null, but that seems like a high bar for something so simple. > > - In the case of 4a, I'm not sure that you really want to send the pull > > email to a notification list, even if it's external. You might send > > email to the puller saying that they should subscribe to the > > notification list, or send a message to the list owner (making a best > > guess as to what that would be, maybe), but not the entire list. Or > > will there be a pull notification list separably configurable from the > > normal push notification list? > > hrm... I don't think I'm understanding this. My take on the 4a case is that > a > repository administrator has put in a non-opensolaris.org mailman-managed > email > address in the notification field for their repository. We can't do anything > other than determine that it's not an opensolaris.org mailman managed list. > It > could be a non-opensolaris.org mailing list, or it could just be a private > individual. My proposal was to email that address (whether it's someone's > individual email address, or their own mailing list somewhere else) and say > "user foo has pulled your repository". I guess what I'm reading here is that this notification address they've put in is going to be receiving both putback and bringover notifications. Nobody cares about bringover notifications except for people and/or scripts that want to do what add-gateling does. So sending them to a putback notification list seems wrong. If you're suggesting that there be two addresses per repository (one for putback and one for bringover notifications), then you didn't make that explicit, but it would solve the problem. In the case of an external address, there's not a whole lot you can do to sign someone up to a list, but you can always notify the puller that this list exists and they should subscribe to see putback notifications. If you want to try to be super clever, you could try some typical majordomo/mailman subscription messages to the appropriately-constructed address, but that's probably overkill. Does that make more sense? Danek _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
