we should setup a jabber server for fosm to use it with kestrel, or rework kestrel to run over irc
People are going to want to host thier own osm layers using osm technology. they are going to want to have control over the license, the users the edits and the rendering of the data. they are going to want to import layers of data and maintain them separately. these layers will be shared under certain terms with other people, and edits to them can be suggested. They will want to be able to publish tiles or subsets of... more »
People will want to have a public domain OSM layer for only PD data, it will be separate from the CC-BY-SA layer etc and will have rules for when data is promoted (tainted) to a different license. We will want to possibly have versions of the objects if someone copies them into a different license and changes them to track branches of objects.
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 maintain ownership of their own data. They will not want to grant all rights for the future. we need a way to allow this in the framework.
People want tools for merging and comparing layers. they will want to see differences and approve them.
people will want to easily and graphically review the deletion history of the edits and rescue deleted data.
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.
we should raise money for hackathons and prizes for implementing these ideas that we find valuable.
* 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.
capture the data that will be deleted and make sure that the maps will be able to be used in the future.
Look into hosting tiles on archive.org