<div id="photodiv">
<img id="photoimg" src="<{$xoops_url}>/themes/gumamela/images/005.jpg?v=0" />
The goal of the XOOPS Foundation is to provide the basic means for XOOPS to grow. It is the Foundation’s belief that XOOPS is made up out of three separate but entwined units: the XOOPS Project, where the core of the XOOPS system is defined and developed, the XOOPS Communities, where support is being provided for the user base, and the XOOPS Foundation, who provides support and continuity for both the project and the community. We call this the XOOPS Trinity, in which each unit focuses its (limited) resources on specific areas of expertise. Together, they all work and collaborate to make XOOPS better. They do this as equal partners, in a professional, mature and open source spirit. That is the core of the vision the XOOPS Foundation has for XOOPS.
In reply to this article, here is the XOOPS Foundation official response.
The Foundation has already initiated the discussions about this with the Chairman of the XOOPS Council concerning their exact requirements and is confident we will find a solution that is mutually beneficial shortly.
Selected domains are available for both Community or Project usage, upon suitable request, and depending upon availability.
As for the XOOPS.org domain name, it is well documented that this domain is still owned by M. Onokazu. He was contacted at many times in the past by the Foundation and by the XOOPS Council. No one never received any answers. Currently, the XOOPS.org domain is pointing on the current XOOPS.org server’s DNS which are controlled by EPC USA. When XOOPS.org is completely moved on the new server, we will be able to change the information on EPC USA DNS.
The XOOPS Council claims that JMorris acted without authorization. JMorris was able to do so with the permissions he had on XOOPS.org for the last 3 years, permissions which were never removed by the XOOPS Council.
The XOOPS Foundation would like to state that it supports both the XOOPS Project and the XOOPS Communities, without leading them left or right. Therefore, the Foundation takes no position in the standpoint between phppp and JMorris. The Foundation supports the simple fact that this issue needs to be resolved soon as in a mature and decent manner, in order to have XOOPS move on and be able to grow again.
JMorris informed the XOOPS Foundation as well as the XOOPS Council about his action and documented his reasons. He then put back the original permissions on XOOPS.org and send all access info to the Foundation.
In the mean time, phppp and the XOOPS Council contacted Herko Commans, chairman of the XOOPS Foundation, on a personal email address and not via the XoopsFoundation.org site or via the Foundation’s public email (board at xoopsfoundation dot org). Unfortunately those messages were not seen directly by Herko, which explains the delay it took for the Foundation to react.
On October 8th, The Foundation sent the XOOPS.org access information to XOOPS Project Council with the assurance expressed by JMorris that he did not alter the site in any way nor do any damage what so ever.
While The Foundation does not approve of JMorris actions on XOOPS.org, it does not approve either of the public news posted by the XOOPS Council about terminating the account of JMorris. This should not have been handled publicly. The Foundation respectfully requests that this news should be removed immediately.
In summary, as of 9th October, the XOOPS Council has full administrative permissions on the XOOPS.org site.
We truly hope the XOOPS Project and the XOOPS Community can move forward and get back on the track XOOPS once was : the best open source CMS alive! The XOOPS Foundation will be happy to help in anyway it can to support the project and the community.
The XOOPS Foundation
http://xoopsfoundation.org