These are the tools we have pretty much settled on as a team. For ease and consistency of development please try to remain on these tools and discuss with the team before introducing competing technologies.
At this point we don't have any strict licensing requirements, however to maintain flexibility we have to be careful about licenses for software we choose to incorporate into our system. The best licenses are open source licenses without copy-left provisions (e.g. Apache License) that give us maximal flexibility in what we later do with the code base. Some strong copy-left licenses (e.g. GPL) would impose licensing requirements on us (e.g. force us to use GPL ourselves) if we chose to redistribute the code base at a later date. For now, we should just be aware of the mix of licenses incorporated into our projects, and have a bias for open source, non-copy left licenses.
http://svnbook.red-bean.com/en/1.1/ch04s02.html#svn-ch-4-sect-2.1
The eclipse plugin for svn generally does a decent job moving files and directories. See also http://svnbook.red-bean.com/en/1.1/re18.html
Here is an example:
svn gets really upset though when you do more complicated things like created a file, delete that file, then make a directory with the same name in the same location as the deleted file. (but that is a pretty odd thing to do anyway)
When in doubt, make a developer branch and try it there first.http://svnbook.red-bean.com/en/1.1/ch04s02.html#svn-ch-4-sect-2.1
Have a large blob of JSON? Want to see it in human readable format? Toss it into this web ui: http://jsonformatter.curiousconcept.com/
Don’t waste your time with drawing programs when you can just write something similar to psuedocode.
Browse lucene indices with Luke http://www.getopt.org/luke/