The title is missleading, this is day 2, but i will try to summarize day 1. At least the parts the others didn’t blog about yet.
But let me first talk about something else. Everybody should have noticed by now, the webworld sprint is hosted at linuxhotel.
It is an awesome hotel with pretty much anything a geek would like to have from a hotel. But to make the concept work you need to obey some basic rules. Like, there are free drinks 24/day. You just need to put the bottle back to where you got it from. Basic rules.
And that leads me to our webteam. Up to this point we were there to fix broken links, typos and maybe even be sort of creative to create a new and shiny look now and gain. Guess how hard that is with subdomains and code spread all over the place.
So we really are in need for some basic rules. We discussed it and came up with the following ones:
No new subdomains will be set up from now
Right now we have over 80 subdomains on more than 5 different servers. That is insane and doesn’t add ANY value. Having less separated systems and maybe a single point of entry makes it both easier to maintain and easier for users to find the information they need.
Note, there are of course exceptions. Like, reasonably big projects might still request one. A good example for that is the new Edu site. They have a very enthusiastic team behind their website and reasonable traffic. This subdomain is worth its setup.
Subdomains need at least one person of contact/maintainer
Let me repeat, we have over 80 subdomains, each having its own codebase, images, screenshots, content etc. A maintenance nightmare for our team, which basically consists of a handful of people. Also, those sites are hosted on svn/git. Another barrier for webdevelopers who are less likely to be used to SVN/Git than app developers, but would have loved to contribute.
So each app or project wishing to run its own subdomain should also provide the manpower to care for it and update it regularly. To give you an impression, yesterday we archived some sites which were not updated since over 5 years. Having listed “news” from 2005 gives not only a bad impression of the app but also of the whole KDE.
Subdomains should have a reasonable amount of traffic
If they really give some value to the users then it indeed makes sense to have a separated domain.
For our followers, we installed a webstats system now, and will now monitor how much traffic goes through our subdomains. But if noone is really interested in a certain subdomain, why should we even provide it?
But of course, in case we will remove a subdomain, we will not remove any data. There are options to move it back to the main page of kde as subdirectory, or just putting it onto userbase (which btw is way easier to get new contributors to than php files in svn).
These are the rules. It is not that much. But it makes our life easier.