Danek Duvall wrote:
Stephen Lau wrote:
I'm looking at porting add-gateling, and here's my current idea for how
to do it:
1. user foo does a clone (or pull)
2. map OpenSolaris.org username foo to their email address via webapp
3. lookup this project/repository in the app to find the notification
mailing addr for it
4. query mailman to see if that mailing addr is an opensolaris.org
mailman-managed list
4a. if not, then email that address and let them know this user
did a clone/pull
4b. if so, then call mailman's CLI to subscribe the user's email
does that seem reasonable with folks?
4a is needed in the case that projects only have one committer, and don't have
a mailing list for notifications, or for some reason or another don't have the
notification address set to an opensolaris.org mailman managed list. I figure
in that case, we can send an email saying:
"user foo ([EMAIL PROTECTED]) pulled a copy of scm-migration/ongk"
Sound reasonable?
Coupla notes:
- We're going to have to have two copies of a bunch of these tools,
at least through the duration of the internal mercurial repo, which
isn't going to have these fancy opensolaris things. I can probably
take what you write and massage it back to meet internal needs.
less work for me, and more work for you?
sounds good to me!
:-D
- 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.
- 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".
cheers,
steve
--
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
