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.
the changesets basic data could be broadcast in an irc channel with a special syntax to describe what area is affected, what the contents are, what conflicts occur and a link to the data. this could be subscribed by simple filtering on the channel.
you could post the basic data about an osm changeset using a short bounding box the basic data in it and a link to the data in twitter and then aggregate the data. this could use a geohash or something similar to easily select the area.
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.
we should raise money for hackathons and prizes for implementing these ideas that we find valuable.
Look into hosting tiles on archive.org
we want to subscribe to peoples edits via georss and have them rendered on top of other maps.
we want the Ability to use GIT or version control to manage small sections of the map.