XOOPS moving forward - XOOPS - XOOPS News - XOOPS Web Application System

Re: XOOPS moving forward

kris_fr Published 08/13/2011 6:29 Theme Designer Joined 12/31/2005 Comments 1009

Very bad news for the community and the future of Xoops.
I see that we will still keep an old kernel with patches from all over.

Where is the new engine X3 ?

Re: XOOPS moving forward

webmystar Published 08/13/2011 6:45 Friend of XOOPS Joined 06/23/2008 Comments 415

Thanks for the Info Mamba. What is with this Article?
https://xoops.org/modules/news/article.php?storyid=6035

Sorry, you don't have the permission to access this area.

Re: XOOPS moving forward

Mamba Published 08/13/2011 6:48 Moderator Joined 04/23/2004 Comments 11409

Kris, the answers are in this thread

Re: XOOPS moving forward

mrphilong Published 08/13/2011 8:41 Quite a regular Joined 07/14/2006 Comments 351

BAD NEWS! Such a Waste!

Re: XOOPS moving forward

trabis Published 08/13/2011 9:32 Core Developer Joined 09/01/2006 Comments 2269

It will be hard to do any bug fix or development without having admin permissions on sourceforge.
Dj resigned from Core Dev team but kept his admin account in sourceforge, added other members and removed me, Rune and Mamba.

Does it make any sense?

Re: XOOPS moving forward

Mamba Published 08/13/2011 10:10 Moderator Joined 04/23/2004 Comments 11409

Quote:

Dj resigned from Core Dev team but kept his admin account in sourceforge, added other members and removed me, Rune and Mamba.

To see the timeline of events, please see this post

Re: XOOPS moving forward

incama2 Published 08/13/2011 10:22 Just popping in Joined 08/13/2011 Comments 2

I congratulate the community with it's dictator Mamba and I am happy to see we finally can bury Xoops as an CMS. Hopefully the forums and comments will be overrunned by spam messages so at least there will be something usefull to read on x.org.

Have fun.

ps. Btw, what will happen to all of those who have inversted in Xoops for the past years, mmm.

Re: XOOPS moving forward

Mamba Published 08/13/2011 10:36 Moderator Joined 04/23/2004 Comments 11409

Quote:

I am happy to see we finally can bury Xoops as an CMS

yes, it takes certain kind of individual to be happy when seeing other project's temporary problems, and anxious to see it buried. Thank you for showing us your true colors

Quote:

Btw, what will happen to all of those who have inversted in Xoops for the past years, mmm.

Don't worry - XOOPS will take care of our current users. Having these three developers on board, I am confident that we'll move forward faster and better than ever before, because they are very good team players. Looking at the results of what they did with EXM, XOOPS 2.4.x, and XOOPS 2.5.x individually, and having them now working together, the future looks bright to me...

Let's wait and see...

Re: XOOPS moving forward

incama2 Published 08/13/2011 10:55 Just popping in Joined 08/13/2011 Comments 2

Sure Mamba,.whatever you say. And if you're saying it often enough, you start believing it yourself.

Re: XOOPS moving forward

kerkyra Published 08/13/2011 12:11 Just can't stay away Joined 02/14/2005 Comments 553

Quote:

I firmly believe that the worst is behind us, and with Trabis, ForMuss, BitC3R0 we'll have finally a great team environment, where contributions from all members will be valued and appreciated.

Viva XOOPS!

i cant see how repeatedly resignations can do any good to xoops! I have nothing against nobody in here, but cant you see that the founder and one of the lead core developers of xoops have resigned in the past few years?

And they were 'the worst' that 'is now behind us'???

Doesnt that mean anything to you? I would agree with 'Viva Xoops' if we could all be working together as a team.

That would be indeed a victory for xoops.

Under those circumstances all i can say is, pitty...

PS: why did onokazu resigned after all?? Just out of curiosity.

Re: XOOPS moving forward

Mamba Published 08/13/2011 12:30 Moderator Joined 04/23/2004 Comments 11409

Quote:

