NukeCops - Joining and combining together the resources, knowledge and forces

How to increase the sustainablitiy, synergy and cooperation between two projects - a discussion about the best path ahead for NukeCommerce and osc2nuke -

now even more sustainablitiy and synergy is possible (a brandnew hot discussion about best practice) - jump in and discuss witouth registration!

osc2nuke and NukeCommerce.org allready are great examples for joining and combining together the ressources, knowledge and forces - eg. on phpnukefiles.com [with more than 2500 dual-use modules blocks & hacks]. Altogehter they re joining together one of the largest socio-technical-network under the sun by Fostering cooperation on the Internet:

jump in and (see the discussion) on one cvs with two branches of - NukeCommerce and osc2nuke - a roadmap-discussion how to increase the sustainablitiy synergy, cooperation between two projects ...[read on for more]

demosite of 7x6 up now

Pro: Avoid future duplication of work, cooperate to make both projects better.
Con: Need to overcome various differences; in opinion, coding style, and language

In my opinion, #3 is our best option. I've been talking to the developers of osc2nuke. It is pretty clear that merging the two projects is out of the question, due to our different goals. Osc2Nuke does not ever plan on including the extra modules that are shipped with NukeCommerce, such as Gallery or Calendar, nor any of the planned OSC modules.

They told me they are not opposed to us using the current or upcoming osc2nuke as the basis of the next NukeCommerce, so long as we give credit in the code. Since it's all GPL, this should be no problem, as they maintain the copyright, and we are free to use and modify their code. They are also welcoming torwards new developers.

I think both teams can work together, without having to sacrifice the independence of their project.

The first thing we have to agree on is a CVS repository. This will allow us to keep our work in sync. We will start by importing the code for osc2nuke 7x6. Both teams will hack on this, making sure it is stable, working, and secure.

Once it reaches a certain level of stability, we will create a NukeCommerce branch in CVS. The NukeCommerce team will then add all the extras to their branch. Their focus will be on integration and stability.

While the NukeCommerce team is working on their branch, the Osc2Nuke team will be working on the main branch, incorporating the latest and greatest OSCommerce and PHP-Nuke as they come out. When the trunk stabalizes again, we create a new Nukecommerce branch, and the cycle continues.

---
Comments?" end of cit - travel over and discuss with all others.

man - the ideas were very interesting.