Currently, the project is not open source, even though there are plans for eventual open-sourcing in the future. There are two main reasons for this. First of all, the application is a part of a larger project catalog, which is hosted on bitbucket as a closed git repository. That means additional trouble when migrating if the source code history is to be retained. Not to mention the need to reevaluate the use of dependent projects (as seen in libs) and their inclusion to/exclusion from this affair

.
The second reason should be rather familiar for you: there is no point in forking an application that hasn't matured enough to be released. But it is always tempting, hence the standard situation of someone silently (or publicly) forking l2jserver, starting doing the same things as all people who tried previously, then running out of steam and dying off. The result is clear: hundreds/thousands of man-hours wasted on the same things and no winner at all. Everyone loses.
To sum it up, open-sourcing is planned with the release of version 1.0 (non-snapshot). Currently we are at 0.8, which means that a lot of internally planned features are available, hence my call to the general public for ideas. Namely, what else should be implemented in a controlled fashion, before people are free to rely on
internal implementation details, subject to change on any future commit at their leisure.
Basically, I am trying to build up a user base and make them familiar with what NetPro has to offer right now.
For example, the planned scripting guide will include details such as where to find the javadoc, as well as how the example scripts were written, one step at a time, as well as what can/should and what cannot be achieved with scripting.
But then again, you could just say that I don't trust that people can implement features efficiently. Still, my experience in the open source field shows that people are content with/biased towards the first implementation provided, even if it is half-baked. And especially in l2j/l2jfree, you can see countless examples where simple methods maliciously refrain from doing what their name implies. The biggest laugh was naturally about the l2jfree's scripting engine (which was pretty much the same as l2jserver's). You would think that script_load/reload builder commands load or reload a script, but you would be wrong. One example (of countless I had come up with to disprove the fact that it has ever worked) is trying to reload a script class that is not a leaf in the class hierarchy (best if it is abstract and has many child classes, that's just gold).
To sum it up: NetPro will go open-source
and I will continue maintaining it, but only when I deem the application/code base has matured enough.
P.S. There are also plans for proper localization, as done in L2JFree's Petition Manager and Vanity L2. Basically, localization with support for languages that are naturally more expressive than the English language, so that strings would not need to be artifically dumbed down when localizing the application, and thus the feel would be more natural for native speakers.