Hey folks,
Thought I'd pop back in after my requested hiatus.
I notice that your development community is very busy and perhaps over
committed. May I suggest that approaching only the developer crowd may
return positive support in general but a lack of ability to administer
the proces? When we went thought the simmilar process in the GRASS
community we relied mainly on the user community with representation
from from the developers. If you think that that are more users than
developers (hopefuly) then it it not make more sense that the user
community can contributed to this process more than the developers can.
Often users want to contribute to Open Source projects but are not
commited to producing code or maintaining documentation. This would be
an opportunity for users to have a lasting impact on JP and leave a
legacy. Remember that we are all about an open community (or at least
that is what I understand Open Source to be), so why close out the users
in this process?
Second, I am sure you are aware of Degree entering OSGEO incubation...
http://www.osgeo.org/node/723
Since they have a version of jump, would it not make good sense to work
with Degree to get the core of deeJump (mainly Jump Pilot) into OSGEO.
I saw discussion of Vivid Solutions, but what about Degree and what
about Refractions (as they also developed the initial JUMP
http://www.jump-project.org/project.php?PID=JUMP&SID=CRED)
My final thought is to address some of the concernes that joining OSGEO
will change how you operate. If you are an open community with
transparent processes then there should not be any negative changes.
Some positive changes might come out that will strengthen the project
though. On the other hand if JUMP calls itself an open source project
but does not realy play the open source game, then the reservations
might be well founded as OSGEO would only want to adopt transparent and
open projects.
We all know of Projects that call themselves open source but you could
never contribute code or influence the direction of the project because
the project is run as a closed source project that gives away its code
but never allows contributions because it is held captive by a few key
players. A closed club with free source code that dies when it forks.
Again, OSGEO wants to avoid associating with such projects. Their
processes are in place to ensure that contributors are protected and
users can exercise their rights under the license.
Some thoughts.
Cheers
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
