Andrew Turner kirjoitti:
The link you gave illustrates to me the current frustration of finding
appropriate tools. It's just a listing of projects - where the project
Yeah, probably I'm acting from the same frustration. I know how some
things are done but I'm often left wondering if those things are very
common,
and if not, then what is. You know, I'm mostly sitting in my room in
a university.
Why don't we treat it like an actual 'catalogue' - or use cases like
Rich pointed out.
Use cases, problems, decision trees, they all sound good to me. Something
that's intuitive and attractive to describe and what would be valuable for
OSGeo cookbook writers or something.
also - I'm not aware of what the "book" is? Is it the "Free GIS Book"
mentioned on the wiki?
This is a result of one brainstorming meeting in IRC of the edu committee
of OSGeo. We came up with three(!) books to write, they're mentioned
on the committee's page in that wiki. This was the first to get at least
some
content. The old Free GIS Book, which was at eogeo wiki is being
or will be moved to somewhere else.
>So you want to try and convince all the projects out there to move
>their repositories, forums, documentation, mailing lists, trackers,
>homepages, et al. to one place? Each language, as we started this
>discussion with, already has a fairly well defined place for modules
>with supporting tools, infrastructure, and community.
On the programming languages page I guess I'd hope to see short
introductory,
texts and then links. Also, for example: if you're working in this
subject then
this language has this to offer.
Thanks,
Ari
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
