14
Quote:
Northern wrote:
• As for modules, they need to have somthing on them and place in a spot that states they are for version 1 or 2
if they are php4 or php5, sql4 sql5 ready, same with the core files. as for the cerrent modules, almost half the modules we have dont work any more due to version change or not php5 ready. for this we need some one that is good in code, and XOOPS core files, and fix the modules, sence thats is one of the larges complaints....
See 2nd bullet point of my Mission Statement. This is exactly what I am taling about. But if you read the entire point it said "(need to establish consensus on what this entails)". So it still needs to be worked out. I suggest something like Bronze, Silver, Gold and Platinum certified modules, themes, etc. An example would be Bronze is PHP4, MySQL 4, Silver could be PHP5, MySQL5, Gold could be XOOPS 2.0.* and 2.* compatible and Platinum wouled be something above that! Agree?
Quote:
Northern wrote:
•• As for offical modules and modules added to the "Out of the box" xoops, this was done in the pre 2.0.11 . Its unsure why they desided to remove them, but they did..
Not sure I understand this one, but it seems related to the statement above ("Official" modules?).
Quote:
Northern wrote:
••• Put them back in there, update them, you can still offer the packets of "theme" based modules
Just give a new user somthing to tinker with while they start to understand what they have.
Same as "Certified" modules as stated above
Quote:
Northern wrote:
• Theme, if we can get some theme designers to take the cerrent themes we do have, and convert them to 2.0.14+
we will have less of a headack, but as said in the modules section, these to should be placed in a spot that states they are for version 1 or 2.
Again, "Certified" components.
Quote:
Northern wrote:
• Generate revenue
Im sure if just these ( above ) are met, many users will chip in some $ to have themes and modules updated and converted to work on the cerrent, and future version of xoops. granted many versions and XOOPS based modules are built and made free of charge, and those that arnt have been donated to and charged for.
why cant xoops? chage for the use of the name.. or to be a partner, "offical" does mean alot....
If the core team cam out with a killer looking userpanel as a update im sure no one will mine if that hade to pay for it.... say 20 bux....
"Killer userpanel"? Not sure what you are looking for, but this is an idea addressed by my 5th bullet point in the my Mission Statement. However $20 aint gonna cut it. We need to get full time programmers, theme writers, etc driving this thing.
How about a Corporate Sponsorship? X Window System (X, or X11) was Open Source but someone came along and Created Motif (a toolkit to work with X) and it was a great success. Why cant we do the same here?[/quote]
Quote:
Northern wrote:
• The cerrent XOOPS •
now thats a isue in its self....
most of use ( if you have been here around 2005-2006 ) or have asked about the avatars....found out that XOOPS has a bad db..
Well fix it. dont sit on it.
so what, the xoops_config is all messed up..
What?
Quote:
Northern wrote:
( Im cerrently doing this with HelpXoops.info )
its about 85-90% done, i just need to deal with the blocks... )
So yet another website for yet another branch of Xoops. Great work.
Quote:
Northern wrote:
these are a few that came to mine.
Thanks for your ideas, however, kc0maz asked for a Vision Mission Statement. Not a long drawn out post about stuff that's broken.
Quote:
kc0maz wrote:
What is your vision of the XOOPS product?
What is your vision of the XOOPS project?
