Oky, you will go to see here soon:

xoopers.org
support.xoopers.org
themes.xoopers.org
addons.xoopers.org
hacks.xoopers.org
core.xoopers.org
docs.xoopers.org
community.xoopers.org

simple thus

Features.

- One unique only base of registered users.
- To each different sub-site one theme.
- To sub-site with groups permissions differents.
- All idea already they had been sent very the much time here.

Moment Zen (The Idiot)

Now we have a specialist in security that is 24 hours per day working to discover the imperfections in our system and it it does not charge nothing for this work all. If this idiot and imbécil to hacker to leave me in peace, this will be made to benefit to all the community. XOOPS Cube care, one day it could be irritated when to discover that it will not have to be able to manage the system and will be able to try to also destroy this excellent work.

my patience arrived here at the end.

in portuguese.

Agora nós temos um especialista em seguran?a que fica 24 horas por dia trabalhando para descobrir as falhas em nosso sistema e ele n?o cobra nada por todo este trabalho. Se este idiota e imbécil hacker me deixar em paz, isto será feito para beneficiar toda a comunidade. Cuidado XoopsCube, um dia ele poderá ficar irritado quando descobrir que ele n?o terá poderes para administrar o sistema e poderá tentar destruir também este ótimo trabalho.

Minha paciência chegou agora no fim.

Moment Zen (phppp)

Thanks for your reply and help.

Quote:

I will add to my previously mentioned GI Joe issue:

Debaser 0.92 Security Patch Released

This is a serious security issue. It is headline news on xoopsinfo.com. Why isn't it here on Xoops.org?

SailJapan,

My query related ONLY to the support forms database that are now in use on a daily basis to research previous problems and fixes and module/theme releases.

Duplicating Peekay's concern.

Thanks in advance
...darcy

Quote:

One of the things XOOPSinfo has striven for is to be a portal for ALL XOOPS-related information. The communication team has also chosen to utilize the site, so when information comes out - it can be posted there without delay.

The points about module v. core v. whatever are well-taken. A central place for all information is needed while preserving the workspace for the specialized groups. Again, a site dedicated to information makes a lot of sense. Points about attracting new users are also being heard. New users don't care about module development or the architecture of the core and developers don't want to wade through all the questions beginners have. Having areas dedicated for those groups makes a lot of sense.

So - why don't articles like that get posted at XOOPS.org? The members of the news/communication team that had access to post/approve/highlight news articles got locked out. They still have that ability at XOOPSinfo. It's that simple.

Quote:

Why the article author publish on xoopsinfo.com instead of xoops.org?

Why some people strive to build a new portal instead of contributing to xoops.org?

I understand that everyone has his own desired way of contributing, so just go ahead with the way you feel comfortable.

Hi DJ

It is the same situation with documentation. We can't post documents on docs.xoops.org because there is nobody to send them to, and we ourselves have no access. We have several times and for a long time now offered to take on this work ourselves and to join teams if necessary, but this proposal has met silence. I cannot understand why.

Thanks.

Look, its just way too hard to contribute to this project. I just don't understand why it must be made so difficult for people to collaborate.

Anyway, I've had enough. I give up.

Hi MadFish, i understand you.

Sharing your frustations

Quote:
Another great loss.
Please, the discussions are fine: but we need facts, organization and who want work (in any matter) can do it.
This site need urgently a full reform. The forums could be here, in xoopsinfo.com in forum.xoops.org etc, but It will be a mess that (as another threads as this) this discussión do not produces facts.
What about prommotion?
What about docs?.
What about comms with local support sites?
What about module repository?.
What about theme repository?.
Look at Joomla.org or drupal.org: not as xoopers, as newbies in CMS. No comments.
Since June there is no advances. Only losts.

With all due respect, but this is due to you and the management style that has allowed fiasco this happen. You seem to have poured everything into the management of the code and forgotten what really matters here at Xoops.org, the community. You seemed to have left this part to people other than yourself and not given them the keys to do the job. DJ, you are a fine coder but your management skills are a lot to be desired. (Or maybe you are just to busy to give a #OOPS# about this side of the project?).

It is about time you took this community by the balls and dragged it into shape, as the way I see it, there is nothing but confusion, splits, misconceptions and people with their own agenda's here at Xoops. You have created this mess and are unwilling to do what is required to clean it up.

If you did what was needed there wouldn't be a need for xoopsinfo.com and their forking of XOOPS (They might as well take the code as well, as they seemed to have taken everything else) and all that work could have been done under and managed here at Xoops.org, but as I said you would prefer to ignore this side of Xoops.

I don't care what anyone says, but project should be under and managed under Xoops.org and until you actually see that this project will go further down the drain that you seem to be making wider and wider each day.

People flocked to help you from day one and you in your wisdom decided to do it your way and create more fiction and problems with your style of management. You really need to do something rather than just the coding if you want this project to be a success.

The problem is that Xoopsinfo is trying to slit this community apart and they #OOPS# well know it. They are exploiting the situation that you have created and rather than you doing something about it, you seem to endorse it by not talking the correct action.

As I have said before, people do not want to have to go to 10 different sites just to get modules, themes, info and support for XOOPS when it should be under the same roof by all the same people working together as one community. If anything it is the information there at Xoopsinfo that should be moved over to Xoops.org and not the other way around. (But we all know that won’t happen, as that would mean people giving up control of that domain).

Either do something about it or give people the tools to do the job properly or give the keys to someone else. You are the leader of this project, lead it (even if you have to drag it by the scruff of the neck to get it where you want it to go) with a sense of purpose or all the coding you are doing will be for nothing and it will not save Xoops.

Wake up DJ and see what is happening here and do something about it.