Dear XOOPS Developers,
there are some exciting news coming up, and we'll need your help!!! 1) http://dev.xoops.org
has been reinstalled, and before we go live with it, we need some of the XOOPS developers who have been using it before and have their modules there, to test it. If you would like to help us with the tests, it, please contact us 2)
Module developers are encouraged to use XOOPS SVN
for their code so that developers can share their ideas and help each other easily. It will also be a centralized place convenient for users to check module updates. A new subdirectory for XOOPS modules has been set up:http://xoops.svn.sourceforge.net/viewvc/xoops/XoopsModules/
Please read the Readme.txt file there, with some links to information about how to use SVN and TortoiseSVN.
Going forward, we want to leverage more the expertise of our community and focus on code reuse, so keeping the code together will help us to achieve that.3)
And now the most important thing: Starting a XOOPS Module Team
We need help with getting existing XOOPS modules up to speed for the upcoming releases 2.3 and 3.0
Therefore we're calling for all XOOPS Developers to join us in this effort. Some of the task that we have are: Phase 1:
* populate our module repository with all available XOOPS modules, and update them to their latest release
* select modules that should be part of our Module Packs (e.g. Basic, Commerce, Web, Community). The Basic Pack will be included in the main distribution of XOOPS, so the user will have first class "out of box" experience
* After the selection of modules, we will ensure that all modules of the individual packs are updated for PHP5, and there are on conflicts between them
* Also ensure that all of them are updated with latest Security patches Phase 2:
* Rewrite the XOOPS modules following XOOPS 3 structure, i.e. using XOOPS_PATH for code libraries (For sharing purposes, or for security consideration like D3 modules) and XOOPS_DATA_PATH for data, which are designed in XOOPS 3 but have been introduced into XOOPS 2.3. Meanwhile XOOPS_TRUST_PATH has been introduced into XOOPS 2.3 as alias for XOOPS_PATH to keep compatibility for a certain number of modules, e.g. D3 series. More information will follow...
* Extract common code and create a XOOPS Module Framework, so we can make the module development easier, and the modules themselves lighter.
We'll have a lot of exciting things coming up, but we need your help.
Please contact us if you would like to join the team and help. Remember, XOOPS is powered by YOU!!!!