The answer would likely depend on the changes you're making. If you are
adding new functionality that is generalizable across deployments we would
love to get patches from your team merged into commcare-hq. If you are
building something one-off to meet the needs of this one application we
might push back on getting it rolled into the codebase and would probably
recommend that you fork commcare hq and stand up your own server. Feel
free to start a thread on commcare-developers@googlegroups.com if you'd
like to have a conversation about which case this falls into.
cheers,
Cory
···
On Fri, Apr 5, 2013 at 8:43 AM, Ian Lawrence wrote: