A real data feed from bugs.webkit.org of the user names would be best. :) If we had one for svn.webkit.org then we wouldn't need commiters.py at all. Commiters.py is a hack around lack of available data from our servers.
Also, we keep hacking bugzilla, and yet our bugzilla is still years-out-of date. Seems we should upgrade to 3.x before we hack it much more. (One of the reasons why working outside of bugzilla via <iframes> to the EWS status server for the bubbles, or a browser extension for the autocomplete data is better than trying to hack our ancient bugzilla.) -eric On Thu, Jun 10, 2010 at 4:08 PM, Ojan Vafai <[email protected]> wrote: > On Thu, Jun 10, 2010 at 3:55 PM, Maciej Stachowiak <[email protected]> wrote: >> >> On Jun 7, 2010, at 2:30 PM, Julie Parent wrote: >>> >>> Thank you thank you thank you! >>> >>> I'm happy using this as a Chrome extension, but if there is enough >>> interest to have it added to Bugzilla directly, I can do it (I already have >>> a local bugzilla running for the Rietveld work). >> >> I think this would be a good addition to bugzilla itself. > > > > I agree. I just did it as a Chrome extension because I could do so as a <1 > day project. It would be relatively simple to do if the CORS headers were > added to trac or svn.webkit.org as Adam suggested. > > Also, I tried porting the Chrome extension to a Safari extension. After much > wrangling, I couldn't get any content scripts to load though. The other bits > of the extension (e.g. the global page) loaded fine though, so it's not just > like I don't have extensions enabled. If someone from Apple wants to help me > debug, I'd be happy to get this working. > > Ojan > > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
