[OSM-dev] OSM Wishlist

[Andy Allan]

On 12 October 2012 00:58, Tom MacWright <tom at macwright.org> wrote:
> Hey all (or, well, those subscribed to dev@ - my flamewar shields are at 50%
> so I'm not risking an email to talk),

Bear in mind that technical (generally software) stuff is often better
on dev@ anyway - and there's lots of developers on this list who
aren't subscribed to the general flamewar^Wtalk@ list.

> The three of these were closed by Tom Hughes, which is fine - they might be
> all bad ideas, and if we're treating the issue tracker as "Stuff we all
> agree is definitely good", then they don't belong there: they're relatively
> undiscussed ideas, since I had just posted them.

We have rails-dev@ was the place to discuss matters relating to the
api/website, and here for matters with a wider impact. Does discussing
new ideas on github bring advantages over mailing lists that I'm
missing? It's not something that I'm used to.

> What do you want to see happen with OSM's software this year? What are the
> tasks which everyone agrees on, but nobody has had the time to tackle?

Ah, good stuff.

There's a lot of stuff on Potlatch2 that I'd like to see, but that I
don't have time to work on. There's a junction editor that needs
writing, an in-editor tutorial framework that needs finishing off, and
a lot of half-done stuff in translations, UI and unit testing. I
haven't seen anything specifically rulling it out, but would I be
right in saying that mapbox don't have plans to contribute to P2?

Beyond that, I'd like to see the issues around the
deleted-item-map-call sorted out, and OWL (or equivalent) integrated
into the rails port to power the history tab. As for all-new things,
I'd like to explore how to integrate all the various QA feeds into a
combined overview, rather than having to hunt around different sites.

Cheers,
Andy