I used to create government procurements, big messy ones where sales guys would hit the prime minister's office to protest and get fired fifteen minutes after a debriefing when they lost. When dealing with potential problems from egos I always found it very helpful to build a list of requirements that were linked to business requirements first.
At the moment I couldn't do that for OSM because I'm not certain what we are trying to do. Are we just having a social gathering on a Sunday afternoon for a walk or cycle with our GPS devices or are we building maps that will be useful to people? Which is most important? Because it affects what business we are in and I suspect we are in two main camps trying to do different things and until we can agree what we are trying to do trying to make decisions about the license issue is irrelevant. Cheerio John I don't know > how to have constructive discussions on the topic though - most seem > to devolve fairly rapidly. > > Steve > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk >
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
