We need a new, more modern looking website.
Probably most of the old sections can be removed. I'd rather have a small description, bug descriptions, plugins / extensibility with APIs, and in-detail tutorials on how to use SpotBugs from different tools:
We also need new graphics... anyone an artist?
I just published a simplified website with responsive design.
I got rid of several sections. Instructions are still missing, and probably will remain that way until we release and are sure what pieces have been kept.
I'm not sure what to do with the manual and sysprops. The manual could use some cleaning, and I'm not sure we want to support those sysprops (which are incomplete and outdated anyway). So far I left no link to those, but we will see.
I am also not sure of keeping the Japanese and French translations of the bug descriptions, since I doubt we will be able to maintain those moving forward (I know no French, and my Japanese is too rudimentary for this task).
i'm fine with nuking the translations
I'm Japanese, I will handle Japanese language translations. I'll watch this issue.
But I also agree that moving forward is the highest priority for now.
@KengoTODA Thanks for volunteering! You work on setting up Travis for FindBugs has been most useful to us when setting it up for SpotBugs.
I can help with the website design. If I can get a basic layout to start from, this would help to support mobile and tricky resolutions.
Awesome! There is a basic responsive layout in the current site repo https://github.com/spotbugs/spotbugs.github.io
Feel free to start from there or fresh with Bootstrap or whatever you feel like.
@jsotuyod Do you have an estimate when you guys are hoping to release 3.1.0 ?
I would try to find some time before that..
@h3xstream not really. As soon as posssible.
As far as I can tell, only #6 and #78 are blocking for a proper 3.1.0 release. We may also want to review the situation with jsr-305
@jsotuyod If possible, it's better to fix #60 by #69 before we release 3.1.0.
In my understanding, BCEL 6.1 is necessary to fix this problem, but not released yet.
@KengoTODA I guess the best we can do is ask @garydgregory and @mebigfatguy for eventual release plan on BECL 6.1.
#112 proposes new manual pages, please check.