And they were 'the worst' that 'is now behind us'???

I meant the recent fights, the hijacking of the servers and XOOPS Site, and the unknown about XE. There is this saying: "The worst is not knowing", and that's what I was referring to.

Now the we know that DJ wanted to keep it as his personal project, we can focus on X2, and move on, making sure that our users know that the project is moving forward. We all wanted to have XE as XOOPS project, incl. me. But DJ decided otherwise, and I respect it, even if I am disappointed with the way he has resigned - the hijacking of the XOOPS servers and Website was wrong and illegal!

Re: XOOPS moving forward

nmshah Published 08/13/2011 13:30 Just can't stay away Joined 07/02/2007 Comments 556

Mamba,

DJ has resigned, stop panting DJ as wrong in every post that you write using a play of words.

Also you had known all along that XE is registered by DJ under his own name (kindly currect me if I am wrong) and still you decided to not inform the community about it until your fallout with DJ. You are as much responsible for the current situation as is DJ.

Re: XOOPS moving forward

Peekay Published 08/13/2011 13:43 XOOPS is my life! Joined 11/20/2004 Comments 2335

It seems like a lot of the arguments stem from an over-enthusiasm to make XE the new Xoops. I think that's understandable as it is a ground-up development with much to offer, but there are many thousands of Xoops 2.0 users who need support and bugfixing of the current application.

Like most end users, I would welcome a better Xoops, but the core devs have a responsibility to address current issues in addition to undertaking development work. I think the council were correct in raising concerns about this and in trying to establish how XE was going to fit into the scheme of things.

I agree with xgarb (yet again!) in hoping that PHPPP and his team continue with XE albeit on another domain. However I still believe that the projects need to be kept separate until XE proves itself and PHPPP can persuade everyone it deserves to be the new Xoops.

I understand Kris_fr that this must be frustrating, as you know better than most the code benefits that XE would bring, but I second the appeal to current developers to stick with Xoops 2.0 and support Trabis, ForMuss and BitC3R0 in bringing it up to speed.

Re: XOOPS moving forward

redheadedrod Published 08/13/2011 13:55 Home away from home Joined 02/26/2008 Comments 1296

Quote:

Also you had known all along that XE is registered by DJ under his own name (kindly currect me if I am wrong) and still you decided to not inform the community about it until your fallout with DJ. You are as much responsible for the current situation as is DJ.

Regardless of Mambas intentions or actions nothing he did directly harmed the xoops community such as what DJ has done. Dj has acted childishly and highly unprofessional. These actions should warn away any one wishing to have any sort of business dealings with him in the future. It is fine to disagree but you can not go to the extent that he did and expect to have positive repercussions.

As a programmer and knowing other programmers, I know that a large portion of programmers do not think like the rest of us do. They generally have issues with social interaction and understanding they are not the center of the universe. It is very unfortunate that by DJ leaving and leaving in this manner he has essentially hijacked the code for xoops for the past 2+ years. HE was the one that requested no further development to be done on the X2 branch because XE was going to be so much better and why waste time coding for X2. Now we can see this was a bad decision back then and hopefully development will continue on X2 while the community looks again at the future of Xoops and starts designing an idea for the true next X3.

I do hope that this will help form a better system to prevent this sort of thing from happening again. A community project like Xoops should not put so much of its future into one person for ANY reason.

Re: XOOPS moving forward

kerkyra Published 08/13/2011 14:16 Just can't stay away Joined 02/14/2005 Comments 553

I agree with redheadedrod and peekay has a crucial point.

If a new version of xoops should come out, it should be backwards compatible with the 2.5 branch and if not, offer a safe and tested environment to users for upgrading without any complications with their modules etc.

So, i believe 2.5 should be bug free, and all crucial/official modules upgraded, and as bug-free as possible they could be also in order to move to a new branch.

People stuck with 2.5 (for any reason) without the possibility to upgrade smoothly and without any possible serious problems are actually left behind to solve their problems by theirselves. :/

Re: XOOPS moving forward

