Re: Whats going on with XOOPS
if your post is not pointing to my post above, ignore my following words, otherwise, listen to me:
1 no one asks you to install or use CBB. You have better place to complain your complaints.
Some of my comments were and some weren't. Nothing personal.
I'm not having a conversation with one person. That is what the quote tag is for and now I include one, to be direct on point.
Several times all of a sudden it is suggested that I use CBB as a solution to a new problem. Of course nobody forces me to use one thing or another, but I'll speak my mind none the less.
When I say I have no interest in CBB I mean that had no interest because the hype was about it being targeted at a community different than mine. To compare, gaming modules have the same lack of interest to me but it doesn't reflect any lack of respect I have or could have if I took the time to investigate the module. If I have a need I'll look further. Other things take up my time like anyone else.
So now I have a need to know more and I didn't like the whole complicated drama that surrounded it and other semi connected issues.
And that is what this whole thread is about isn't it.
Sorry, learnt from your post in the other topic and reply together there:
Nothing to be sorry about, I intended the two threads to merge together and assumed you would make that link.
All over the place. Everywhere I look it seems. By definition it can't be easily explained and solved at the same time.
A Catch-22 if you will..
I mentioned culture difference and cultural gap just let ppl be aware of it and do not ignore it.
"it won't happen with software", are you talking about culture difference? if yes, then you are wrong. Culture difference exists both in coding, multilanguage is an example, and, more important, in management.
Like I said, it is hard to miss. I'm aware of it. And I still disagree.
Code is code and if it covers all the bases, logical and cultural, then I can use it for my particular needs. The user decides how they want to exploit the code to create their content. The damn thing won't get written in the first place if there is a battle about the shape of the table the kings and prime ministers will sit at. That is the link I refer to about culture wars being a dead end. Winners and losers. Sucks to be the loser.
?So as a user I will likely have to frequently change gears and decide on allegiance and the politics of the application so I can maintain the content, style, and cultural identity I have? That should be irrelevant.
This isn't about icons and logos. It isn't fashion (reference to The Big Chill..). And I sure hope it isn't about a "management" style or any other cultural battle going on here and there. My decision to not buy cars or tires from one country or another is not the same issue at all.
So if anyone is totally confused by my rant don't fret. So am I.
I don't want to drag this out. So either this is a debate with a hope of a resolution that benefits the average user or it should be a private forum thread.
I won't be blown off because I wasn't asked to use a module that is for now a 3rd party module. But for sure there are better places to discuss some of these things. Like perhaps on the home site of the module in question for example.
And to circle back to the topic at hand. This affects some important decisions a user will be making. Maybe I too should look at Mambo or forks of parts or all of xoops. I wish I didn't. Mention of user group rights differences is a much bigger issue than the cultural battles behind the scenes. Mentioning that the concerns over specific issues like group rights will be covered in version xxx.xx is scary no matter what the intentions. My 486 CPU mainboard that was "Pentium Ready tm." years ago. It still is and is still a 486. But a darn nice doorstop it made....
So I don't know "What's going on with XOOPS". I hope it turns out ok..
oh, the thread has grown some more.
@DonXoop, can u explain me what means Chinese version
That is how the news was posted. Of course it shouldn't matter what language the author speaks. php is php.
why we dont switch to stable, and actively developed CBB, and to stay with dead and bugy NewBB 2.0.2
Because until all this nonsense and fighting started making sense I thought that newbb was an active project. And how is CBB already considered a project that will remain the active and true replacement? I'm not convinced yet and why should I be? I'm sure that a new XOOPS user is even more confused over what is the trusted module.
the xoops.org team don't have the time to go round every site and post modules to the repository here. at the end of the day it is entirely the module developers choice of where they wish to submit their modules
Thank you. That's another sore point. Few of the module listings here are maintained and kept up to date by the authors. The occasional announcement and listing might be made but rarely updated. Or the announcement might spark a firestorm. Or a host of other things could happen. Like this debate.