[josm-dev] JOSM mini-roadmap anyone?

[Frederik Ramm]

Hi,

   I've been very busy for a while and am just beginning to see the
light in terms of free time I will spend on improving JOSM. (Thanks to
Gabriel who has obviously fixed lots of bugs and responded to
enhancement requests!) I see that there's a lot of discussion about
the UI on the Wiki, as well as a number of bugs in Trac (and some
patches there as well) that I'll have to look into.

If anyone has put a patch in Trac that has been ignored for no
apparent reason, I will probably catch up with it during the next week
or so but it doesn't hurt to point me at it directly.

Is there anything consensus-like about the most important things that
should be done next?

My personal impression is that we'll first have to address the
"accidental moving" problem (what would be the best way you reckon?),
then fix the "cascading relations upload" bug which was revealed
during OpenGeoDB import, and then get the damn Mappaint mode to work
faster, it seems incredibly slow once you load a sizeable area. I
think there was a tuning patch for the wireframe display which I
haven't applied to the mappaint side of things so that could help
already but I guess there's a lot more to be done.

Has anyone already done work in these areas, and/or does anyone see
different priorities?

I'd also like to hear from those subscribed here if there's anything I
can do to get you to contribute to JOSM, not only by developing cool
new stuff but also by tending to Trac every now and then and fixing
bugs that may make some folks out there unhappy. It seems that this
job, at the moment, rests on Gabriel's and my shoulders (with me not
having done a lot recently...), and I would really like to have a core
team of about five developers who somewhat feel responsible for JOSM;
I'd consider that a prerequisite to someday releasing JOSM into the
OSM SVN.
 
Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00.09' E008°23.33'