<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi,<div><br></div><div>Wondering if anyone on the JBT team is interested in helping to fine-tune this idea and acting as a mentor for this year’s Summer of Code.</div><div><br></div><div>From the prospective GSoC student:</div><div><blockquote type="cite"><div dir="ltr"><blockquote style="margin-right: 0px;"><strong>Create Tattletale plugin for Eclipse</strong><br>Lot of tools have plugin for eclipse. (Findbugs, PMD...). Tattletale plugin for Eclipse does not exist, but this way it should be easier to use comparing to usage trough console . The basic implementation of this plugin could display standard Tattletale HTML report, but some sub reports like "Unused Jar" or "Multiple Jar files" could "mark" some referenced libraries displayed in the Eclipse controls and highlight them for removal.</blockquote></div></blockquote></div><div>I’ve been impressed with this student’s initiative so far, but unfortunately the original project he approached me about was already completed in last year’s round of GSoC.</div><div><br></div><div>I found GSoC mentorship to be a fun and rewarding process. It’s not too heavy on red tape, so most of the time you invest is actually spent helping with actual coding issues. There’s maybe 90 minutes of filling out forms over the whole 4 month term. Depending on the student, you might expect to spend 4-6 hours a week mentoring on the coding project itself: answering questions, offering pointers to good docs and tutorials, making sure they don’t stay stuck on one thing for a week, etc.</div><div><br></div><div>Cheers,</div><div>Jonathan</div><div><br></div></body></html>