I have been waiting for some weeks now but since no one is making a clear statement to this and people are continuing to post about this issue in several threads and news comments so finally i want to say something about it before it might be to late.
For heavens sake please stop creating (or even thinking about) having subsites outside of *.xoops.org that are integral part of Xoops. Before someone is gonna shoot me:
I am not saying put them in recycle.bin.(more about that a little later)
There are several things to consider about splitting sites under different top level domains:
1. how that appears to first time visitors
If i went to a project and found that integral parts of that would be placed into the official domain and some on completely different ones i would already start to have first doubts. Because if a project is not able to maintain these things under one domain ... i´d guess i would not trust it as far as i can throw it. Since i can´t really throw a website ... thats not very far then. What signal does this send to new visitors?
2. Multisite login
User would need to register different accounts. Don´t say they only need one one the subsite that holds the forum because thats not true. Other subsites do have submission systems for files, news ...
3. Did i say ... just don´t do it already?
Lets have a look why we are currently facing this scenario ...
Due to things that happened in the past like (not timely updating, massive delays in creating the new sites, differences of opinions about what to do) we now have sites being created under different tlds with the purpose of having them under community control instead of project control.
Someone explain to me what community control means? Because when it comes down to it ONE person is in charge. And thats the guy or girl who owns the domain. Yes he might be good in involving people and get things down faster right now. But what if ...?
Let me draft a scenario:
- we create
http://www.xoopsforums.org registered by person x
- the council offcially announce that site as the official community forums of xoops.org and links to it
- everything works fine. Post numbers are growing because everyone who posted on x.o before does now post there
- 6 month later ... there is some disagrement in the group of people that runs the site (the community ... but still some people need to be in charge as you wont have 10.000 people with admin rights on that site, right?) Now the owner of the domain gets so mad about the disagreement that he shuts down the site. Forums would be gone and content would be gone.
Thats just one possibility and it alone justifies to have the sites from a server standpoint under the roof of x.o since that way the backups will be in posession of the main project/foundation/council and in any case will be available for one argument. The point is whatever site you create and belongs to the official sites it will never be a community site in the way that 10.000 people own it at the same time. One will be in charge when it comes down to it.
Now as i said before i don´t suggest to trash all the work that has already been done. I just urge you to take whats been done on those sites, make it the official subsites under the official domain subsites and since you worry about control
put whatever you think you might need to into the XOOPS manifesto which Marco is working on to ensure that the community does have a certain level of control about the sites when situated under the wings of *.xoops.org.
Find a way to implement the level of control you need for both sides but do not create lots of splitter sites, lots of different places to visit, different logins ...
Just don´t. And act now since the longer you wait the more difficult it will be to implement.
ps: i know some of you (you know who you are) might be dissapointed to see me posting this here. Sorry guys but i sincerely believe that using many different domains does more harm then good at the end. And this way at least i won´t regret for the next years to not have a least said something about it. If it will happen or not ...
Sorry, this signature is experiencing technical difficulties. We will return you to the sheduled signature as soon as possible ...