Re: [OSM-dev] Andy Allan joining web site maintainers
On 22 June 2017 at 21:15, Tom Hughes wrote: > I'm pleased to be able to invite you all to join me in welcoming Andy Allan > as the new co-maintainer on the code base for the OpenStreetMap web site. > > Going forward we intend to look to add additional maintainers to further > diversify and spread the load, so we will be actively looking for candidates > among those working on the code base. > > Please continue to open issues and pull requests on GitHub as before. Thanks Tom. My intentions for the next few months are to continue to do whatever I can to encourage new contributors. I've done a lot of refactoring recently which will help whoever tries to make code changes, but there's other things I think I can do too. So it will likely be a combination of: * My own refactoring priorities, which will pay off for developers in the long term but aren't very visible to most people. * Working through the PR and issue backlogs, to try and help some straightforward things get "over the line" - hopefully motivating for developers. * Work on a few end-user facing tasks, so that we're making visible progress. Thanks, Andy ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Andy Allan joining web site maintainers
Hi, On 10.07.2017 11:14, Andy Allan wrote: > My intentions for the next few months are to continue to > do whatever I can to encourage new contributors. I think it would be helpful for new contributors if the following two points could be explained: * What kinds of changes to the API are acceptable while still being "API 0.6"? Is anything that adds new API calls automatically on hold until we do "0.7", or should we just refrain from breaking existing API calls? One reason I'm asking this is that there's a bunch of things that have an API call but are not accessible through the web site (e.g. "show me a specific version of this object" - website has just full history or latest), and vice versa (web site can show all changesets by a given user, but no API call exists for that). It could be a low-hanging fruit to create feature parity between website and API at least in some areas. Maybe this is even on some mental roadmap somewhere - I heard people talking about making the web site actually *use* API calls, rather than accessing the database directly. * What is the relationship between "cgimap" and the web site, and in how far are contributions that touch an area handled by "cgimap" required to cover both the C++ and the Rails implementation? One reason why this is of interest to me is that I'm still very much interested in being able to access deleted objects through the API and through the web site. I've made a few half-baked attemtps at implementing that in the past (https://github.com/woodpeck/openstreetmap-cgimap/tree/deleted_call, https://github.com/woodpeck/openstreetmap-website/tree/browse-deleted-objects) and would appreciate guidance of how to "do this right", if at all possible within the constraints of "0.6". Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Andy Allan joining web site maintainers
sent from a phone > On 10. Jul 2017, at 11:48, Frederik Ramm wrote: > > It could be a low-hanging fruit > to create feature parity between website and API at least in some areas. +1, few people know you can request specific versions like the previous one, with big objects often running in timeout for the full history it would be convenient to offer a link to the previous version rather than the full history or after a timeout occurred. Cheers, Martin ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Andy Allan joining web site maintainers
On 10 July 2017 at 11:14, Andy Allan wrote: > Thanks Tom. My intentions for the next few months are to continue to > do whatever I can to encourage new contributors. I've done a lot of > refactoring recently which will help whoever tries to make code > changes, but there's other things I think I can do too. Currently, the openstreetmap-website is both responsible for the openstreetmap.org web application, and for the API. How hard would it be to separate these two functions, perhaps even into two projects? Would there be any advantages in doing so? Intuitively both functions seem to be separate projects. I could imagine having two smaller applications might make maintenance easier. It would also mean we could, for example phase Ruby out for the app but not for the api or vice versa. Lastly, making the website make only use of well-defined api endpoints instead of interface with the database directly might also makes things clearer. Have there been any thoughts in this direction? -- Matthijs ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Andy Allan joining web site maintainers
On 10/07/17 13:25, Matthijs Melissen wrote: On 10 July 2017 at 11:14, Andy Allan wrote: Thanks Tom. My intentions for the next few months are to continue to do whatever I can to encourage new contributors. I've done a lot of refactoring recently which will help whoever tries to make code changes, but there's other things I think I can do too. Currently, the openstreetmap-website is both responsible for the openstreetmap.org web application, and for the API. How hard would it be to separate these two functions, perhaps even into two projects? That's exactly what we're working on with cgimap. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev