[pago]

Based on recent discussion I wanted to share a couple of possible tasks that do not require much knowledge of SimpleEdits internals (most of them require non at all). They're not sorted in any specific order, if you're interested in solving one of these tasks, just contact me and you'll get the required information. Some sound really boring but are still necessary and must be done.

Collect licenses
SimpleEdit comes bundled with lots of 3rd-Party libraries but the license-directory does not contain licenses for all of them. Thus this task is basicly: Find the website of the library, look for their license file, create a LICENSE.[lib-name] file for each of those. Simple, boring, yet necessary.
Requirements: You should know how to use Google...

Create a new build-system (build.xml)
I've reorganized the complete project structure 'cause the old one evolved over time and was not useable any longer (hard to understand, hard to find stuff in, not a good start for new developers).
As a result of this the old build-system is broken. This task involves writing a build.xml that compiles and fully builds SimpleEdit, including read-to-use packages for Windows and Linux (deb-files).
It also got more complicated because I plan to write parts of SimpleEdit in Groovy and the build file should compile these files like any other Java file (there is an Ant-task for this and it's capable of compiling interdependent Groovy/Java-files).
Requirements: Know how to use Ant / how to build packages for linux/mac (optional).

Preconfigured projects for IDEs
Some people who actually wanted to try to develop on SimpleEdit failed because they were unable to configure their IDE in a way that it could handle SimpleEdit. Thus it'd be useful to offer some preconfigured projects for the major IDEs (NetBeans, Eclipse, IDEA) or at least some documentation on how to setup the IDE for SimpleEdit.
Requirements: You must know how to use at least one of NetBeans, Eclipse and IDEA.

SimpleEdit website
I've paid a graphics artist to develop a new design for the SimpleEdit website. We'll still need to implement it in HTML (I've already written an template, so it might not be needed anymore) and put it into a CMS (which would've to be chosen based on the sites requirements). And perhaps it'd be a good idea to explain to me how to use it...
Requirements: Knowledge of XHTML and CMS.

Modularize the old code base
I've mentioned above that I've restrucured the project. Part of this was to modularize the project structure. For example: PHP-support was part of the core-module before, now it is supposed to become a module of its own.
I've also removed a couple of old libraries and replaced them with new ones. As a result some of the modules will no longer compile.
Therefore it would be useful if someone would support me in making the transition towards the new structure by creating (copy 'n paste) and transitioning the modules towards the new libraries.
Requirements: Java (medium level knowledge should be enough).

If you're interested in taking on one of these tasks, please let me know.