To give you some heads-up, I'm migrating web hosts, and so there will be some downtime for the to-do list as it stands on the wiki (if it's still in use - I haven't been paying much attention to it recently). I'm migrating to a Virtual Private Server, and I'm expecting downtimes of about three hours. Absolute worst-case scenario is about two weeks of downtime, though I have a plan that *should* circumvent that. I am thinking about not installing the wiki on the VPS system, since it seems to do a good job of collecting spam. I will, however, have a tool called GForge(1) on the site. I will be using it to track my own projects, though kernel janitors are perfectly welcome to use it if you want. It has a built-in wiki, though it also has a tracking system (for bug reports and to-do list items), which I would think would make it a better tool for the job. Unfortunately, I haven't been able to do hardly any kernel hacking, so I'm not very qualified at all to make that kind of a decision. If you're really adverse to the idea of using something other than MediaWiki I can try to install it on the new VPS system, that's no problem either. It's just a bit harder for me, since this is the first time I've really had to configure all this software from the ground up. I'm expecting to start the migration within two to three weeks, and I will keep backups of everything from the old site - just in case. Aside from the inconvenience, the good news is that the new site will not be anywhere near as slow as the current one. The shared server I'm on is incredibly overloaded, and because of policy issues it's impossible to make it better. The VPS host is also connected to Internap, which - in my experience - is a really fast network, so the site should be even more responsive. Thanks for your patience, and have a nice day! -- Registered Linux Addict #431495 http://profile.xfire.com/mrstalinman | John 3:16! http://www.fsdev.net/ | http://lordsauron.wordpress.com/ -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
