What is commercial about XOOPS? As far as I know XOOPS only acquired the .com name as well for promotional purposes.

In my point of view XOOPS can serve some commercial purposes for consultants, designers etcera. The code itself is openSource and bound to the GPL license. Nothing new about that...

I have more modules and themes and languages for xoops2 than xoops.org ( now xoops.com , commercial ) - and today the project was replaced again by Mithrandir and xoops, because Mithrandir think that is inative.


The real XOOPS is japonese. This is a commercial project that use the same name, and incompatible with my ideas about opensource.

Here is:
http://www.xoops.com

Quote:

Yep, still around .. with all kinda forks flying in the blue sky

Now seriously ppls, the whole forum is full of forks staff, leave this whole staff behind, everyone here got scared from nothing...
This community is solid as an open soource community can be. amasing future ahead with this Xoops 4 "Xoosphere" Development ... I had to read it 4 times till my tired brain got over all those "forks" "forks" yals in here ...

A few interesting modules also released ("Membership Module" is very interesting, CBB is great, Weblinks is a great replacement for mylinks, plus the fact that google like it A LOT) .... and the "efqDirectory" is gonna come soon (I hope) .. so all is good then ever ... stop yalling, my newborn baby is crying less ...

You know the story about the kid that scared everyone by shouting "WOLF" "WOLF" .. and nobody belived him anymore ... but you see, Now the Wolf is back ... you can stop shouting

Let's focus on the good staff here, which is US, building together a thing which is BIGGER then US.

P.S. .. just finished a new project (not a XOOPS one unfortunatly) which I'm very proud of...http://www.netanya.muni.il/Tourism/ ...) so I'm free again for a little xoopsing

It seems everyone is going on about XOOPS being forked and how this is doing damage to Xoops, but the fact is that i would even call it a fork. The Japanese community are creating a XOOPS for themselves and it is still called Xoops.

Seems to me that both versions will work together at some point coding wise.

The fact is that XOOPS was forked two years ago and is still here and I am sure that XOOPS will be forked again, but the fact is XOOPS will still be here and with a very good user base.

Now lets get back to basics and get the job done at hand ok.

A group is its own worst enemy.

This seems strangely appropriate right now.

i'm not gonna comment on the rest, but a fork would mean a different cms completely going in different directions.. XOOPS will keep it's current direction.. so y are you worried??

if a fork happens, so be it, you then have another cms system to try out.. but that doesn't mean XOOPS will stop..

if you read the rest of the recent threads regarding XOOPS issues and problems, gripes etc.. you will know that things are being done.. how many times does that have to be repeated?

as for

Quote:

are they easy to fix? y not offer your expertise if you think it's easy.. how can a security issue be easy to fix if it's not known in the 1st place.. you say there are security issues? are there?

there probably is yes.. maybe.. but DO you know what security issues there are? i seriously doubt that, if you do, y not *work* with the devs to solve them? you said it's easy..

people keep mentioning security and patches etc and y they aren't patched.. but what security issues do you want patched? if you are referring to all the hype regarding the argument between skalpa, mith and Onokazu then i'd read up some more.. if you think that issue was disregarded, then think again.. what was the outcome of the argument? the argument continues, but the token system *was* implemented in XOOPS 2.0.10 so to say things don't get patched is completely wrong..

Over complicating things, yes, guess that's just human nature. My comment on your understanding might have been a little harsh and even wrong, but there was just quite some irritation I had to get out. You're not the only one who's stated that everything is easily fixable and telling Xoopsers to 'just do it better....'

I'll just leave it at that

Quote:

But that's not easy.

That's the fundamental cause of the "forking".

Quote:

As geeks, nerd, coders, or whatever we have a way of over complicating things sometimes. The issues I stated are easy to fix if everyone WORKS TOGETHER.

As for my "complete lack of understanding concerning open source as a whole and XOOPS as a part of it" I'm not real sure why you felt the need to question my understanding of these things but you don't know how wrong you are and I'm going to leave it at that.

Quote:

I really don't know, but there is a lot more to forking a community project like XOOPS than changing the code. The forks need to recruit their own user base, developers and establish their own communities etc etc. Not everyone will leap onto a new fork overnight, it may or may not be successful and it might take quite a long time to get it moving.

The strength of the original (ie. this) XOOPS development path is that it already has a large user base and community. It is well supported, and if you have a problem its pretty easy to get some free advice on how to fix it. That's all available right now. Maybe the forks will offer some technical advantage that you will find useful, but you might also want to consider whether the support of a large community is important to you or not, and whether you are willing to take a gamble with something new, or at least heading in a different direction.

Anyway, it looks like some outstanding issues may have started getting fixed in this thread, so here's hoping...