i can't comment on the roadmap and features, altho there's a lot of them.

regarding WOX newsletters, we are working on that, and i posted earlier regarding this.. i'm not going to repeat the whole post here as it isn't necessary.. but i'm drafting a wox newsletter this weekend, and then it will be discussed and reviewed by the new news/liasons team etc.. the plan is to have a WOX newsletter out ASAP hopefully within the next week, 2 weeks at most.. but definitely soon. we're just deciding exactly what to put in it at the moment as there's a hell of a lot of news to sort through.. i hope this is good news for some of you..

seems that some communication or management problems DO exist.

The core dev team feels alone while module developers feel not well informed with XOOPS dev/management roadmap.
If XOOPS has a manager or a management team, could it be improved?

After I started this thread, Mith had a chat with me.
Answering his question about why I created a folk "CBB", I told him "CBB" was not intended to be a fork, "C" means "Chinese" and CBB was dedicated to Chinese users (I also explained the reason of dedicating to Chinese users).
More important, the CBB uses the same db prefix/structure, the same dirname with NewBB 2.02 and the CBB could be rolled back at any proper time.
As Mith mentioned above, we had kind of 'agreement' on management of dev.xoops.org and expected some actual action during that weekend, meanwhile he or Herko would contact Marko.
I know ppl are all very busy. However, it is really a pity that Marko made his "final" decision before ppl got time to deal with such issues.


Believe or not, there was a call for dev team at jp.xoops (I do not understand Japanese language) on the same day with this thread.
As for JP "fork" (no matter what you call it), it is not a good sign to XOOPS community.
Skalpa does not think it a culture difference but I do think cultural gap plays a key role here -- perhaps this is another example of culture difference as I am an asian. I remember that Herko and me discussed a bit about cultural gap (mainly on aisan and western) in XOOPS commmunity in the last year.


To me, OK and Skalpa are the two labels of XOOPS.
I do not expect anything but the XOOPS dev core works as a core.

I'm one of the people calling CBB a fork. I didn't call it that at first. I saw the announcement and since it was a Chinese version of newbb I had no interest. My users speak English, French and Spanish. They might speak 100 other languages but on my site I support 3.

I assumed there were character issues that prompted a CBB. Cultural issues escape my logical thinking but if options can be turned on and off then fine and dandy.

When I ask a question about a bug that appeared when 2.0.10 came out I start seeing answers that point to CBB as a solution. Now the other threads about politics and devel issues has finally connected the dots for me. So now I call CBB a fork. Plain and simple. I won't even comment about another fork being mentioned.

From a user's point of view I shouldn't care or even know about so called cultural issues with the devel. From the point of view of a user that tries to help other users, those issues matter a little bit more. From a user that helps other users yet probably has the most unanswered questions himself, it starts to matter a lot. For a module that is likely the most critical outside of the core itself, what happens with devel matters a great deal.

The future of newbb is of great importance to me. However at this stage there isn't a chance in hell that I'm jumping ship to install CBB to fix problems with newbb. I'd rather jump overboard and start over with another CMS. No offence but things are much too volatile to change over to CBB no matter how good the first "fork" is doing so far.

BTW, this is the kind of thread that is best done in a private forum. It scares and confuses some people and is pushing other questions off the page to never be answered.

chao pescaos.

@DonXoop,
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.
2 When I talked about culture difference, I was meaning the core team not CBB. Why the CBB came out, since you have no interest, neither me on this topic with you.

Sorry, learnt from your post in the other topic and reply together there:
Quote:
where is "culture wars"? 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.

@DonXoop, can u explain me what means Chinese version (I was the first one who told that CBB is a fork, few minutes after the news for CBB 1.0 release), after some tests, I replace all my XOOPS sites from NewBB 2.02 to CBB 1.12, no matter is the module is created by Chinese, Koreans, Japanese or whatever Asian, African ppl, the module is a good addition to XOOPS community. With this strange words - "Created for Chinese community" - both of you phppp, donXoop, Mith u scare some ppl, yesterday one of Bulgarian xoopers, ask me for CBB - "How CBB can be converted to work for Bulgarian", and this stupid question comes from there.