chco2 Published 08/13/2011 15:13 Module Developer Joined 03/05/2004 Comments 374

Well said redheadedrod!

Re: XOOPS moving forward

bjuti Published 08/13/2011 15:19 Just can't stay away Joined 01/07/2009 Comments 871

My proposal to the community: Let them (council, management etc) one week to sort things out. If they're not, we all should leave, coz this is all stupid. A lot of vanity, power issue, childish arguments like 'my daddy is stronger than yours'.

I made a lot of websites on Xoops. I can't see the reason why I couldn't do it on other CMSes. I like Xoops a lot, but this is so wrong. I have no nervs to read all of this and waiting for 'the right thing'.

You could make a spaceship, but without passingers it's useless. Xoops is dead without users, and I can't see that userbase is growing.

Goodluck, see you in one week.

Re: XOOPS moving forward

vamptrix Published 08/13/2011 17:29 Theme Designer Joined 05/03/2008 Comments 424

I agree with redheadedrod. Don't give up on XOOPS. If DJ wants to go on with XE, that's his choice. It's also his choice to leave.

I don't judge anyone here, we just have to do what is best for XOOPS. DJ did some things that are way beyond the acceptable.

My questions are: where is development going on and how can I help? I'd gladly help, even with my limited knowledge of PHP (but I've gotten quite good with the CodeIgniter framework).

My laptop is still broken, but I'm glad to help anyone if there is anything going on and I'll support the XOOPS community and project. Our users shouldn't be the one that suffers from this!

XOOPS needs to continue, with or without XE. I'll gladly help write X3 if that's going to happen.

Instead of arguing right now we need to unite and make sure that XOOPS continues. We need to do best for the project; and if you want to go with DJ, you can do that, but please think of the users of your software, modules.

Developing something isn't the hardest part. That's honor goes to maintaining and supporting what you made.

We need to unite and think what XOOPS needs. The current branch of XOOPS is buggy and that should be fixed, that's our stable branch. Maybe we should think of a new development system too (with that I mean the way we release versions. Maybe we could use SCRUM (http://en.wikipedia.org/wiki/Scrum_%28development%29). So we could put out more new features and more frequent releases, but avoid waiting for new features.
It's better to release a few new features every release than to wait a few months for a single release with a lot of new features.

But I'm going off topic here.

Don't judge, think what is best for the project.

Re: XOOPS moving forward

amaranth Published 08/16/2011 6:27 Just popping in Joined 12/21/2008 Comments 9

Wow, it's been quite a ride watching this project change since 2006. Cheers to a fresh start, Mamba and good luck with the new team!

Re: XOOPS moving forward

Defkon1 Published 08/16/2011 13:05 Not too shy to talk Joined 01/27/2005 Comments 151

as Italian Support site webmaster I'm worried about these days' events and i think that all this fight is really childish, unprofessional and a bit untransparent.

imho we can't waste all work done on XoopsEngine; it's fundamental to stabilize 2.5.x branch, but it's equally important to plan the future with a radically new engine like XE should be.
in italy this is called "short blanket" (coperta corta) because of little resources availability, but we can't continue to "drag" an old kernel along the years.

my proposal is simple:
- stop fights between mamba and phppp, xoops community doesn't deserve it
- council should approve the new dev team
- the new dev team should work on 2.5.x/2.6.x branch
- phppp and his team should be reinstate in the position of XE dev team
- enlarge the number of xoops council members (to prevent lack of activity)
- replace the inactive members of council and of all teams (core, doc, themes,...)

Stats
Goal:	$100.00
Due Date:	Nov 30
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

XOOPS: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Re: XOOPS moving forward

Login

Search

Recent Comments

Re: New Admin Theme for XOOPS (Beta)

Sanford Pharmacy: Exceptional Pharmacy Services Tailored to You

Re: New Admin Theme for XOOPS (Beta)

Re: XOOPS 2.5.12 Beta-2 available for Testing

Re: XOOPS 2.5.12 Beta-2 available for Testing

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}

Archives

News archives