Vaughan, my point was:

You and others left XOOPS and have created a competing fork. I don't have any problems with that and I wish you all the best. It's unfortunate for XOOPS, but things happen, so it's OK, XOOPS will survive.

But why you, Steve, David, and others are behaving like the boyfriend who is breaking up with his girlfriend because he found another one, but for whatever reason still wants to have sex with her, I don't get it!

You guys have your fork (you new girlfriend), then make a clean cut and MOVE ON. Resign from XOOPSInfo and XOOPSAddons, and focus on your fork.

There are people who re-marry but are still coming back to their ex-partners and want to have sex, or they are still stalking them. Why? Who knows. But every shrink will tell you that this is a sick behavior. Police issues a restraining order against such individuals.

Unfortunately, you, Steve, David and others exhibit the same behavior. It's a new year, opportunity for a new start, new beginning, so make a clean cut with XOOPS and move on to you new fork. You guys made the decision, then finally accept it. Resign from XOOPSAddons and XOOPSwiki and XOOPSdocs, give it back to the XOOPS community, and MOVE ON!!!! Don't hold those Website hostage, especially since they are paid by the XOOPS Community!

BTW, speaking of XOOPSInfo - James Morris started with the silly idea to create XOOPSInfo. As you can see from this thread, I was totally against it, as it creates fragmentation of the community. Steve was also a big supporter of it and was beating me up. Then together with David you went on to create XOOPSAddons and XOOPSwiki and XOOPSdocs, claiming that this is also needed.

Now, if you believe that this is right, WHY don't you apply the same model at ImpressCMS? Why are you creating EXACTLY what I was advocating and was beaten up by JMorris and others?

Quote:

But if you believe that the "One stop shopping" model is right (since you're implementing it at ImpressCMS), why are you insisting that we need XOOPSInfo, XOOPSAddons and XOOPSwiki and XOOPSdocs?

Double standard? Hypocracy?

Or because you are still trying to feel like being in control of at least part of XOOPS, the same way as some ex-husbands are trying to control their ex-wifes via missed child support, etc.? Again, this is a sick and destructive behavior, guys. Please, move on!

How about this mamba? Maybe they are doing things the way it should have been (granted it took them a while to figure it out like I said it should have been three years ago) and there seems to be nothing happening over here right now that would suggest different. XOOPS will lose a lot of people, in fact it has lost a lot of people.

Whether you care to admit it or not, DJ is doing more harm than good here at Xoops, he back stabbed people with all this server crap, he had no intention in working with anyone but himself. How many people have to stand up and say we CANNOT WORK with DJ because he either doesn't want to, doesn't listen, say one thing and does another?

So he got another server, big deal. He states he is willing to work with the community? Strange I don't see one real change that anyone has asked for. How many developers have to come and go at XOOPS before you all realize there is a fundamental problem here?

yes they have created a new fork, good luck to them, I suggest you take note and see what they're doing and how it should be done. I suspect you will see a larger amount of people take notice in future.

Oh, btw. I have been looking at the so called changes by DJ, and I have to say i am not impressed. The security fixes recently are more of a cover up than anything else and do not address the issues correctly.

Quote:

No, they are not doing the way it should be done. YOU did it the right way, when you went off to work on your fork. You said you're leaving, and then you went on to work on it. And I respect you for it. You didn't try (at least to my knowledge), to hijack any servers or to hold hostage any XOOPS Website. You made a clean cut and moved on and I commend you for that. Then you decided to come back, and that's great! You update your modules, and that's awesome. We might have a different opinion about few things, but I still respect you for HOW you did it.

People leave Open Source projects for different reasons and that's OK. But the way they should do is similar to you - make a clean cut and move on. There is no need to fight or have some hostile power struggles by holding hostage XOOPS Website paid by the XOOPS Community.

Quote:

Is the Plan 2008 addressing at least some of the issues?

Quote:
Can you help with suggesting a better solution? DJ can't do everything himself, so I'm sure he'll appreciate feedback and help.

who hijacked servers? considering the foundation owned the servers, they couldn't hijack their own server now could they.


what was the 1st thing DJ did when he was given all the access info (which he did not require root access)? the 1st thing he did even though he was asked not to, was to change the password and refuse to inform the foundation. he then altered config settings on the server which caused more issues later on. let me remind you the foundation servers were thoroughly tested by many users and even digg users. but after DJ's messing with the server, there were more problems than a little. he even changed the servers contact email address to his own instead of the foundations.. basicly HE was locking the foundation out.

but enough of that..

why the hell should we resign from xoopsinfo, xoopsaddons etc? come on give me 1 #OOPS# good reason.

Quote:

give it back to the community? when was it the communities in the 1st place? they were built for the community. but we did not and have not taken it from the community. they are not being held hostage.. lmao and as for paid for by the community.. get frakin real.. the server was paid for by the foundation, but the sites were not paid for not 1 little bit, no money was passed between anybody, everyone was working on them voluntarily.. so don't try and say that the community bought & paid for those sites.. that is definitely not True

yes they are offline at moment, but thank your brazilian hacker friend for that. but no you won't blame him because you just want to blame us for everything.

and we have moved on, but we also still support XOOPS software. BUT you are telling us in fact demanding that we STOP supporting XOOPS software. so just go back to sleep will you.

and they were needed because there was no module repository at the time in xoops. so it was built to give the community a repository, and it was built by many people not just us 3. because there was a need.

as for fragmentation, we did not do that, DJ did that and others by ignoring, disrespecting & back stabbing people. but anyway enough is enough.

is it NOT allowed for anyone to support more than 1 project? get real.

as for:
Quote:

one stop? all those my friend are seperate sites, and all will be clearly linked, with navigation, matching themes etc, and sub domain urls.. which is what we suggested before. except you wouldn't listen.. a url is a url it can be easily changed..

but even xoops.org is seperated with sourceforge & dev.xoops.org etc etc.. they are seperate sites or is that acceptable because well you're just nitpicking.

oh and btw.. WE ARE STILL SUPPORTING XOOPS SOFTWARE just not here.. xoopsaddons is for XOOPS modules.

it will be a seperate repository for impress modules at addons.impresscms.org.. ie addons.impresscms.org & xoopsaddons.org will NOT be the same site, they are seperate sites. get that? u probably don't.. lol



and as for what Catz says, he is correct.. the security fixes aren't fixes they are just covering it.

since when is htmlspecialchars used for sanitizing? sanitizing means to clean the $string text or whatever you call it.. it does not mean Prevent all html from being parsed which is what htmlspecialchars is used for.

Prevention is not sanitizing!!!

as for providing you with how it should be done.. why should we (according to you, we are not allowed to support or help people who use XOOPS).. that's what you are saying anyway..

but if you want a tip.. remove the htmlspecialchars from places where it is incorrectly used to (not sanitize but prevent) and properly Sanitise the $string 1st instead.. then it wouldn't need the htmlspecialchars (especially in function insertbreak() ) lol

and if you want us to stop coming here and replying to your stupid comments and insinuations then stop frakin making those stupid insinuations and accusations in the 1st place, then there'd be no need for anyone to respond to it would there..

so we move on, you should move on too.

XOOPS Addons & XOOPSWiki will re-open once the issues are fixed. if you don't like it, so be it.. to be honest I don't care what you think. just like you don't really care what I think either.. so i guess we're even there.