This night (searching for words for the japanese fork of XOOPS or something) I found very interesting and good modules (as description, not tested yet), why this modules are not provided from Modules resporsitory ? Or they are created for Japs only ?

The same is the situation with Brasilian mods, Spanish, Russians, all of this sites, have created some times very interesting and usefull mods, but they are not listed here.

Why? Most of the modules described in Modules resporsitory are French and English (authors)...

Or maybe u have to create a block on the top of xoops.org, "here u can find only our (core dev team) modules, for 3rd party modules for xoops, use google"

CBB works fine for me, both in Windows-1251 and Unicode, now I can say that my first post was a mistake, (and I promise never will say it against for other module, before the test). CBB have great improvments and additions to NewBB 2.0.2, why we dont switch to stable, and actively developed CBB, and to stay with dead and bugy NewBB 2.0.2 ?

Quote:

i think i can at least answer this question apropriately but it is just my opinion.

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, yes it would be nice to see them all in 1 place or at least something to point the users to those modules existence (maybe that can be worked on at least) but i see 1 reason the local sites may choose to just host them on their own sites is that if they submit the modules here, then most likely if anyone has issues with the module or wants to know things, then it would be highly probable that the developers may not visit this site as often as users may wish, so that could create issues where support is not given in a timely manner and then you get support given in different places and on different sites scattered about the place.. this is not good practice as a whole.

the wf-projects team prefer support issues and requests etc to be made on their website, not because they don't like to come here but mainly because that's the site where they are most active and your request is most likely to be seen and addressed there.

invisionboard mod is preferred to be kept on bbpixel as then things get kept together. it is probably the same with the rest of the local sites..

communication between sites is going to be stepped up and bringing the point about modules been hosted on other sites is something that i think has been overlooked when discussing recently, now the attention has been brought to that, maybe that can also be addressed in the communications/liasons team aswell. i hope i gave this opinion satisfactory and i hope i have at least given a valid opinion..

@m0nty, interesting, but

Quote:

WF-Projects are listed here, in the resporistory, and if someone have troubles with one of their mods, he can click and will be redirected to their homesite.

The same is the situation with BBPixel forums.

What about Russian Top Sites, or Korean Blues Board ?
I cant agree with this local support sites to host the files localy, in this case, first no one (due the nature of XOOPS), will not know which version is last, 2nd who (web administrator) with XOOPS will browse every morning all support site with Google translators, to check what's new and what no.

How Gentoo's community organize all dev teams in one place, there is no support sites, yeah some local sites to promote Gentoo, to give simple answers, but all main discussions for and about Gentoo and his sub projects, comes on the main site. No matter with nationality they are, u have to learn from them, this is the one of the best communities in the net, allways with "smiles" no matter what some angry (l)users says, they are smiley, in Gentoo forums cant see fork from fork.

In your way, XOOPS have to separated to everyone nation, and when u or Solo for example, let's take his multiMenu, current 1.7 but tomorrow will be 1.8. And I as non-official (who gives this title official) support for Bulgarian XOOPERS, have to:
1. to check is the new release is a release or just a note to upcoming release
2. if is release, to go to wolfpackclan site, get it, install it, translate it, and put it localy, only for Bulgarian users and so for all other modules.

If u understand Community created - "Powered by You (XOOPS Slogan)" - You are in great mistake.

Quote:
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.

Quote:
Nothing to be sorry about, I intended the two threads to merge together and assumed you would make that link.

Quote: 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..

Quote:
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.
Quote:
That is how the news was posted. Of course it shouldn't matter what language the author speaks. php is php.

Quote:
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.

Quote:
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.

the module repository needs attention, no doubt there i think some organisation will be implemented as soon as the communications team is established. i think tho a good idea would be to have all modules submitted in the repository either locally or by remote url to the modules download page on the hosted site. the hosted site of the module oughta keep the link the same for updated module so that the repository here doesn't become out of date and point to an older module or dead module.. this can be achieved by the local site hosting, if they upload the new module to the same place. and then possibly archive the previous versions either on the sourceforge repository or in a seperate archive.. it can be done if everyone works that way.

Quote:

I agree that need some organisation !

Quote:

Yes, if xoopsers know what's going on!...

Cheers