52
Please, forget my suggestion number two.
I did not notice that the file xoops.js is not translated in the XOOPS spanish version. Sorry.
I did not notice that the file xoops.js is not translated in the XOOPS spanish version. Sorry.
.
54
Good job. Two suggestions:
1.- I believe that would be useful if the file to donwload is named with the release. In this case 2.0.1 (not 2.0)
2.- Is there any posibility that the messages in xoops.js can be in language files?. Better in orden to translations.
1.- I believe that would be useful if the file to donwload is named with the release. In this case 2.0.1 (not 2.0)
2.- Is there any posibility that the messages in xoops.js can be in language files?. Better in orden to translations.
59
No problem about get a copy.
I hope that Xoops-México soon can be on line again. It is a great XOOPS site.
I hope that Xoops-México soon can be on line again. It is a great XOOPS site.
60
Module Dev Team is out of xoops.org and it is a Community Team here; it was not allowed that Team worked here (as akitson said).
Since June a very a valuable group of xooppers had been working about module dev and module repository.
Never was said: equipment of the Community, has been decided that the Council will manage all the relative one to the project and that everything will be here.
However, now, after the work is done:
phppp wrote:
Quote:
But, why Module Dev Team is not in xoops.org
Quote:
If the Council want to assume all the jobs, tell us it clearly; is is not acceptable that when other people is doing the job and it was not allowed to do here, now they in addition are accused.
It is not the first time that this happen. The Comms Team worked too but now...The Doc Team started the jobs (in xoopswiki and xoopsinfo) but now the Council want take the control about documentation; results, no docs.
But the worse thing of everything is than valuable people finish tired which their work is not taken advantage of or are obstructed and they leave xoops. (the last Madfish).
Since June a very a valuable group of xooppers had been working about module dev and module repository.
Never was said: equipment of the Community, has been decided that the Council will manage all the relative one to the project and that everything will be here.
However, now, after the work is done:
phppp wrote:
Quote:
Some people would like to work on their own sites of which they have full control instead of on the xoops.org If you have interest to help the Project, either on a specific area, or to improve the management, please contact the Project Council at xoops-council@googlegroups.com or contact me at phppp@users.sourceforge.net
But, why Module Dev Team is not in xoops.org
Quote:
a request to be allocated a private discussion forum at xoops.org has been denied. This forum is to be used as a team thinking room to thrash out things before seeking public feedback. It will of course mean that such discussions become a matter of record accessible to XOOPS Council. The team has commenced this discussions using email.
If the Council want to assume all the jobs, tell us it clearly; is is not acceptable that when other people is doing the job and it was not allowed to do here, now they in addition are accused.
It is not the first time that this happen. The Comms Team worked too but now...The Doc Team started the jobs (in xoopswiki and xoopsinfo) but now the Council want take the control about documentation; results, no docs.
But the worse thing of everything is than valuable people finish tired which their work is not taken advantage of or are obstructed and they leave xoops. (the last Madfish).
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|