(sorry, I can’t speak rusian, but maybe somebody likes to translate the very essential stuff?)
the past weeks I joined the Navit project (an open source offline navigation system), so now I need your input:
I like to collect what is called** “user stories”**, so we can get detailed visions of a working functionality for Navit. So on what device should it run, how is the scenario (e.g. driving by car to aunt Josy, you just don’t know the target area in detail, …). It’s basically an open minded brainstorming, that just ignores the current problems/limtations of the tool (as we try to build a roadmap of what needs to become integrated). So we like to gather similarities, that could be reflected in a changed architecture etc.
I started an quick example on the “Installation” scenario and how I wish it should work in future:
And here somebody on a quiet complex scenario (so called Use case)
Of course you can even write about situations, where Navit currently fails, or aspects, that are pretty good solved at commercial Navis.
Like at OSMBugs, you should take care, that you explain the essential backgrounds, as the reader has no idea/orientation what and why you like/dislike a certain behaviour. But hey, if you write to much, nobody else likes to read your story anymore :/…
So personal hints/explainations would be best in a seperate block at the end.
But in general this is NOT about, what currently doens’t work right with Navit (therefore we have a bugtracker and not what the current development lacks (the navit team iscurrently not satisfied with that, too e.g. focus on usability).
Maybe it’s not nessesary to point to a specific implementation, to solve a problem (e.g. the compass should look like this and that), but the dev team should understand the backgrounds and the why (e.g. the compass should become easier to understand, to get simplier recognized during a car journey).
I would be happy, if we could show the navit team, that we are interested in their project and that’s not about sueing somebody (again and again), what just don’t wirk, but to find together the things people wish and what might be possible. With this ideas, we can find specific improvements, order them by effort/interests/… and out them on a roadmap.
But please, don’t shout it from the rooftops. Till now, only a few people from the navit core dev team gave feedback to this approach and such suggestions to substantial aspects by externals will take it’s time. So it wouldn’t be wise, if 500 mappers would send out wishlists for the new year, or who try to explain the navit devs, how they would solve all the problems “pretty easily”
But it would be nice if 5…10 of you would write some stories in the wiki during holidays, just look at the existing articles
As you might know, I especially take care on promoting OSM and dealing with community aspects (here in Germany). After a lot of talks during the past months, my impression solidified, that only a well running offline navigation app would help, to attract new users for OSM from the mainstream (as GIS, IT and science people seem all to know about OSM).
As I worked on the software catalogue in our wiki, I decedided form me, to join the navit community and to help to make this becoming true. Here this doesn’t mean coding/forking/… but to encourage the dev team to reflect the current situation and to get an idea of what Navit should be like and to find ways how to solve the current problems. I did some brainstorming here: