I’ve finished a rough draft of some suggested procedures that we can implement to encourage more collaborative development of OpenJUMP. I am putting the document out there to stimulate some discussion among developers of JUMP, OpenJUMP, and the many different JUMP “brands”.
You can find the document in PDF format here:
http://thejumppilotproject.pbwiki.com/f/CDP.pdf
I think most of us recognize that we will all benefit from more cooperation. I don’t think it will be practical to merge all of the different flavors of JUMP running around, but I think we can do more to create a common foundation in OpenJUMP, and to ensure plug-in compatibility across flavors. I am hoping these suggested procedures, or some procedures based on them, will help reach those 2 goals.
The suggested procedures basically address 3 areas:
[1] Contributions to OpenJUMP’s core, made by an OpenJUMP developer.
[2] Development of plug-ins that will work in JUMP, OpenJUMP, and JUMP “brands”.
[3] A way for development teams to inform OpenJUMP developers of the changes that are being made to their independent code bases.
A number of things will need to happen for the procedures to be put into place and to work successfully:
[1] We will need to recruit some members that can reactivate the JUMP Pilot Project Development Committee.
[2] I will need to complete my proposed Java Package Naming Standard for OpenJUMP, and the Development Committee will need to revise and approve it.
[3] I will need to work on a GUI standard, and the Development Committee will need to revise and approve it.
It will take some effort to make all of this work, but I am confident that collaborative development of OpenJUMP will benefit all.
The Sunburned Surveyor
You can find the document in PDF format here:
http://thejumppilotproject.pbwiki.com/f/CDP.pdf
I think most of us recognize that we will all benefit from more cooperation. I don’t think it will be practical to merge all of the different flavors of JUMP running around, but I think we can do more to create a common foundation in OpenJUMP, and to ensure plug-in compatibility across flavors. I am hoping these suggested procedures, or some procedures based on them, will help reach those 2 goals.
The suggested procedures basically address 3 areas:
[1] Contributions to OpenJUMP’s core, made by an OpenJUMP developer.
[2] Development of plug-ins that will work in JUMP, OpenJUMP, and JUMP “brands”.
[3] A way for development teams to inform OpenJUMP developers of the changes that are being made to their independent code bases.
A number of things will need to happen for the procedures to be put into place and to work successfully:
[1] We will need to recruit some members that can reactivate the JUMP Pilot Project Development Committee.
[2] I will need to complete my proposed Java Package Naming Standard for OpenJUMP, and the Development Committee will need to revise and approve it.
[3] I will need to work on a GUI standard, and the Development Committee will need to revise and approve it.
It will take some effort to make all of this work, but I am confident that collaborative development of OpenJUMP will benefit all.
The Sunburned Surveyor
Posts
