hi faidon, i do not think you personally and WMF are particularly helpful in accepting contributions. because you:
- do not communicate openly the problems
- do not report upstream publically
- do not ask for help, and even if it gets offered you just ignore it
with quite some arrogance
let me give you an example as well. git.wikimedia.org broke, and you, faidon, did _absolutely nothing_ to give good feedback to upstream to improve the gitblit software. you and colleagues did though adjust robots.txt to reduce the traffic arriving at the git.wikimedia.org. which is, in my opinion, "paying half of the rent". see
includes details how to take a stack trace
- upstream bug:
https://code.google.com/p/gitblit/issues/detail?id=294, no stacktrace reported
Lets not point fingers at specific people. Its really unhelpful and causes defensiveness.
In the case of gitblit, the problem at this point has been identified (web spiders DOSing us accidentally). Its really not surprising that creating zip files ~100mb on the fly is expensive. It doesn't really seem that likely that a stack trace would help solve such a problem, and really its more a config issue on our end than a problem with gitblit.
I really don't see anything wrong with what any of the wmf folks did on that bug.
-bawolff