On Aug 9, 2012, at 1:58 PM, Chris Hostetter wrote: > But many users don't know /think to search svn history -- particularly > when there is an official bug tracker and docs saying that they can search > that bug tracker to find out all about known bugs/fixes in particular > erions.
Yeah. > To be clear: i was definitely refering to the commiter opening a Jira to > track any bug fix they do based on annecdotal reports they hear about form > the mailing list, blog, stackoverflow, CPAN RT, etc... by no means is it > a good idea to tell people "we'll only fix this bug if you file it in the > right place" ... it's definitley more productive to say "thanks for > mentioning this, i've filed it in the official bug tracker and i'll take a > look" -- hell, that's usually helpful even if you don't have any idea how > to fix the bug. i do that in Lucene/Solr all the time. (it doesn't take > long ... half the time i just cut/paste the meat of hte problem and > include a URL to where i saw it mentioned) Great, as it should be. :-) > if you commit that code, based on that blog comment, and cite the authors > permission and hte blog URL in your commit message, you're *probably* ok > ... but what happens if the site hosting that blog goes away in 3 years? > what happens 2 years after that if the author of that code says the ASF > is stealing his IP? I would probably re-confirm via email before committing. > Is it likely? not really ... but it's the reason why it's a good idea to > get any "non-trivial" contributions "on the record" in the ASF mailing > list or ASF Jira instance. What you are more likely to see are pull requests on the GitHub mirror. Best, David
