On Wed, Mar 9, 2011 at 6:25 AM, Andy Allan gravityst...@gmail.com wrote:
Happy to answer any questions, but remember things are neither set in
stone nor necessarily fully thought-through!
Hi Andy,
First - thanks for taking the time to write up this documentation.
My question is about the
On Mon, Feb 28, 2011 at 4:31 AM, Richard Fairhurst rich...@systemed.net wrote:
In the near future it looks likely that P2 will become the default editor on
osm.org.Consequently we need to move from the 'rapid development' stage to
the 'mature code' stage, and enforce a bit more rigour in the
On Tue, Mar 8, 2011 at 8:12 PM, Serge Wroclawski emac...@gmail.com wrote:
For potatch2, especially, I foresee developers customising it for
various use cases (like I'm doing), and git is very useful here
because it allows someone to customize their instance while keeping up
to date with the
Steve Bennett wrote:
Can you elaborate a bit on who we is, in this context? And what kind
of process of review and integration of new features do you envisage?
I guess I'm wondering how long we can expect to wait between
developing a new feature and seeing its deployment.
We're having a
In the near future it looks likely that P2 will become the default
editor on osm.org.Consequently we need to move from the 'rapid
development' stage to the 'mature code' stage, and enforce a bit more
rigour in the codebase - with great power comes great responsibility
and all that. :)
In
On Mon, Feb 28, 2011 at 8:31 PM, Richard Fairhurst rich...@systemed.net wrote:
r25368 should be the base for the functionality freeze. That's certainly not
to say that we abandon the stuff that's been done since then, but we will
separate it into the essentials (a and b above) and the
