Hello.
We are using OpenMap trunk (aka v5b) in production and has done so over a long time. Both in a swing client and a wms server. The code is working just fine.
The project, however, is not in good health. The lack of a v5 release is not a problem for me, but the fact that OpenMap is so locked down to BBN has become a greater problem over the years. From time to time, I send in a patch. This is now done be sending the patch to Don, who then merges it with his own work. And then, some time later, Don send his work to a person in BBN. This is not a very smooth and open process.
My wishes for OpenMap would be the following:
#1) Move the code base to a distributed version control system like mercurial or git to make it easy to contribute.
#2) Switch to a true Open Source license like BSD, MIT or Apache. LGPL is also fine, but not GPL.
#3) Allow for non-BBN committers to the main branch to open up the project and spread the workload of handling pull requests.
#4) Start working on a v5 release.
With #1, #2 and #3 in place, the people in need of #4 can start working on it instead of waiting.
Regards,
Tore Halset
Long time OpenMap guy
On 5. okt. 2011, at 16:52, phil.kelso_at_l-3com.com wrote:
> There hasn’t been an upgrade in nearly 3 years and the last post I found related to v5 was dated July 21 asking when v5 would be non-beta. There was no answer to that.
>
> A June 15 post by Don said version 5 would be out “very soon”. Four months later and v5 is still beta. Do you know when v5 will be non-beta?
>
> Phil Kelso
> L-3 Communications/Greenville
> 903-457-5502
>
--
[To unsubscribe to this list send an email to "majdart_at_bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]
Received on Wed Oct 19 2011 - 06:52:17 EDT