Quote:
khuhner wrote:
So Northern, what ideas, thoughts, suggestions do you have to move this forward?
Personaly, and from what ive seen, my oppinion and may other's oppinions arent worth the broadwidth we use..
but i will always be here, and so i will reply. lol
Quote:
khuhner wrote:
Mission Statement
• Foster a centralized unified community for end users, developers (core, module, theme, etc.), and documentation specialists
• Certify modules as “Xoops Ready” (need to establish consensus on what this entails) to ensure successful implementation
• Distribute XOOPS as a package of XOOPS core, modules, themes that are maintained by XOOPS on Xoops.org.
• Generate revenue streams for development, enhancements, and upgrades.
• Create and maintain new product offerings that are easily deployed and flexible by the entire XOOPS user base.
Respectfully submitted,
Kurt
• 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....
•• 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..
••• 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.
• 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.
• 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....
• 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..
make a new "updated" XOOPS site on server of off, subdomain or what ever...
tranfer files images,modules,uploads, and any other "needed items", for the data base... tranfer everything but the 3 config files... youll have to set up the site like a new site, but all users are there, messages,folders, files you just have to place the block in the right places and deal with the meta, name,and slogan related things...
( Im cerrently doing this with HelpXoops.info )
its about 85-90% done, i just need to deal with the blocks... )
yah well 2.0.16 has isues,
well so does the rest, but if you expect use to use it, you should to. " teach what you preach"
as stated in a earlier post ( same topic )
make some sub domain, label them, use one XOOPS or multi...
and link the db with a bridge..
these are a few that came to mine.
Quote:
kc0maz wrote:
What is your vision of the XOOPS product?
What is your vision of the XOOPS project?
These shouldnt have to be changed from the original plains...
