we should setup a jabber server for fosm to use it with kestrel, or rework kestrel to run over irc
* Internet Servers
* Data Storage
for the hosting of the central coordination system. For the ability to manage a part of the map and include mode. We dont need to be able to store all layers and all tiles on the server, but need the capacity to process a part of it and distribute the load.
look into rendering and hosting tiles on the wikipedia toolserver
Build a local api proxy that you can tell it to publish your changesets to multiple server, to your blog and to sync and resolve changes and conflicts
we want real time rendering. we want to be able to have changes rendered immediately.
The OSM planet file is sorted by ID, this makes processing it cumbersom because you need to load in all the ids to know what id is in what geographic location. it would be better to sort the file by geographic location. my idea was to use a geohash as a sorting mechanism. or to use some block system. in any case some sorting would be great.
Sometimes there are changesets that are really strange. It would be cool if we could create Bugtracker tickets from Changeset IDs. This would help to get in contact with the Changeset user and help to revert or fix strange/wrong/vandalism changesets.
we need to have a scheduling system for coordinating rendering of tiles. Some People will want to render some parts immediately to fix problems and see the results asap. others will have computers to donate off hours. Others will have old computers to use. others will rent cloud computers for dedicated rendering. Some will want to render only their own town. all these need to be considered.
People will want to import georss feeds into the system and also produce edits as georss.
People will want to post changesets and blogposts with annotations and pictures. they will want to render tiles and show what they have edited. They will want to store the OSM change data in the blogpost and not have to store it in some central server.