On 05/03/10 23:49, Robin H. Johnson wrote: > Known prototypes: > ================= > http://dev.gentoo.org/~rbu/assign.py > - I believe this prototype is fully up to date, it just takes > herds/metadata.xml as well as a string, and gives you the output the > commandline. > rbu: can you confirm that your prototype matches the proposal?
I have fork of that laying around here: http://git.goodpoint.de/?p=eassign.git;a=summary When rbu and I last talked about it we came to the conclusion that the tool serves several distinct use cases .. - backend use by bugzilla - command line use on package X, even without a bug - security team usage (forgot the details) .. and that they need to be split smartly to keep each working in a shared codebase. python modules and three entry point scripts on it could work. I know that neither rbu nor me have resources for the code of this atm, maybe idl0r has? I'd like to be notified on progress, though. Two regex related things I'd like to append: - I've been using this alternative regex for but title extraction elsewhere before, seems to work well: package_pattern = re.compile('\\b(?P<category>[a-z0-9_+-]+-[a-z0-9_+-]+)/(?P<package>[a-z0-9_+-]+(?:[a-z_+]+[0-9]+|[a-z0-9_+-]+[a-z+]+))') - If you stick with the original pattern, this patch may still help: http://git.goodpoint.de/?p=eassign.git;a=commitdiff;h=7ad3cd607589aba7a1528dbd0744a942d18065eb > How is it integrated into workflow? > =================================== > [..] > 5. Javascript then appends the server results into the "Additional > Comments" box: a suggested assignee and suggested CC values, with logic > as to why. assign.py does not explain reasoning, yet. > Assignment/CC computing: > ======================== > Step 1 - Summary line processing > -------------------------------- > [..] > 3. Process ALL atoms in the summary line, using any after the first for CC > only. (new in v4) I'm unsure about the handling of order: it wouldn't work well for "dependency foo/bar missing on foo2/bar2". > Step 2 - Metadata.xml contains only a herd > ------------------------------------------ > 1. Take the herd element, and look up the herd in herds.xml to convert > to an email address. This email address must be a valid bugzilla > account. This may need a replacement map. Think media-video versus video, perl-bugs versus perl, etc. Best, Sebastian
