OpenStreetMap Foundation - User contributions [en]

Operations Working Group

Matt — Sat, 19 May 2018 09:48:36 GMT

Matt: Update membership list.

__NOTOC__
<div style="margin:2px 0;border:1px solid #9B9;background:#EFE;color:#000;padding:2px .5em;text-align:center">
[[File:OWG_potential_logo_2017.svg|thumb|left]] 
The '''Operations Working group''' is responsible for proposing the budget for, and running of the servers owned by the OpenStreetMap Foundation. 

 '''Status: Active'''

Twitter: [https://twitter.com/OSM_Tech @OSM_Tech] 

<big>'''https://operations.osmfoundation.org'''</big> 
</div>

==Get in touch ==

{| class="wikitable"
! style="color:black; colspan="2"| Contact us
|-
! style="color:black; background: white"| [mailto:operations@osmfoundation.org operations@osmfoundation.org]
| Get in touch with the whole team for general discussion.
|-
|-
|}

==Our Policies ==
* [https://operations.osmfoundation.org/policies/ Policies]

== What we do ==
The key priority for this group is ensuring the operation and smooth running of the XML editing API and data distribution services (planet files and diff updates). Secondary priorities include the operation of the other OSMF servers.

The main task of the Operations Working Group is the forecasting of demand and the purchasing of hardware required to meet the priorities.

Other tasks include
* Creating policies for OSMF services, such as the tile usage policy or API usage policy
* The organisation and budgeting for hosting OSMF servers

It does not concern itself with
* Authoring software to run on the services. This is left to the development community
* Day-to-day running of the servers. This is the remit of the sys admins group

== Who we are ==

We're an anarcho-syndicalist commune. We take it in turns to act as a sort of executive officer for the week.

{| class="wikitable"
!width=220px style="text-align: middle; background: white;"| Members 
!width=220px style="text-align: middle; background: light-grey;"| Former Members 
|-
| width=220px style="text-align: middle; background: white;"|
* Tom Hughes
* Grant Slater
* Jon Burgess
* Andy Allan
* Emilie Laffray
|
* Sarah Hoffmann
* Matt Amos
* Brian DeRocher
|-
|}

== Minutes ==
* [https://operations.osmfoundation.org/reports/ Current Reports]
* [https://operations.osmfoundation.org/meetings/Minutes 2010-2016]

Some minuted meetings have taken place although most decision and discussion takes place in an unscheduled manner via normal community channels.

== Historic ==
* Formerly known as the "Technical Working Group"
* [https://wiki.osmfoundation.org/wiki/File:OWG_Plan_2013.pdf 2013 Plan]

Licence and Legal FAQ/Why would I want my contributions to be public domain

Matt — Wed, 13 Apr 2016 11:49:41 GMT

Matt: Fixed typo, removal -> remove, thanks to Blair Alper

Translations: (unofficial)
* [[OSM:DE:Editing Why would I want my contributions to be public domain|Deutsch: Sollte ich all meine Daten als Gemeinfreiheit (Public Domain) freigeben?]]

----



OpenStreetMap's license is a free share-alike license. I.e. you are more or less allowed to do what ever you want with OpenStreetMap's data under the one condition that you agree that any modifications or additions again are under the same free license.

In the eyes of many people, this share-alike clause - which limits your freedom in certain ways - is necessary for a greater good, which is generally seen as spreading the freedom and openness of data. The plan is to force people (rather than just encourage them) to contribute improvements back so that anyone can benefit from them just like they benefited from OpenStreetMap.

Other people however think that this forced share-alike property is an undesirable reduction of freedom, and would thus rather see their contributions under a full free for all, or [http://en.wikipedia.org/wiki/Public_domain Public Domain] license. The question of share-alike vs public domain is mostly a question of personal taste and often very controversially debated. For every "reason for PD" that you find listed below, there is also a "reason against PD", and it is unlikely that both sides will ever agree. Thus OpenStreetMap gives its users a choice as to express their personal preference on this topic.

If you declare your contributions to be in the Public Domain, '''you are thereby making a statement only. You will not actually be changing the license or what people can do with your data''', because database law still overrides the protection of individual items. People will have to adhere to ODbL when they want to use OSM, even if a majority of contributions should be declared PD. But nonetheless such statements can be powerful. How many people choose the PD option will influence the way we think about OSM licensing in the future. Nothing is ever black and white; even ODbL can be enforced strictly or handled leniently. By selecting the PD option, you basically say: Hey guys, do this ODbL thing if you must but don't go over board with it, I consider my contributions PD and would rather get mapping than think about what is allowed and what not.

Public Domain is the idea that a work can exist without anyone claiming any rights to it. In some jurisdictions you can create something and place it in the Public Domain explicitly; in other jurisdictions your right as an author cannot be signed away, so in these jurisdictions Public Domain is understood as a shorthand for "Yes I may be the author of that but you just do whatever you please with it." (In lawyer's terms this sounds something like "I grant anyone a permanent and irrevocable license to use my work for any purpose, without any conditions, unless such conditions are required by law.").

'''Declaring your contributions to be public domain is up to your ''free choice''. Not selecting this option ''will not prevent your account creation'' or affect your contributions to OSM negatively in any other way.'''

Reasons why [http://wiki.openstreetmap.org/wiki/Category:Users_whose_contributions_are_in_the_public_domain some people] consider Public Domain superior to more restrictive forms of licensing include:

=== Reasons for PD ===

* PD is simple for users and providers of data. Users need not be concerned with legal details, and providers need not spend time to find out whether a certain use case is acceptable. ODbL is the best license that a number of very good people could come up with, but it still is a complex piece of work to laymen and professionals alike; there are a number of use cases where it is very hard to determine from the license alone whether they are allowed or not. Thus, additional documentation has already been provided on subtle questions like "what is a database", "what is a substantial extract" and so on, and this will have to be maintained and refined in the future.

* PD is fair. Data under a PD license is usable by everyone all over the planet in exactly the same fashion, whereas the extent to which ODbL or any other known share-alike license affects the data (or the strength of the protection offered by ODbL) varies from jurisdiction to jurisdiction. Under ODbL, certain use cases of our data are possible in some countries of the world and not possible in others. The likelyhood of someone "getting away" with an ODbL violation in the USA is different from the likelyhood of getting away with the same violation in Europe because the legal concepts ODbL has to employ are different in these jurisdictions.

* Releasing your data PD means that you opt out of the "intellectual property game". Rather than fighting owners and purveyours of proprietary data (like map data providers, record labels, or film studios) on their own terms by using copyright or database right to force people to adhere to your conditions, someone who goes PD asserts, by example, that knowledge and data should be free and ''not'' encumbered by EULAs and the like, no matter how well-intended these rules are.

* PD would remove a significant barrier to direct contribution to OSM by US Government organizations, like the US Geological Survey and the US Census. Right now, OSM can import data produced by these organizations and occasionally get a little guidance. These organizations are hesitant to invest significant effort in developing OSM because they can't use the data themselves. From the perspective of the US Government, OSM is another place where data goes to die. PD would remove the restrictions, allowing US Government organizations to explore direct data interoperability with OSM rather than attempting to duplicate efforts.

Engineering Working Group

Matt — Mon, 02 Mar 2015 17:33:27 GMT

Matt: /* 2015 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2015 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-03-02|2nd March 2015]] || - || ''upcoming''
|-
| [[Working_Group_Minutes/EWG_2015-02-23|23rd February 2015]] || mobile, authpocalypse || ''draft''
|-
| [[Working_Group_Minutes/EWG_2015-02-09|9th February 2015]] || mobile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-02-02|2nd February 2015]] || mobile dev, RPi2 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-26|26th January 2015]] || routing, alternative login || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-19|19th January 2015]] || hack weekend ideas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-12|12th January 2015]] || rails_port, hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || - || {{Accepted}}
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || osm2pgsql, budget || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Working Group Minutes/EWG 2015-02-23

Matt — Mon, 02 Mar 2015 17:32:49 GMT

Matt — Mon, 09 Feb 2015 15:50:40 GMT

Matt: /* 2015 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2015 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-02-09|9th February 2015]] || - || ''upcoming''
|-
| [[Working_Group_Minutes/EWG_2015-02-02|2nd February 2015]] || mobile dev, RPi2 || ''draft''
|-
| [[Working_Group_Minutes/EWG_2015-01-26|26th January 2015]] || routing, alternative login || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-19|19th January 2015]] || hack weekend ideas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-12|12th January 2015]] || rails_port, hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || - || {{Accepted}}
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || osm2pgsql, budget || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Working Group Minutes/EWG 2015-02-02

Matt — Mon, 09 Feb 2015 15:50:00 GMT

Matt: Created page with "== Attendees == {| class="wikitable" style="font-size:0.9em;" |- ! IRC nick ! Real name |- | pnorman || Paul Norman |- | RichardF || Richard Fairhurst |- | RobJN || Rob Nicke..."

== Attendees ==

{| class="wikitable" style="font-size:0.9em;"
|-
! IRC nick
! Real name
|-
| pnorman || Paul Norman
|-
| RichardF || Richard Fairhurst
|-
| RobJN || Rob Nickerson
|-
| tmcw || Tom MacWright
|-
| zere || Matt Amos
|-
|}

== Summary ==

* Mobile development
** RobJN has written up some notes on a potential mobile app to make it easier for people to collect survey data [[File:PhotosAndNotes.pdf]].
** RichardF had a similar-sounding idea 2 weeks ago, and has also written up some notes [http://www.systemed.net/osm/osm_mobile.pdf].
** One thread of the discussion was about getting "official" status for the app(s), so the developer would appear as "OpenStreetMap".
** ''ACTION'': RobJN to take something forward to the board broaching the topic of having an official class of apps.
** ''ACTION'': zere to start organising a hack weekend with mobile dev as the theme, provisionally for April.
** tmcw pointed out [https://www.mapbox.com/blog/coffeedex/ coffeedex] as an example of special-purpose editors.
* Raspberry Pi
** RobJN noted that the new RPi2 has been released, and wonders whether anyone has any ideas for how it could be used for something OSM-y.

== IRC Log ==

<pre class="forcewrap">
17:33:12 <zere> minutes of the last meeting: http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2015-01-26 - please let me know if anything needs changing.
17:33:38 <zere> on the agenda today is: mobile dev.
17:33:51 <zere> #topic mobile dev
17:34:35 <RichardF> good evening
17:34:49 <RobJN> evening
17:35:57 <pnorman> Could someone introduce the topic?
17:36:16 <zere> pnorman: please wait, organising stuff
17:36:21 <pnorman> k
17:37:05 <RobJN> So I guess the question is about next steps on app ideas (both Richard's and if there is interest in it, mine)
17:37:35 <zere> RobJN (Rob Nickerson i assume?) has written up some notes on a potential mobile app to make it easier for people to collect survey data. he's agreed (i hope) that we can share it and i've uploaded it here: http://wiki.osmfoundation.org/wiki/File:PhotosAndNotes.pdf
17:38:23 <zere> RichardF had a similar-sounding idea 2 weeks ago, and has also written up some notes: http://www.systemed.net/osm/osm_mobile.pdf
17:38:37 <zere> (i think in response to RobJN's notes)
17:39:50 <zere> so... now we have some documents setting out the idea - the questions are: 1) are they potentially the same app? 2) how do we help kick off development of it/them?
17:39:50 <RobJN> Yeah happy for you to share that :-)
17:41:21 <zere> i don't know if RobJN and RichardF would agree with me here, but based on the two documents, i'd say RichardF's is considerably more complex as it involves editing in addition to data collection.
17:41:41 <RichardF> yep, I think that's fair.
17:41:57 <RobJN> Re 1) - Possibly, yes, it just depends on whether you want a really simple app with no editing capabilities, plus a simple app with basic editing.
17:42:10 <zere> but does that mean a P2-style "expert mode" in the same app, or does the inclusion of such a mode spoil the UX of either or both?
17:42:33 <pnorman> I'd say RichardF's is a more complex app but RobJN's involves more backend changes
17:42:39 <RichardF> I'd envisage Rob's idea as something that could potentially be developed by the community in a relatively short space of time, particularly if you start off Android-only (there are more likely to be interested Android developers in and around the existing community).
17:42:58 <RobJN> I think that given that the basic bits need doing, perhaps we start with this, release something, and then start adding features until we get to Richard's idea
17:43:13 <RichardF> that's then a potential stepping stone to a consumer-grade app along the lines which I've mocked up, and where we'd need to look crossplatform (i.e. iOS too)
17:43:34 <RobJN> We end up with two apps but this is fine (we have multiple editors catering for different needs)
17:43:49 <RichardF> and a lot of the backend work for Rob's app would be invaluable for a consumer app, particularly the pic/audio storage
17:44:18 <RobJN> Exactly :-)
17:45:37 <RobJN> Although I think we should aim to do iOS and Android from the off. Not sure what developers think of this. I've played with Appery.io before which can spit out both Android and iOS versions. Seemed quite good but I strated to get stuck with the more technical bits.
17:46:09 <RichardF> yeah - the problem with using a crossplatform solution like that is that you're less likely to find devs who are experienced in it
17:46:41 <zere> the mobile devs that i know all pour scorn on "cross platform", but i don't know how much of that is bigotry and how much is really due to benefits of being platform-specific.
17:46:46 <RichardF> I suspect we have <reasonable number> of Android devs in and around the community, of iOS devs, and <almost zero> of any crossplatform solution
17:47:07 <RichardF> I mean, I could write something in Flash that uses Adobe's AIR crossplatform compilation stuff, but it might not be very popular ;)
17:48:08 <zere> from the start, though, i'd like to kill the idea of "backend changes". we shouldn't be putting anything extra into rails_port for this. if we need to write new, independent services; okay. but at a time when we're trying to break up rails_port to make it more maintainable, i don't want anyone to get the idea that we'll be adding to it.
17:48:37 <RichardF> zere: +1
17:49:12 <RobJN> One of the things I would like is to open an OpenStreetMap portal on the main app stores (to go hand in hand with openstreetmap.org). Do you think we can have some apps as android only or should we be aiming for cross-platform?
17:49:45 <RichardF> depends on the audience, really. existing mappers are likely to skew towards Android.
17:49:52 <RichardF> (I say that as an iPhone owner :) )
17:50:17 <zere> having never released a mobile app, i have no idea what a portal in an app store would mean. any sort of "official" presence is likely to require bureaucratic overhead.
17:50:39 <RobJN> So we would need some way of storing collected photos online. The natural thing is to have this and Notes together, but if it's easier to keep them seperate to start then that's fine too.
17:51:12 <RobJN> I mean having the developer listed as simply "OpenStreetMap"
17:51:25 <zere> RobJN: for technical reasons, it's easier to separate them. however, the user of the app doesn't need to be aware of that split - it would transparent to them.
17:51:40 <RichardF> photos are essentially an exercise in cloud storage. it doesn't have to be (shouldn't be) anything to do with OSM core infrastructure.
17:51:46 <RobJN> zere: correct.
17:52:28 <zere> right, but having the developer listed as "OpenStreetMap" means that OSMF will be the owner, will take any liability, etc... that's going to require a lot more hoop-jumping than simply releasing an app.
17:52:38 <RobJN> But it would be nice to have some level of "officialness" just like the defualt editor on osm.org
17:52:53 <RobJN> So making the apps available at: https://play.google.com/store/apps/developer?id=OpenStreetMap
17:53:10 <zere> then there'll be continued effort put into 1) preventing other people from using the OSM brand, 2) evaluating other apps which wish to be under the OSM portal/umbrella
17:53:11 <RobJN> zere: correct, but let me have a go :-)
17:53:21 <RichardF> zere: to be fair, we do 1 already
17:53:55 <pnorman> We should probably see if we can start jumping through the hoops, if solely to stop others from claiming their apps as official when they aren't
17:54:01 <RobJN> I can approach the OSMF with the idea and they can knock it back if they want, but don't ask=don't get
17:54:03 <zere> we do (1) very badly at present, partly, i think, because we don't have an "official" app and partly because no-one puts in the continued effort to do it
17:54:31 <zere> oh, i wasn't suggesting we don't do it. i was simply "managing expectations" ;-)
17:56:07 <RobJN> So the bit I want to add to my report before sending it to OSMF board is some endorsements basically stating that you are happy to see the app on the play store under OpenStreetMap in theory, reliant on the code being of sufficient quality.
17:56:58 <zere> i think that's premature. there's no point writing any sort of report or asking for any kind of permission until there's an actual app on an actual store.
17:57:22 <pnorman> I would like to see the EWG recommend OpenStreetMap claimed on the stores independent of the app
17:57:41 <RobJN> Well I was hoping that it might spark some interest in it so that I can find developers will to work on it :-)
17:57:48 <pnorman> Although, do we need an app to open an OpenStreetMap portal?
17:58:56 <RobJN> Basically I've taken it as far as I can, so the main way I can help now is by doing that "hoop jumping" (both for myself and Richard)
18:00:36 <zere> what i'm afraid of is that you take a proposal to the board, they discuss it, hopefully approve it, and... then nothing happens. a year from now, someone comes along with a working app and is now in a worse position because they're "blocked" by a vapourware app which never existed.
18:01:14 <RobJN> So I was thinking of a time limit. Say 1 year.
18:01:18 <zere> additionally, board approval of a "sight unseen" app just makes it a complete wildcard. people will rush to put anything on that pedestal, regardless of the actual quality.
18:01:39 <pnorman> I wouldn't want to recommend anything specific to this app. Should we say an app of sufficient quality, with potentially other criteria put upon it?
18:02:37 <RobJN> Really I'd be asking the board to agree to the potential for OpenStreetMap to be used as a name on the app stores and to establish some acceptance criteria
18:03:16 <RobJN> The app would be an example of what we could put on the store
18:03:36 <RobJN> Richard's suggestion would be a second example.
18:04:01 <RobJN> And if you wanted a full blown editor then there are Android and iOS examples already in existance.
18:04:14 <pnorman> I agree with recommending for the potential for the name to be used, but not with tieing it to any app yet. I think it's premature to have acceptance criteria - also, keep in mind we didn't set down acceptance criteria for iD before it was developed
18:05:18 <RobJN> I just don't want to see the goal posts moving every time!
18:05:44 <zere> right, so would it be better to talk to the developers of those existing full-blown editors (Vespucci, i guess?) and see if they would want to use the OSM name and accept whatever criteria that come with that?
18:06:19 <RobJN> Could do. Question is do we want the first OpenStreetMap app to be a complex one.
18:06:40 <RichardF> well, that depends if anyone writes it ;)
18:06:59 <zere> that ship has rather sailed - vespucci exists (and is complex) :-/
18:07:16 <pnorman> RobJN: I'm not opposed to setting criteria, just setting criteria this early. The criteria may differ depending on the target of the app, what else exists in the space, and other factors
18:07:21 <RobJN> The ship is the "OpenStreetMap" portal on the stores
18:07:22 <zere> whether it's "official" is, i would suggest, not spectacularly important to 99% of users.
18:08:06 <RobJN> Possibly not but it gives people a single place to go to to find OSM apps
18:08:35 <zere> i think people just put "openstreetmap" into the app store search box, don't they?
18:08:40 <pnorman> yes
18:08:47 <RobJN> It also enables you to then promote it via the CWG
18:08:50 <zere> then look at how many stars it has, reviews, screenshots, etc...
18:09:34 <zere> i guess what i'm trying to say is that i think the quality of the app is more important than its official status (not that the latter is unimportant, just less important)
18:10:02 <RobJN> functionality/UI as well
18:10:19 <pnorman> that's part of the quality of the app
18:12:10 <zere> as for getting this written, i can see a few ways forward: 1) we've been thinking about running a "themed" hack weekend, and this might be an ideal candidate. not, perhaps, that it can be finished in a single weekend, but a good start can be made and hopefully momentum kept up afterwards
18:12:11 <RobJN> So given that I'm not a dev, my opions are to (a) throw this idea out on dev ML and see if anyone picks up up out of their own good will, (b) try and get some OSM sign-on first to then hope that someone is more likely to pick it up, failing that start looking for funding/sponsorship (which would be near impossible advertising this as a "Rob Nickerson" app)
18:12:50 <RobJN> A hack weekend sounds great
18:13:54 <zere> 2) take the idea to the board and get *WG (i guess either CWG or EWG) to run a competition: "we're looking for an official app, here's a document with some ideas, here's a panel of judges and judging criteria. the best app on the DD/MM/2015 will be blessed."
18:14:03 <RobJN> (p.s. Vespucci on Android, Go Map!! on iOS were the two I was thinking off)
18:14:33 <RichardF> 1 is good. I'm not sure we're anywhere near 2 yet
18:15:01 <RichardF> and having a lot of developers competing with each other would be a really bad way of doing things
18:15:07 <zere> 3) make a more flashy set of mock-ups and run a crowdfunding campaign to get it written. (to my mind, this is the highest risk and lowest payoff version - we get no continuity of app development, and run a high risk that the project will run out of money and fail)
18:15:25 * RichardF gets back to the Swift course
18:15:35 <zere> RichardF: yes, the downside to (2) is that we'd get competition where collaboration would really be more helpful
18:15:58 <RichardF> I'd suggest we start with 1. the next steps will become more apparent as we actually start to build things
18:16:35 <RobJN> With (2) you could ask devs to approach you before writing any code. See who is interested and then put a small group together??
18:17:00 <RobJN> Was (1) hack weekend? or just to put the idea on dev ML?
18:17:04 <RichardF> hack weekend
18:17:08 <RobJN> ok
18:17:36 <zere> no reason not to do both. personally, i think it makes sense to start with a hack weekend, but there are downsides to that too.
18:17:47 <RobJN> My concern with dev ML is that it opens you up to the wild west, things getting added to and losing the simplicity of the idea
18:18:39 <zere> that's true. it's a quesion of how much "top-down control" you want to exercise and how much you're willing to let that put off developers.
18:18:44 <RichardF> also, I'd gently add in here that SOTM-US is June 6-8 and will (I suspect) have more OSM-inclined mobile developers than any other event has yet had
18:19:11 <RichardF> zere: there are actual developers (the sort that develop) on the dev@ list? :p
18:19:42 <zere> anyone who's volunteering their time (and even a paid dev) is going to want to have input into the idea, which will tend to drive it away from the purity of the original concept.
18:19:51 <pnorman> Regardless, I'd like to get the wheels turning on creating an OpenStreetMap portal and in principle saying that apps may be added to it if they meet yet to be determined criteria
18:19:58 <zere> RichardF: i think so. generally lurking, though ;-)
18:20:54 <zere> pnorman: "yet to be determined criteria" seems synonymous with "continually moving goalposts"
18:21:32 <pnorman> zere: I don't see it as that. An editing app may have a different set of criteria than a data collecting app
18:22:06 <RobJN> zere: well yes I appreciate that, and I would dare suggest how to code it, I do feel that we should agree the design up front and stick to that. It has to be dead simple otherwise it won't avheive it's objective
18:22:15 <RobJN> *wouldn't dare
18:22:33 <zere> pnorman: sure, but if you're not prepared to think about, write down and be transparent about the criteria up-front then it's very confusing and quite possibly scary for anyone attempting to meet those criteria
18:22:42 <RobJN> (long day! and I can't type at the best of times!)
18:23:23 <pnorman> zere: perhaps say something about criteria to be determined in advance of development? but then we've got the possibility of adding existing apps
18:24:49 <RobJN> On criteria you could say that a data collecting app should upload to a central place so that any map editors could use the collected data. The uploading should be direct from the app so no faffing with copying the files to a computer first.
18:25:08 <zere> i think i'd be happy to try and run a hack weekend (perhaps in April?) on the theme of a simple OSM data collection app. i'd like RobJN to come along to explain the concept, and RichardF to sprinkle potlatch-dust on it. sounds good?
18:25:16 <RichardF> I'm up for that
18:25:36 <pnorman> zere: in many ways I see it as someone proposing a project to come up with criteria, along with milestones, etc and all the other standard project proposal stuff
18:25:44 <RobJN> I'm in (assuming we are looking at the UK as a location)
18:26:36 <RobJN> So actions: (1) Hack weekend in April (2)??
18:26:54 <zere> pnorman and RobJN: do you want to take something forward to the board broaching the topic of having an official class of apps? given the board's historical decision-making speed, perhaps the hack weekend will occur first ;-)
18:27:36 <pnorman> I'm not going to have time to do anything before the karlsruhe hack weekend
18:28:08 <zere> pnorman: criteria, milestones and standard project management stuff are (in my experience) in fact actively harmful to open, collaborative, "bazaar" projects.
18:28:08 <RobJN> zere: Can do. pnorman would you have enough time to get me on email and suggest what I should be preparing?
18:28:56 <pnorman> zere: you said we want acceptance criteria
18:29:56 <pnorman> RobJN: have you ever done a project proposal?
18:30:03 <zere> pnorman: if you're running a competition, or setting up an open class - yes.
18:30:30 <zere> s/setting up an open class/asking people to submit their apps for approval/
18:31:33 <zere> milestones and project management imply continued development under OSMF's supervision which... is too horrific to comprehend.
18:31:51 <RobJN> pnorman: I've put projects out to tender and seen the reports that have come back in. I've got the pdf written up that was linked to at the start of the meeting.
18:32:22 <RichardF> I think we have to accept that any "official OSM" mobile app would have a developer-maintainer, just like all other OSM software does.
18:32:37 <RichardF> (TomH for rails_port, me for P2, jfire for iD, and so on.)
18:32:43 <RobJN> I'm not wanting to do any rigorous project management as it's probably too much for an open community
18:32:58 <RichardF> having it ruled by a non-developer or, god forbid, a committee would be a disaster.
18:33:01 <RichardF> let's stick to what we know works.
18:33:39 <RobJN> The main ongoing work is to keep any Photo server up and running
18:33:56 <pnorman> RobJN: nor am I - but if you know how the more rigorous project management works it's helpful as then you can strip away parts that aren't desirable
18:34:04 <RobJN> The app should be so simple that it rarely needs an update (unless iOS / Android radically change)
18:34:06 <zere> RobJN: i think there's a case to be made that an "official" stamp - being included in the OSM apps umbrella - would help. the next step on that is thinking what the minimum criteria are (e.g: no spyware. no ads? works globally? supports at least these translations? etc...)
18:34:15 <RichardF> hmm... photo server... maybe we've finally found something to do with Amazon's offer of support ;)
18:35:13 <RobJN> zere: Yeah really basic criteria like what you have just suggested is what I had in mind.
18:35:14 <zere> RichardF: s/offer of support/desire to maximise PR while minimising actual usefulness to OSM/ sure.
18:37:44 <zere> okay... so i think we have our two sets of actions: i'll start planning for a hack weekend with this as a theme (helped by RobJN and RichardF), and RobJN will continue to make a case for "official" status on the app store and the minimum criteria for that.
18:37:48 <zere> sounds good?
18:38:17 <RobJN> Yep, sounds good to me.
18:38:48 <zere> awesome :-)
18:38:53 <zere> #topic AoB
18:38:59 <tmcw> just fyi, might want to look at coffeedex, this is the problem space it is a demo of
18:39:21 <zere> anyone else have something to discuss (hopefully very quickly, as we're over time already)?
18:40:18 <RichardF> not me
18:40:21 <RichardF> (and coffeedex is fun)
18:41:18 <pnorman> Just noting that I'm hoping to tag a new osm2pgsql minor version (0.87.3?) soon
18:41:22 <zere> it's certainly part of the discussion we'll have to have (native vs. whatever you call a locally-installed web app without the web)
18:41:39 <RobJN> What's possible with the new Rasberry Pi (that was announced today)? Anything interesting that could be done with it as a way of introducing OSM to people?
18:41:41 <tmcw> yep. factor in react-native for that conversation
18:42:03 <zere> yeah, i watched the keynote for that, it looks totally awesome.
18:42:14 <RobJN> (That's my randon off topic asside that I thought of whilst listening to the radio today)
18:42:58 <pnorman> RobJN: I might buy one and set up osm2pgsql on it
18:44:07 <zere> RPi is definitely targetted at education, but the concept of having very cheap phones-but-not-mobile available in developing countries is very interesting.
18:45:17 <RobJN> zere: No maps in education?
18:45:38 <RobJN> OS have a pretty good grip on UK education in that space
18:45:46 <zere> yeah, i guess that didn't make much sense...
18:46:29 <zere> i meant; the RPi specifically seems targetted at teaching kids how computers work and how to program them (i.e: like the BBC micro of yore)
18:47:08 <RobJN> That's the aim of the RPi Foundation. And from what I can see, they seem to be doing a good job so far.
18:47:42 * pnorman is about to order two
18:47:42 <RobJN> Anyway I've got to head off. Thanks for dedicating so much time towards the mobile app ideas.
18:47:49 <zere> however, there's no reason that geography (or graph theory) couldn't be taught using OSM data.
18:48:43 <zere> but they've also sparked an explosion in RPi-like small, cheap devices which have many potential uses outside the classroom.
18:49:30 <pnorman> hah. element14 is down, raspberri pi 2 is released. any relationship?
18:50:22 <zere> okay, thanks to everyone for coming & hope to see you next week! :-)
</pre>

Engineering Working Group

Matt — Mon, 09 Feb 2015 15:39:34 GMT

Matt — Mon, 02 Feb 2015 17:25:13 GMT

Matt: /* 2015 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2015 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-02-02|2nd February 2015]] || - || ''upcoming''
|-
| [[Working_Group_Minutes/EWG_2015-01-26|26th January 2015]] || - || ''draft''
|-
| [[Working_Group_Minutes/EWG_2015-01-19|19th January 2015]] || - || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-12|12th January 2015]] || rails_port, hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || - || {{Accepted}}
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || osm2pgsql, budget || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Working Group Minutes/EWG 2015-01-19

Matt — Mon, 26 Jan 2015 17:32:27 GMT

Matt: /* Summary */

== Attendees ==

{| class="wikitable" style="font-size:0.9em;"
|-
! IRC nick
! Real name
|-
| gravitystorm || Andy Allan
|-
| RichardF || Richard Fairhurst
|-
| TomH || Tom Hughes
|-
| zere || Matt Amos
|-
|}

== Summary ==

* Ideas for hack weekends:
** Vector tiles
** Lovely Friendly OSM-branded Mobile App That Will Attract Millions More Contributors To Do Actual Real On-The-Ground Surveying
** Inline tag editing for rails_port
** General rails_port stuff: routing branch, 'rubocop', 'devise', etc...
** Groups?

== IRC Log ==

<pre class="forcewrap">
17:31:47 <zere> minutes of the last meeting: http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2015-01-12 - please let me know if anything needs changing.
17:31:58 <zere> #topic actions
17:32:34 <zere> we had one action arising from last meeting: RichardF, gravitystorm, pnorman, TomH, zere: think of a theme for a hack weekend to discuss next week
17:34:13 <zere> RichardF: what thoughts did you have?
17:35:33 <RichardF> vector tiles seems the obvious theme to me. I'd like to have a 'OSM mobile app' one, too, but I don't think we're quite ready to do that yet.
17:36:59 <zere> what kind of mobile app, though? an editor like vespucci?
17:38:18 <RichardF> Lovely Friendly OSM-branded Mobile App That Will Attract Millions More Contributors To Do Actual Real On-The-Ground Surveying
17:38:43 <RichardF> aka OSM's presence in the App Store namespace, just as osm.org is our presence in the web namespace.
17:38:59 <RichardF> but like I say, the idea is a bit embryonic ;) (or vapourware, if you're being less kind)
17:41:24 <zere> it's an interesting idea. i wonder how it would work to have an "official" app where we don't even really have an official editor (although i suppose having a 'default' one is pretty close)
17:41:59 <RichardF> yeah. the analogue is osm.org rather than iD/P2/JOSM, really.
17:43:25 <zere> right, so more of a 'demo' app that showcases what's possible with OSM data rather than an editor... but hooked into some kind of surveying / tracing / mapillary / something?
17:44:10 <zere> s/tracing/GPS tracing/ - to be clear ;-)
17:44:57 <RichardF> yep. it could be transformational for a lot of things - address surveying, for one. and steering it back to EWG, it needs a skillset (iOS/Android development) that we don't have in our core dev community at the moment
17:47:09 <zere> it seems like a lot of the pieces (mapbox's mobile SDK, mapillary's API (perhaps they'd share / open their SDK?), various GPX loggers) are already around
17:47:34 <zere> so perhaps it's not out of the realms of possibility for a weekend.
17:47:48 <zere> gravitystorm: what thoughts did you have?
17:48:01 <RichardF> yes, I think so. the one thing that we don't have at the moment, and which would give the app a lot more potential, is vector tiles on osm.org :)
17:48:26 <gravitystorm> zere: I had my thoughts last week :-) Rails Port stuff mainly.
17:48:55 <gravitystorm> if you want a fresh^Wrehashed example, then I would say 'inline tag editing'
17:49:07 <gravitystorm> along with all the cgimap stuff that I want to work on
17:49:14 <RichardF> and routing
17:50:12 <zere> RichardF: routing as in jsrouting branch?
17:50:14 <RichardF> yep
17:50:31 <RichardF> as in "part of a Rails port hack weekend"
17:51:00 <zere> yeah, i think TomH is/will be reviewing that at some point - i'm not sure (i really hope) there's not enough work left before the initial release to need a whole hack weekend.
17:51:11 <zere> but there's a lot of stuff that was put off for v2
17:51:40 <RichardF> zere: oh, absolutely. just thinking that if TomH identifies fixes that need to be made, we could polish them off as part of gravitystorm's suggested Rails port hack weekend
17:51:41 <zere> perhaps a hack weekend on jsrouting2, to add... a better UI? ... what else?
17:51:42 <gravitystorm> I can throw in some rails port keywords like 'devise', 'rubocop', 'rspec' etc if people need ideas
17:52:02 <gravitystorm> but those aren't exactly enticing more like hard work.
17:53:46 <zere> i think some of that will get easier and more enticing once the rails port is smaller and doing more of what rails was designed to do: make a website.
17:55:59 <zere> pnorman: what thoughts did you have?
17:58:23 <zere> TomH: what thoughts did you have?
17:58:37 <TomH> on what?
18:00:05 <zere> on themes for a hack weekend
18:00:47 <TomH> I don't really have any
18:02:17 <zere> i was also thinking about groups - it's a bit of a nebulous feature, but the core of it seems doable in a weekend. RichardF - do you think so?
18:02:20 <TomH> I mean I struggle to think of anything that might attract enough tpeople to work
18:02:55 <RichardF> zere: absolutely. I think it's the sort of feature that would benefit from four people hacking on it rather than 20, but as part of a wider Rails port weekend that may not be a bad thing.
18:03:36 <zere> sure, but if we don't try we'll never know. i think a key criterion is whether there's enough spread of technology / skills in the theme to attract a broad range of people.
18:04:02 <TomH> it's hard for multiple people to work on something like a rails port feature at the same time
18:04:11 <zere> RichardF: do you think 'groups' needs to be better defined first?
18:05:00 <TomH> or indeed anything that doesn't naturally decompose into independent modules
18:05:18 <RichardF> zere: I think most of the ideas have been expressed... somewhere... but before a hack weekend there'd certainly be some work to do in getting them all together into a coherent whole
18:06:34 <zere> hmm... then we'd have to be pretty disciplined to stop the whole weekend disappearing into one long bike-shedding discussion
18:06:57 <RichardF> zere: well, ideally, we'd have the plan ready _before_ the weekend
18:08:24 <zere> haven't there already been some plans? i seem to remember there was a group of people including yourself and Martijn who were putting something together?
18:08:35 <RichardF> yep, exactly that. it's just the plans are a bit scattered.
18:08:59 <RichardF> some in diary entries, some in pages somewhere on github.com/osmlab, etc.
18:10:30 <zere> so it sounds to me like vector tiles is a pretty popular option?
18:11:22 <TomH> I think it more chance of being parallelisable
18:11:26 <RichardF> +1 from me
18:12:17 <zere> yes, there are definitely different 'strands' of work in C++, databases, JS, cartography, etc... within the general umbrella of 'vector tiles'.
18:15:43 <zere> okay, sounds like that's sorted then :-)
18:17:28 <zere> and you're all hereby roped into helping ;-)
18:19:58 <zere> #topic AoB
18:20:07 <zere> was there anything else anyone wanted to talk about?
18:26:30 <zere> i guess not. thanks to everyone for coming, and hope to see you next week!
</pre>

Working Group Minutes/EWG 2015-01-19

Matt — Mon, 26 Jan 2015 17:30:02 GMT

Matt: /* IRC Log */

== Attendees ==

{| class="wikitable" style="font-size:0.9em;"
|-
! IRC nick
! Real name
|-
| gravitystorm || Andy Allan
|-
| RichardF || Richard Fairhurst
|-
| TomH || Tom Hughes
|-
| zere || Matt Amos
|-
|}

== Summary ==

*

== IRC Log ==

<pre class="forcewrap">
17:31:47 <zere> minutes of the last meeting: http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2015-01-12 - please let me know if anything needs changing.
17:31:58 <zere> #topic actions
17:32:34 <zere> we had one action arising from last meeting: RichardF, gravitystorm, pnorman, TomH, zere: think of a theme for a hack weekend to discuss next week
17:34:13 <zere> RichardF: what thoughts did you have?
17:35:33 <RichardF> vector tiles seems the obvious theme to me. I'd like to have a 'OSM mobile app' one, too, but I don't think we're quite ready to do that yet.
17:36:59 <zere> what kind of mobile app, though? an editor like vespucci?
17:38:18 <RichardF> Lovely Friendly OSM-branded Mobile App That Will Attract Millions More Contributors To Do Actual Real On-The-Ground Surveying
17:38:43 <RichardF> aka OSM's presence in the App Store namespace, just as osm.org is our presence in the web namespace.
17:38:59 <RichardF> but like I say, the idea is a bit embryonic ;) (or vapourware, if you're being less kind)
17:41:24 <zere> it's an interesting idea. i wonder how it would work to have an "official" app where we don't even really have an official editor (although i suppose having a 'default' one is pretty close)
17:41:59 <RichardF> yeah. the analogue is osm.org rather than iD/P2/JOSM, really.
17:43:25 <zere> right, so more of a 'demo' app that showcases what's possible with OSM data rather than an editor... but hooked into some kind of surveying / tracing / mapillary / something?
17:44:10 <zere> s/tracing/GPS tracing/ - to be clear ;-)
17:44:57 <RichardF> yep. it could be transformational for a lot of things - address surveying, for one. and steering it back to EWG, it needs a skillset (iOS/Android development) that we don't have in our core dev community at the moment
17:47:09 <zere> it seems like a lot of the pieces (mapbox's mobile SDK, mapillary's API (perhaps they'd share / open their SDK?), various GPX loggers) are already around
17:47:34 <zere> so perhaps it's not out of the realms of possibility for a weekend.
17:47:48 <zere> gravitystorm: what thoughts did you have?
17:48:01 <RichardF> yes, I think so. the one thing that we don't have at the moment, and which would give the app a lot more potential, is vector tiles on osm.org :)
17:48:26 <gravitystorm> zere: I had my thoughts last week :-) Rails Port stuff mainly.
17:48:55 <gravitystorm> if you want a fresh^Wrehashed example, then I would say 'inline tag editing'
17:49:07 <gravitystorm> along with all the cgimap stuff that I want to work on
17:49:14 <RichardF> and routing
17:50:12 <zere> RichardF: routing as in jsrouting branch?
17:50:14 <RichardF> yep
17:50:31 <RichardF> as in "part of a Rails port hack weekend"
17:51:00 <zere> yeah, i think TomH is/will be reviewing that at some point - i'm not sure (i really hope) there's not enough work left before the initial release to need a whole hack weekend.
17:51:11 <zere> but there's a lot of stuff that was put off for v2
17:51:40 <RichardF> zere: oh, absolutely. just thinking that if TomH identifies fixes that need to be made, we could polish them off as part of gravitystorm's suggested Rails port hack weekend
17:51:41 <zere> perhaps a hack weekend on jsrouting2, to add... a better UI? ... what else?
17:51:42 <gravitystorm> I can throw in some rails port keywords like 'devise', 'rubocop', 'rspec' etc if people need ideas
17:52:02 <gravitystorm> but those aren't exactly enticing more like hard work.
17:53:46 <zere> i think some of that will get easier and more enticing once the rails port is smaller and doing more of what rails was designed to do: make a website.
17:55:59 <zere> pnorman: what thoughts did you have?
17:58:23 <zere> TomH: what thoughts did you have?
17:58:37 <TomH> on what?
18:00:05 <zere> on themes for a hack weekend
18:00:47 <TomH> I don't really have any
18:02:17 <zere> i was also thinking about groups - it's a bit of a nebulous feature, but the core of it seems doable in a weekend. RichardF - do you think so?
18:02:20 <TomH> I mean I struggle to think of anything that might attract enough tpeople to work
18:02:55 <RichardF> zere: absolutely. I think it's the sort of feature that would benefit from four people hacking on it rather than 20, but as part of a wider Rails port weekend that may not be a bad thing.
18:03:36 <zere> sure, but if we don't try we'll never know. i think a key criterion is whether there's enough spread of technology / skills in the theme to attract a broad range of people.
18:04:02 <TomH> it's hard for multiple people to work on something like a rails port feature at the same time
18:04:11 <zere> RichardF: do you think 'groups' needs to be better defined first?
18:05:00 <TomH> or indeed anything that doesn't naturally decompose into independent modules
18:05:18 <RichardF> zere: I think most of the ideas have been expressed... somewhere... but before a hack weekend there'd certainly be some work to do in getting them all together into a coherent whole
18:06:34 <zere> hmm... then we'd have to be pretty disciplined to stop the whole weekend disappearing into one long bike-shedding discussion
18:06:57 <RichardF> zere: well, ideally, we'd have the plan ready _before_ the weekend
18:08:24 <zere> haven't there already been some plans? i seem to remember there was a group of people including yourself and Martijn who were putting something together?
18:08:35 <RichardF> yep, exactly that. it's just the plans are a bit scattered.
18:08:59 <RichardF> some in diary entries, some in pages somewhere on github.com/osmlab, etc.
18:10:30 <zere> so it sounds to me like vector tiles is a pretty popular option?
18:11:22 <TomH> I think it more chance of being parallelisable
18:11:26 <RichardF> +1 from me
18:12:17 <zere> yes, there are definitely different 'strands' of work in C++, databases, JS, cartography, etc... within the general umbrella of 'vector tiles'.
18:15:43 <zere> okay, sounds like that's sorted then :-)
18:17:28 <zere> and you're all hereby roped into helping ;-)
18:19:58 <zere> #topic AoB
18:20:07 <zere> was there anything else anyone wanted to talk about?
18:26:30 <zere> i guess not. thanks to everyone for coming, and hope to see you next week!
</pre>

Working Group Minutes/EWG 2015-01-19

Matt — Mon, 26 Jan 2015 17:29:36 GMT

Matt: Created page with "== Attendees == {| class="wikitable" style="font-size:0.9em;" |- ! IRC nick ! Real name |- | gravitystorm || Andy Allan |- | RichardF || Richard Fairhurst |- | TomH || Tom Hu..."

Engineering Working Group

Matt — Mon, 26 Jan 2015 17:28:28 GMT

Matt: /* 2015 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2015 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-01-26|26th January 2015]] || - || ''upcoming''
|-
| [[Working_Group_Minutes/EWG_2015-01-19|19th January 2015]] || - || ''draft''
|-
| [[Working_Group_Minutes/EWG_2015-01-12|12th January 2015]] || rails_port, hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || - || {{Accepted}}
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || osm2pgsql, budget || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Engineering Working Group

Matt — Mon, 26 Jan 2015 17:28:07 GMT

Matt: /* 2015 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2015 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-01-26|26th January 2015]] || - || ''upcoming''
|-
| [[Working_Group_Minutes/EWG_2015-01-19|19th January 2015]] || - || ''draft''
|-
| [[Working_Group_Minutes/EWG_2015-01-12|12th January 2015]] || - || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || - || {{Accepted}}
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || osm2pgsql, budget || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Working Group Minutes/EWG 2015-01-12

Matt — Mon, 19 Jan 2015 17:22:23 GMT

Matt: /* Summary */

== Attendees ==

{| class="wikitable" style="font-size:0.9em;"
|-
! IRC nick
! Real name
|-
| gravitystorm || Andy Allan
|-
| insertcoffee || Peter Johnson
|-
| pnorman || Paul Norman
|-
| RichardF || Richard Fairhurst
|-
| TomH || Tom Hughes
|-
| zere || Matt Amos
|-
|}

== Summary ==

* Breaking up the rails_port
** It would be possible to break up the database using a FDW wrapper or something equivalent, but that would still leave the website itself monolithic.
** Dangers of breaking things up:
*** Stuff stops working
*** More "pieces" - makes it harder to deploy and/or develop
** insertcoffee and people from MapZen will have a look and come back to EWG with a recommendation for discussion.
** CGImap is moving in a similar direction
*** zere is building a Ruby gem around it [https://github.com/zerebubuth/cgimap-ruby] - it's very early stages at the moment.
*** The plan is to use the gem, so as to still be able to just 'bundle install' everything, but gradually switch all parts of the rails_port which directly access API details to instead use the HTTP API.
* Hack weekends
** There's one in Karlsruhe soon [http://wiki.openstreetmap.org/wiki/Karlsruhe_Hack_Weekend_February_2015].
** RichardF suggests that a hack weekend with a theme (specific goal and/or piece of software) would attract more people and keep them engaged.
** It would need more 'organisation' and structure, and more people involved in setting it up and running it.
** It would need more than one room, one for talking/demoing/helping setup and other quieter one for heads-down hacking.
** ''ACTION'': RichardF, gravitystorm, pnorman, TomH & zere: think of a theme for a hack weekend to discuss next week.

== IRC Log ==

<pre class="forcewrap">
17:31:50 <zere> minutes of the last meeting: http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2015-01-05
17:32:01 <zere> not much in there, but if anything needs changing, let me know
17:32:16 <zere> on the agenda for day: breaking up the rails_port :-)
17:32:26 <zere> #topic breaking up the rails_port
17:33:24 <zere> the idea here is that the rails_port is pretty monolithic, but there are areas of it (the GPX traces, the API, perhaps others) which we can start breaking out as separate services
17:33:40 <zere> each of which is then smaller, easier to maintain, lower risk to deploy, etc...
17:34:01 <zere> i was reading http://blog.carbonfive.com/2014/05/29/an-incremental-migration-from-rails-monolithic-to-microservices/ earlier, but haven't fully digensted it yet
17:35:01 <insertcoffee> will read in more detail but the bullets for "A Three Phased Attack" are a good strategy of attack
17:35:53 <insertcoffee> while it's tempting to change an API while also doing a migration it's probably best to do one at a time
17:36:13 <zere> yup, i agree... makes it easier to iterate
17:36:32 <zere> i was thinking about what we'd need to break off GPX API/database to its own service
17:36:51 <zere> and i was wondering if it would require breaking off the user stuff also / first.
17:37:19 <insertcoffee> yes, from what we discussed I think the traces feature is a good starting point as it has the least interdependencies
17:38:28 <insertcoffee> re: user relations, are you thinking we may need to open a user API to ensure the data is valid?
17:39:11 <gravitystorm> it's not clear to me yet how much is work required at the rails_port level and how much is a deployment thing. For example, doing FDI wrapper stuff at the postgresql level rather than through rails
17:39:19 <insertcoffee> or could this be tied to the session data?
17:39:38 <gravitystorm> and I mean "not clear to me" as in "I haven't tried to see what works"
17:39:50 <insertcoffee> ie. you are auth'd as insertcoffee, so you can act on those records and create as insertcoffee
17:40:01 <zere> i was thinking that the point of intersection between the GPX API and "the rest" is the users table. thinking in terms of services, this means having a service (or services) to manage user state - both long-lived and at the session level
17:40:36 <insertcoffee> ACK, but the question is whether is NEEDS to be done before the GPX API
17:40:59 <zere> yes, that's the question :-)
17:41:16 <insertcoffee> We can have an engineer explore this issue and report back here for further dicussion
17:41:19 <gravitystorm> our approach to users wrt rails_port( + gpx) + help + wiki + osmfoundation + forum needs a fair bit of careful thinking, and for once I'd recommend a bit of forward planning over jfdi
17:42:22 <zere> i agree, that's why i brought it up. i'd love to see user accounts extended to other services, but that seems unlikely in the short term (e.g: people often have different account names for the wiki and main API)
17:43:17 <zere> insertcoffee: sounds like a great idea. i've no real experience designing micro-services stuff - i'm kinda trying to think about this intuitively, but there's only so far that can work
17:43:20 <insertcoffee> I personally feel the User API will end up being far more complex than we think and starting small would be better, then tackling the 'harder' APIs once we have something done
17:44:25 <gravitystorm> we already have various levels of integration with help and the forum (iirc) albeit not with the wiki
17:45:00 <gravitystorm> so it's worth making sure we don't break existing stuff
17:45:09 <insertcoffee> So as a first step. mapzen will take a stab at a recommendation of how the traces feature could be split out and we will discuss that as a group at a future meeting
17:45:30 <insertcoffee> Can we document this stuff somewhere, so whoever works on it is well informed?
17:46:30 <zere> backing up to a previous point: there's a difference between splitting at the database level (e.g: with something like FDW) and splitting at the code level - the latter decouples to a greater extent and (hopefully, at least) makes both components smaller and easier to develop & maintain
17:47:05 <zere> insertcoffee: yeah, these meetings are all archived in full at http://www.osmfoundation.org/wiki/Engineering_Working_Group#Minutes
17:47:11 <insertcoffee> I think we try to handle both those points at the same time
17:47:25 <insertcoffee> is there an easier way than reading through all the past meeting notes?
17:48:55 <zere> i'm not sure i understand - an easier way to do what?
17:49:35 <insertcoffee> re: "so it's worth making sure we don't break existing stuff"
17:49:51 <insertcoffee> I mean, so the engineer understands what not to break ;)
17:51:26 <zere> oh, that's about the user API... not sure that's really documented anywhere at all. basically, some services (the forums for sure, but i'm not sure about help) abuse the user/details API in an attempt to use OSM like an OpenID provider.
17:51:38 <insertcoffee> oh ok
17:52:01 <zere> as long as the current API for rails_port is maintained, it shouldn't break anything
17:52:14 <zere> for some values of "shouldn't", anyway ;-)
17:52:15 <insertcoffee> FYI, I have to run in 5 minutes, really sorry but we have a 2015 planning meeting that I must attend at 18:00 GMT
17:52:31 <zere> no worries
17:53:06 <insertcoffee> so, I will figure out who will work on this; someone senior; and get them to look over it to understand it better
17:53:19 <insertcoffee> then we will discuss specific points in a future meeting
17:53:21 <insertcoffee> sound good?
17:53:54 <zere> yeah, that sounds great :-)
17:54:17 <zere> in my searches on the internet earlier, i was hoping to find an article written by someone who'd already done something like this
17:54:28 <zere> i.e: broken up a large, already-existing, complex application into services.
17:54:51 <insertcoffee> ok cool, I better run away then, please email me if you want to discuss further :)
17:54:53 <zere> but most of what i can find is either trivial (as in the article i linked to earlier) or greenfield.
17:55:02 <zere> insertcoffee: cool, thanks!
17:55:09 <insertcoffee> I have a fair bit of experience there, mostly in nodejs
17:55:17 <insertcoffee> kk, thanks, cya!
17:56:54 <zere> gravitystorm, pnorman: what do you think about what we've discussed so far?
17:58:46 <gravitystorm> zere: it's a reasonable place to start, lets see how things go. I have a desire to ensure that the separation remains seamless for hackers and private deployers (i.e. doesn't make the rails_port a nightmare to set up) but that, of course, is secondary to OSMF operations
17:59:23 * pnorman doesn't know rails
17:59:40 <TomH> well I assume we're only talking about a couple of components right? not fragmenting into a billion pieces?
17:59:49 <TomH> rails for web, cgimap for api?
17:59:57 <TomH> maybe something separate for gpx api
18:00:10 <zere> gravitystorm: i completely agree, and i think how the application gets carved up will make a big difference to how "locally deployable" it is.
18:01:36 <zere> yeah, i think we're talking about carving off one component at a time. it will probably make sense when to stop, as we'll see the benefits start to dry up.
18:02:31 <TomH> well I don't even see it that black and white
18:02:44 <zere> it's still not clear to me whether we'd do this at an "internal API" level, and leave all the GPX-related UI stuff in rails_port, or whether it would be a completely separate application.
18:02:44 <TomH> it's more like "finish off moving api to cgimap"
18:02:53 <TomH> then "gradually rewrite web code to use api"
18:03:18 <TomH> I don't think you can sanely split the web into multiple pieces
18:03:34 <TomH> unless you decide to literally make it completely separate with it's own design etc
18:04:19 <TomH> but anyway, do we actually somebody volunteering to do all this?
18:04:27 <TomH> or is this just pie in the sky?
18:04:57 <gravitystorm> TomH: yep, insertcoffee/mapzen are tasking an engineer to investigate
18:05:16 <zere> i've been working (slowly) on the cgimap stuff, and it sounds like insertcoffee and mapzen are willing to put some effort into it as well. (or, what gravitystorm said)
18:05:30 <TomH> cool
18:05:52 <TomH> I mean that definitely one of the the first things (and relatively easy for the read stuff at least) to think about
18:06:35 <zere> sadly, i think for compatibility, i'm going to have to make some changes to cgimap internals. basically, so that i can extract the (marked up) status code, headers and body separately. currently it writes it all to a stream, which i don't fancy parsing.
18:07:43 <zere> gravitystorm: you might find this interesting - the cgimap gem now has a (pretty close to full) test suite: https://github.com/zerebubuth/cgimap-ruby
18:07:56 <gravitystorm> zere: I was just looking at that :-)
18:07:59 <TomH> zere: what do you need to extract them for?
18:09:43 <zere> TomH: unless the rack request supports socket hijacking, the status code, headers and body have to be added separately to the response.
18:10:15 <zere> of course, we'd prefer socket hijacking in practice, but i'm fairly sure whatever internal mocking rails tests use don't support it
18:10:33 <TomH> oh for cgimap-ruby you mean
18:10:42 <zere> yup
18:10:43 <TomH> sorry was just think of fastcgi version
18:11:05 <TomH> forgotten now why we even want the ruby one?
18:11:18 <zere> or, indeed, if we wanted to use a different front-end other than fastcgi. i was looking at adding a libmicrohttpd one
18:12:10 <gravitystorm> TomH: we could use cgimap-ruby to gut out all the xml-building code from within the rails port
18:12:17 <zere> the ruby gem can be included in rails_port, and then it "just works" without needing anyone to run a fleet of separate (and hard to deploy) servers.
18:13:06 <gravitystorm> my plan is to use that to mean we can do authenticated things where the auth stuff is done in rails but the xml-stuff handed over to the gem. zere has other ideas though which are similar but different.
18:13:18 <zere> right, and then you can have a smaller rails_port which either runs cgimap in-process (e.g: for local dev or small deployments), or as separate fastcgi/http servers for better control.
18:14:11 <zere> eventually ("gradually rewrite web code to use api") the rails_port itself will end up not using the gem, which will be removed.
18:14:20 <TomH> yeah I'm conflicted - my real preference would be to rip the api code out of the rails stuff completely
18:14:21 <zere> so it's kind of like a transitional scaffold.
18:14:29 <TomH> but I understand that makes it hard for people to wor on it
18:14:37 <TomH> hell I'd have to look at my own dev setup
18:14:47 <gravitystorm> zere: from what I can see of cgimap-ruby it looks like it's about ready to try crowbaring it into the rails_port (purely as a demo/hack I know). Is that right?
18:15:51 <zere> gravitystorm: i think you might hit this issue where the rack implementation (rails mocks, webrick, etc...) don't support socket hijacking. but i haven't tried - it's certainly close to that point.
18:16:08 <gravitystorm> sounds like a hack weekend kind of thing
18:16:43 <zere> i've been working on it today, but i've wasted some time exploring some dead ends ;-)
18:16:47 <zere> hopefully next monday.
18:16:54 <zere> speaking of hack weekends...
18:17:09 <zere> i know there's one that woodpeck is running in karlsruhe soon
18:17:45 <gravitystorm> yep, can't make that unfortunately. I had an idea to run one in London simultaneously but I'm busy that weekend too.
18:18:21 <zere> more info for the minutes: http://wiki.openstreetmap.org/wiki/Karlsruhe_Hack_Weekend_February_2015
18:18:25 * pnorman is going to be in Karlsruhe
18:21:12 <zere> we could just do what we've done in the past, but i'm not great at running these things on a regular schedule. i was wondering if there might be an opportunity to get a group of people together, to spread the burden of organisation?
18:21:37 <zere> or, more succinctly: gravitystorm, do you fancy helping out?
18:21:56 <RichardF> I wonder if _possibly_ the way to get hack weekends that attract a wider crowd (and hence fulfil EWG's remit) is to theme them
18:21:56 <gravitystorm> zere: yes
18:22:31 <RichardF> with the notion that people who aren't likely to come to a general OSM hack weekend might come to a "OSM C++ hack weekend" or an "OSM mobile app hack weekend" or something
18:22:34 <zere> RichardF: welcome, lurker! :-) i'm intrigued - could you expand on what you mean by "theme them", please?
18:22:40 <zere> #topic hack weekends
18:22:40 <RichardF> i.e. you get C++ developers to the former, mobile developers to the latter
18:23:21 <RichardF> or even a more definite theme than that, e.g. "we are going to write an <n>"
18:24:11 <zere> i've always shied away from that, thinking that we might put off people who don't feel like they could contribute, or add a layer of organisational burden, or something... clearly it would need to be more "organised" than i'm generally able to manage ;-)
18:25:27 <zere> putting it another way, it's a lot less "casual"...
18:25:59 <zere> how would you see it working? we pick a topic, or a goal, and spend some time briefing people on the first day?
18:26:21 <RichardF> it might not be something we need to consider until we actually have a project that needs it. but (say) if we decided OWL needed resuscitating, yet we didn't have anyone with the skillset to do so, organising a hack weekend for that could be a good way to get capable people
18:26:37 <zere> i know the workshops/lectures at previous hack weekends were very enthusiastically received.
18:26:49 <RichardF> ideally you want to provide a briefing in advance (i.e. coming along to the hackday? you might want to read this / check this out first)
18:27:10 <RichardF> given that IME large% of any given hackday is spent installing the thing I want to hack on :|
18:27:56 <zere> is it better to have one project/focus, or allow several to provide coverage/variety?
18:28:31 <RichardF> with my marketing hat on I'd say "one, for clarity". though I suspect you'd probably get the hackday regulars along anyway
18:29:49 <zere> e.g: if we ran one on, for the sake of argument, original XAPI... that might be a tough call. "first, install this random binary kernel module, then download MUMPS..."
18:30:01 <zere> i know many people feel the same way about C++...
18:30:11 <zere> or, for that matter, actionscript :-)
18:30:31 <RichardF> true. you'd probably want to say "don't worry if you can't get it set up, we'll help at the hackday". but if you can get a few people to hit the ground running, so much the better
18:30:49 <RichardF> I guess "familiarising more people with codebase X" is probably a good outcome for any hackday anyway.
18:31:08 <zere> so you at least need a core of >1 person to do 1:1 or small-group tutoring.
18:31:19 <zere> it becomes semi-educational
18:31:59 <RichardF> ideally 2+ people who are clued up on the project in question, yes.
18:32:06 <zere> and, i guess, the thing needs to be broken down into "bite size" chunks previously, so that people can work on multiple aspects concurrently
18:32:27 <zere> damn, that requires a project with a truck number >1 in the first place ;-)
18:32:41 <RichardF> either that or a new project where everyone is starting from 0 ;)
18:33:39 <RichardF> it's just an idea - can you think of any projects that could benefit from such an approach?
18:34:21 <RichardF> osm-carto might be one but I'm not convinced there's a sufficient number of github-savvy cartographers/designers to run one (in the UK, that is - perhaps more likely in the US)
18:34:22 <zere> in terms of the educational aspect - and raising the truck number: all of them
18:35:23 <RichardF> come to think of it, it's maybe a good argument for de-monolithing the Rails port - smaller codebases to grasp => more approachable to new developers => run hackdays on single aspects
18:36:24 <zere> as a very hands-on workshop flavoured hack weekend, i can see that working. prepare materials up-front, spend the saturday morning on setup / orientation, then the afternoon in "education" mode, then the sunday on "now implement this".
18:36:44 <zere> gravitystorm: what do you think?
18:37:00 <TomH> but do we have any project where there are enough people interested in learning it to make this work?
18:37:14 <zere> i don't know. but it might be interesting to find out
18:38:56 <gravitystorm> so my feelings are: * we should go with osm-themes (e.g. owl) rather than technology themes (e.g. c++). Most of the osm projects need a fair amount of cross-discipline work anyway, like designing svg icons + carto + db profiling for osm-carto
18:39:48 <gravitystorm> I do find myself running into a wall with no-theme hackdays since it's often very distracting, but I also know that people like them since they can't otherwise commit to 2x10 hours coding at home of a weekend
18:40:37 <gravitystorm> so I think we should try having a theme, but with a FAQ at the bottom saying you're welcome to attend and work on other osm-things
18:41:12 <gravitystorm> and I think it would be good if, like at sotm-eu, there are multiple rooms e.g. one for talking/demoing/helping setup and other quieter one for heads-down hacking
18:42:52 <RichardF> makes sense.
18:43:59 * TomH doesn't remember that, but it makes sense I guess
18:44:36 <zere> i had an especially quiet room for heads-down hacking ;-)
18:44:52 * RichardF had a quiet mountainside :)
18:45:32 <zere> this all sounds very reasonable so far. so do we start with a theme, or start planning and leave the theme until later...?
18:46:27 <RichardF> are there any themes that immediately spring to mind?
18:47:20 <gravitystorm> well, I want to hack on cgimap-ruby :-)
18:47:53 <gravitystorm> so a general 'rails_port' theme could work. The downside is that it's a big beast.
18:47:53 <zere> OWL has been mentioned already. i don't know what the current state of that is, but it could probably do with some help.
18:48:38 <gravitystorm> could owl be one of those things where a bunch of effort gets it working again? i.e. a hack weekend with a goal?
18:49:01 * gravitystorm reminisces about the i18n hack weekend
18:49:09 <zere> i think "rails_port" as a whole is too big. but some aspect of it might work... but i can't think of such an aspect right now... is "groups" still a thing?
18:49:43 <zere> yeah, i don't know enough about the current state of OWL to know how far it might be from "working again".
18:50:00 <RichardF> I'd love it if groups was... it's been in abeyance for a while because I hit a coding wall, but it'd be great to resuscitate it, and there've been sporadic bits of interest
18:50:32 <gravitystorm> does EWG have an up-to-date list of osm projects that it's interested in? Or is https://github.com/gravitystorm/osm100/blob/master/projects.yml still a reasonable list?
18:50:54 <gravitystorm> (it came from the developer survey a while back)
18:51:46 <zere> RichardF, gravitystorm, pnorman, TomH, zere: we all get homework (a.k.a: an action) - think of a theme for a hack weekend to discuss next week :-)
18:52:10 <RichardF> ok :)
18:52:36 <zere> i think that list is about right, except perhaps jxapi should be taken off and/or replaced with pyxapi. i don't think jxapi is actively maintained any more
18:52:55 <zere> perhaps pyxapi isn't either... overpass has rather taken over that space.
18:53:48 <zere> and i'm sure there's lots of interest in vector tiles, too. not to be too parochial about it, but it would be awesome to get avecado into a "apt-get install working-osm-tileserver" state.
18:53:56 <RichardF> hell you're right
18:54:04 <RichardF> vector-tiles-on-osm.org is a hack weekend in itself
18:54:56 <pnorman> zere: I have instructions for installing avecado
18:55:16 <zere> pnorman: sure, but avecado != working-osm-tileserver ;-)
18:55:48 <zere> RichardF: that's excellent! a more modest goal than working-osm-tileserver, but would still be very useful
18:56:35 <zere> hopefully we can continue next week, when we've all done our homework.
18:56:42 <RichardF> I do have an idea for a future project and hack weekend that has "osm.org can serve vector tiles" as a dependency, but that's a story for another time ;)
18:56:58 <zere> but, until then, is there anything else anyone wanted to discuss?
18:57:02 <zere> #topic AoB
18:57:29 <pnorman> zere: well yes, but that gets into having a render stack that's sane to deploy
18:57:44 <zere> yup, that's why it's so hard :-/
18:58:02 <pnorman> currently we don't - mod_tile/renderd is scary, as are others
18:58:47 <RichardF> it may be obsoleted by vector tiles, but right now I have a project where I'd love UTFGrid in mod_tile/renderd
18:58:49 <zere> mod_tile/renderd is scary, mapnik-master is scary, osm2pgsql (+ postgres, on some platforms) is scary, downloading planet is scary :-)
18:59:15 <RichardF> at present the alternatives are (a) learn Tilestache (b) pregenerate all the tiles. I'm leaning towards (b)
18:59:40 <pnorman> osm2pgsql data loading isn't too bad on ubuntu - I've pointed completely new people at http://switch2osm.org/loading-osm-data/ and had them follow it successfuly
19:02:06 <TomH> RichardF: I think vector tiles is a bit more than a weekend!
19:02:45 <zere> sure, due to the huge efforts of a small number of people, it's much less scary than it used to be. but i'd say it's still pretty scary for a lot of people.
19:02:50 <pnorman> zere: for one of my personal projects I'll be running avecado_server to generate openstreetmap-carto vector tiles
19:02:54 <RichardF> TomH: oh, absolutely. but perhaps we could get the ball rolling within a weekend, such that people had something to go away and hack on afterwards
19:03:51 <zere> to be honest, i don't think we are more than a weekend away from *an* implementation for osm.org. we might be more than weekend away from a *good* implementation, though ;-)
19:05:31 <zere> i set up avecado_server behind an apache reverse proxy & cache, and it was pretty good. i'm not sure it would scale, but that's a problem it would be easy enough to attack at a hack weekend.
19:05:36 <TomH> RichardF: the technology stack might be a weekend - actually migrating the style is the big job
19:06:13 <pnorman> TomH: a dumb migration of the style is an afternoon. I did it
19:06:32 <TomH> really? I imagined it would be a much bigger job than that
19:06:36 <zere> carto -> webgl compiler as a stream of that hack weekend. sounds good to me :-)
19:06:44 <pnorman> Unless you're talking about migrating to mapbox-gl, in which case, oh god no
19:06:50 <TomH> well in a month or so when the tile servers collapse maybe we can use that as an excuse
19:08:23 <pnorman> TomH: actually all that's required is adding min/max zoom to each layer and then listing the layers in the new style yml MML file. I did the former in an afternoon, the latter is trivial.
19:08:32 <zere> tomh: speaking of which, when was the database on orm last vacuum full'ed or the indexes rebuilt?
19:08:56 <TomH> zere: there is insufficent space to rebuild the indexes
19:09:02 <TomH> well we might be able to do the mall ones
19:09:08 <TomH> have never been able to do the biggest
19:09:18 <TomH> autovacuum should be on
19:09:36 <pnorman> the problem is that you gain few advantages from doing that simple a conversion. and openstreetmap-carto is a huge complex beast
19:10:02 <pnorman> is OWG looking at a 3rd server or upgrading the two existing ones?
19:10:13 <TomH> but last June by the looks of it for the indexes
19:10:28 <TomH> got maybe 5% or so back then
19:10:37 <TomH> but as I say I couldn't do some of the largest ones
19:10:53 <RichardF> <devils_advocate> you could take it as an opportunity to deploy a clean-room style as the default for osm.org, and move openstreetmap-carto to a secondary, Osmarender-like style... </devils_advocate>
19:10:56 <pnorman> it's the planet_osm_ways nodes GIN index, right? that one also bloats the fastest
19:11:03 <zere> ah, so, not even worth stopping updates, creating a tablespace on / (1.5TB free), rebuilding the indexes and moving them back?
19:11:14 <pnorman> RichardF: thank you for volunteering to create the new clean-room st yle
19:11:20 <TomH> pnorman: in the first insance, fix yevaud to be less shit (https://github.com/openstreetmap/operations/issues/5)
19:11:20 * RichardF forks osm-bright
19:11:37 <TomH> and make more space (https://github.com/openstreetmap/operations/issues/6)
19:11:45 <zere> RichardF: with vector tiles you can have client-side styles - as many and as eyewatering as you like ;-)
19:12:02 <RichardF> true :)
19:12:17 <TomH> zere: well yes I could spend hours fucking around and have us running on yevaud for a weekend, or we could just sped a few quid
19:12:44 <TomH> if yevaud was less shit I might be more inclined to go with the first option
19:13:55 <zere> i think we're out of scope for EWG by now anyway. thanks for coming, and hope to see you next week (especially gravitystorm, RichardF, pnorman, TomH & myself, who have homework! :-) )
</pre>

Working Group Minutes/EWG 2015-01-12

Matt — Mon, 19 Jan 2015 17:03:20 GMT

Matt: /* Attendees */

== Attendees ==

{| class="wikitable" style="font-size:0.9em;"
|-
! IRC nick
! Real name
|-
| gravitystorm || Andy Allan
|-
| insertcoffee || Peter Johnson
|-
| pnorman || Paul Norman
|-
| RichardF || Richard Fairhurst
|-
| TomH || Tom Hughes
|-
| zere || Matt Amos
|-
|}

== Summary ==

* Happy new year!

== IRC Log ==

<pre class="forcewrap">
17:31:50 <zere> minutes of the last meeting: http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2015-01-05
17:32:01 <zere> not much in there, but if anything needs changing, let me know
17:32:16 <zere> on the agenda for day: breaking up the rails_port :-)
17:32:26 <zere> #topic breaking up the rails_port
17:33:24 <zere> the idea here is that the rails_port is pretty monolithic, but there are areas of it (the GPX traces, the API, perhaps others) which we can start breaking out as separate services
17:33:40 <zere> each of which is then smaller, easier to maintain, lower risk to deploy, etc...
17:34:01 <zere> i was reading http://blog.carbonfive.com/2014/05/29/an-incremental-migration-from-rails-monolithic-to-microservices/ earlier, but haven't fully digensted it yet
17:35:01 <insertcoffee> will read in more detail but the bullets for "A Three Phased Attack" are a good strategy of attack
17:35:53 <insertcoffee> while it's tempting to change an API while also doing a migration it's probably best to do one at a time
17:36:13 <zere> yup, i agree... makes it easier to iterate
17:36:32 <zere> i was thinking about what we'd need to break off GPX API/database to its own service
17:36:51 <zere> and i was wondering if it would require breaking off the user stuff also / first.
17:37:19 <insertcoffee> yes, from what we discussed I think the traces feature is a good starting point as it has the least interdependencies
17:38:28 <insertcoffee> re: user relations, are you thinking we may need to open a user API to ensure the data is valid?
17:39:11 <gravitystorm> it's not clear to me yet how much is work required at the rails_port level and how much is a deployment thing. For example, doing FDI wrapper stuff at the postgresql level rather than through rails
17:39:19 <insertcoffee> or could this be tied to the session data?
17:39:38 <gravitystorm> and I mean "not clear to me" as in "I haven't tried to see what works"
17:39:50 <insertcoffee> ie. you are auth'd as insertcoffee, so you can act on those records and create as insertcoffee
17:40:01 <zere> i was thinking that the point of intersection between the GPX API and "the rest" is the users table. thinking in terms of services, this means having a service (or services) to manage user state - both long-lived and at the session level
17:40:36 <insertcoffee> ACK, but the question is whether is NEEDS to be done before the GPX API
17:40:59 <zere> yes, that's the question :-)
17:41:16 <insertcoffee> We can have an engineer explore this issue and report back here for further dicussion
17:41:19 <gravitystorm> our approach to users wrt rails_port( + gpx) + help + wiki + osmfoundation + forum needs a fair bit of careful thinking, and for once I'd recommend a bit of forward planning over jfdi
17:42:22 <zere> i agree, that's why i brought it up. i'd love to see user accounts extended to other services, but that seems unlikely in the short term (e.g: people often have different account names for the wiki and main API)
17:43:17 <zere> insertcoffee: sounds like a great idea. i've no real experience designing micro-services stuff - i'm kinda trying to think about this intuitively, but there's only so far that can work
17:43:20 <insertcoffee> I personally feel the User API will end up being far more complex than we think and starting small would be better, then tackling the 'harder' APIs once we have something done
17:44:25 <gravitystorm> we already have various levels of integration with help and the forum (iirc) albeit not with the wiki
17:45:00 <gravitystorm> so it's worth making sure we don't break existing stuff
17:45:09 <insertcoffee> So as a first step. mapzen will take a stab at a recommendation of how the traces feature could be split out and we will discuss that as a group at a future meeting
17:45:30 <insertcoffee> Can we document this stuff somewhere, so whoever works on it is well informed?
17:46:30 <zere> backing up to a previous point: there's a difference between splitting at the database level (e.g: with something like FDW) and splitting at the code level - the latter decouples to a greater extent and (hopefully, at least) makes both components smaller and easier to develop & maintain
17:47:05 <zere> insertcoffee: yeah, these meetings are all archived in full at http://www.osmfoundation.org/wiki/Engineering_Working_Group#Minutes
17:47:11 <insertcoffee> I think we try to handle both those points at the same time
17:47:25 <insertcoffee> is there an easier way than reading through all the past meeting notes?
17:48:55 <zere> i'm not sure i understand - an easier way to do what?
17:49:35 <insertcoffee> re: "so it's worth making sure we don't break existing stuff"
17:49:51 <insertcoffee> I mean, so the engineer understands what not to break ;)
17:51:26 <zere> oh, that's about the user API... not sure that's really documented anywhere at all. basically, some services (the forums for sure, but i'm not sure about help) abuse the user/details API in an attempt to use OSM like an OpenID provider.
17:51:38 <insertcoffee> oh ok
17:52:01 <zere> as long as the current API for rails_port is maintained, it shouldn't break anything
17:52:14 <zere> for some values of "shouldn't", anyway ;-)
17:52:15 <insertcoffee> FYI, I have to run in 5 minutes, really sorry but we have a 2015 planning meeting that I must attend at 18:00 GMT
17:52:31 <zere> no worries
17:53:06 <insertcoffee> so, I will figure out who will work on this; someone senior; and get them to look over it to understand it better
17:53:19 <insertcoffee> then we will discuss specific points in a future meeting
17:53:21 <insertcoffee> sound good?
17:53:54 <zere> yeah, that sounds great :-)
17:54:17 <zere> in my searches on the internet earlier, i was hoping to find an article written by someone who'd already done something like this
17:54:28 <zere> i.e: broken up a large, already-existing, complex application into services.
17:54:51 <insertcoffee> ok cool, I better run away then, please email me if you want to discuss further :)
17:54:53 <zere> but most of what i can find is either trivial (as in the article i linked to earlier) or greenfield.
17:55:02 <zere> insertcoffee: cool, thanks!
17:55:09 <insertcoffee> I have a fair bit of experience there, mostly in nodejs
17:55:17 <insertcoffee> kk, thanks, cya!
17:56:54 <zere> gravitystorm, pnorman: what do you think about what we've discussed so far?
17:58:46 <gravitystorm> zere: it's a reasonable place to start, lets see how things go. I have a desire to ensure that the separation remains seamless for hackers and private deployers (i.e. doesn't make the rails_port a nightmare to set up) but that, of course, is secondary to OSMF operations
17:59:23 * pnorman doesn't know rails
17:59:40 <TomH> well I assume we're only talking about a couple of components right? not fragmenting into a billion pieces?
17:59:49 <TomH> rails for web, cgimap for api?
17:59:57 <TomH> maybe something separate for gpx api
18:00:10 <zere> gravitystorm: i completely agree, and i think how the application gets carved up will make a big difference to how "locally deployable" it is.
18:01:36 <zere> yeah, i think we're talking about carving off one component at a time. it will probably make sense when to stop, as we'll see the benefits start to dry up.
18:02:31 <TomH> well I don't even see it that black and white
18:02:44 <zere> it's still not clear to me whether we'd do this at an "internal API" level, and leave all the GPX-related UI stuff in rails_port, or whether it would be a completely separate application.
18:02:44 <TomH> it's more like "finish off moving api to cgimap"
18:02:53 <TomH> then "gradually rewrite web code to use api"
18:03:18 <TomH> I don't think you can sanely split the web into multiple pieces
18:03:34 <TomH> unless you decide to literally make it completely separate with it's own design etc
18:04:19 <TomH> but anyway, do we actually somebody volunteering to do all this?
18:04:27 <TomH> or is this just pie in the sky?
18:04:57 <gravitystorm> TomH: yep, insertcoffee/mapzen are tasking an engineer to investigate
18:05:16 <zere> i've been working (slowly) on the cgimap stuff, and it sounds like insertcoffee and mapzen are willing to put some effort into it as well. (or, what gravitystorm said)
18:05:30 <TomH> cool
18:05:52 <TomH> I mean that definitely one of the the first things (and relatively easy for the read stuff at least) to think about
18:06:35 <zere> sadly, i think for compatibility, i'm going to have to make some changes to cgimap internals. basically, so that i can extract the (marked up) status code, headers and body separately. currently it writes it all to a stream, which i don't fancy parsing.
18:07:43 <zere> gravitystorm: you might find this interesting - the cgimap gem now has a (pretty close to full) test suite: https://github.com/zerebubuth/cgimap-ruby
18:07:56 <gravitystorm> zere: I was just looking at that :-)
18:07:59 <TomH> zere: what do you need to extract them for?
18:09:43 <zere> TomH: unless the rack request supports socket hijacking, the status code, headers and body have to be added separately to the response.
18:10:15 <zere> of course, we'd prefer socket hijacking in practice, but i'm fairly sure whatever internal mocking rails tests use don't support it
18:10:33 <TomH> oh for cgimap-ruby you mean
18:10:42 <zere> yup
18:10:43 <TomH> sorry was just think of fastcgi version
18:11:05 <TomH> forgotten now why we even want the ruby one?
18:11:18 <zere> or, indeed, if we wanted to use a different front-end other than fastcgi. i was looking at adding a libmicrohttpd one
18:12:10 <gravitystorm> TomH: we could use cgimap-ruby to gut out all the xml-building code from within the rails port
18:12:17 <zere> the ruby gem can be included in rails_port, and then it "just works" without needing anyone to run a fleet of separate (and hard to deploy) servers.
18:13:06 <gravitystorm> my plan is to use that to mean we can do authenticated things where the auth stuff is done in rails but the xml-stuff handed over to the gem. zere has other ideas though which are similar but different.
18:13:18 <zere> right, and then you can have a smaller rails_port which either runs cgimap in-process (e.g: for local dev or small deployments), or as separate fastcgi/http servers for better control.
18:14:11 <zere> eventually ("gradually rewrite web code to use api") the rails_port itself will end up not using the gem, which will be removed.
18:14:20 <TomH> yeah I'm conflicted - my real preference would be to rip the api code out of the rails stuff completely
18:14:21 <zere> so it's kind of like a transitional scaffold.
18:14:29 <TomH> but I understand that makes it hard for people to wor on it
18:14:37 <TomH> hell I'd have to look at my own dev setup
18:14:47 <gravitystorm> zere: from what I can see of cgimap-ruby it looks like it's about ready to try crowbaring it into the rails_port (purely as a demo/hack I know). Is that right?
18:15:51 <zere> gravitystorm: i think you might hit this issue where the rack implementation (rails mocks, webrick, etc...) don't support socket hijacking. but i haven't tried - it's certainly close to that point.
18:16:08 <gravitystorm> sounds like a hack weekend kind of thing
18:16:43 <zere> i've been working on it today, but i've wasted some time exploring some dead ends ;-)
18:16:47 <zere> hopefully next monday.
18:16:54 <zere> speaking of hack weekends...
18:17:09 <zere> i know there's one that woodpeck is running in karlsruhe soon
18:17:45 <gravitystorm> yep, can't make that unfortunately. I had an idea to run one in London simultaneously but I'm busy that weekend too.
18:18:21 <zere> more info for the minutes: http://wiki.openstreetmap.org/wiki/Karlsruhe_Hack_Weekend_February_2015
18:18:25 * pnorman is going to be in Karlsruhe
18:21:12 <zere> we could just do what we've done in the past, but i'm not great at running these things on a regular schedule. i was wondering if there might be an opportunity to get a group of people together, to spread the burden of organisation?
18:21:37 <zere> or, more succinctly: gravitystorm, do you fancy helping out?
18:21:56 <RichardF> I wonder if _possibly_ the way to get hack weekends that attract a wider crowd (and hence fulfil EWG's remit) is to theme them
18:21:56 <gravitystorm> zere: yes
18:22:31 <RichardF> with the notion that people who aren't likely to come to a general OSM hack weekend might come to a "OSM C++ hack weekend" or an "OSM mobile app hack weekend" or something
18:22:34 <zere> RichardF: welcome, lurker! :-) i'm intrigued - could you expand on what you mean by "theme them", please?
18:22:40 <zere> #topic hack weekends
18:22:40 <RichardF> i.e. you get C++ developers to the former, mobile developers to the latter
18:23:21 <RichardF> or even a more definite theme than that, e.g. "we are going to write an <n>"
18:24:11 <zere> i've always shied away from that, thinking that we might put off people who don't feel like they could contribute, or add a layer of organisational burden, or something... clearly it would need to be more "organised" than i'm generally able to manage ;-)
18:25:27 <zere> putting it another way, it's a lot less "casual"...
18:25:59 <zere> how would you see it working? we pick a topic, or a goal, and spend some time briefing people on the first day?
18:26:21 <RichardF> it might not be something we need to consider until we actually have a project that needs it. but (say) if we decided OWL needed resuscitating, yet we didn't have anyone with the skillset to do so, organising a hack weekend for that could be a good way to get capable people
18:26:37 <zere> i know the workshops/lectures at previous hack weekends were very enthusiastically received.
18:26:49 <RichardF> ideally you want to provide a briefing in advance (i.e. coming along to the hackday? you might want to read this / check this out first)
18:27:10 <RichardF> given that IME large% of any given hackday is spent installing the thing I want to hack on :|
18:27:56 <zere> is it better to have one project/focus, or allow several to provide coverage/variety?
18:28:31 <RichardF> with my marketing hat on I'd say "one, for clarity". though I suspect you'd probably get the hackday regulars along anyway
18:29:49 <zere> e.g: if we ran one on, for the sake of argument, original XAPI... that might be a tough call. "first, install this random binary kernel module, then download MUMPS..."
18:30:01 <zere> i know many people feel the same way about C++...
18:30:11 <zere> or, for that matter, actionscript :-)
18:30:31 <RichardF> true. you'd probably want to say "don't worry if you can't get it set up, we'll help at the hackday". but if you can get a few people to hit the ground running, so much the better
18:30:49 <RichardF> I guess "familiarising more people with codebase X" is probably a good outcome for any hackday anyway.
18:31:08 <zere> so you at least need a core of >1 person to do 1:1 or small-group tutoring.
18:31:19 <zere> it becomes semi-educational
18:31:59 <RichardF> ideally 2+ people who are clued up on the project in question, yes.
18:32:06 <zere> and, i guess, the thing needs to be broken down into "bite size" chunks previously, so that people can work on multiple aspects concurrently
18:32:27 <zere> damn, that requires a project with a truck number >1 in the first place ;-)
18:32:41 <RichardF> either that or a new project where everyone is starting from 0 ;)
18:33:39 <RichardF> it's just an idea - can you think of any projects that could benefit from such an approach?
18:34:21 <RichardF> osm-carto might be one but I'm not convinced there's a sufficient number of github-savvy cartographers/designers to run one (in the UK, that is - perhaps more likely in the US)
18:34:22 <zere> in terms of the educational aspect - and raising the truck number: all of them
18:35:23 <RichardF> come to think of it, it's maybe a good argument for de-monolithing the Rails port - smaller codebases to grasp => more approachable to new developers => run hackdays on single aspects
18:36:24 <zere> as a very hands-on workshop flavoured hack weekend, i can see that working. prepare materials up-front, spend the saturday morning on setup / orientation, then the afternoon in "education" mode, then the sunday on "now implement this".
18:36:44 <zere> gravitystorm: what do you think?
18:37:00 <TomH> but do we have any project where there are enough people interested in learning it to make this work?
18:37:14 <zere> i don't know. but it might be interesting to find out
18:38:56 <gravitystorm> so my feelings are: * we should go with osm-themes (e.g. owl) rather than technology themes (e.g. c++). Most of the osm projects need a fair amount of cross-discipline work anyway, like designing svg icons + carto + db profiling for osm-carto
18:39:48 <gravitystorm> I do find myself running into a wall with no-theme hackdays since it's often very distracting, but I also know that people like them since they can't otherwise commit to 2x10 hours coding at home of a weekend
18:40:37 <gravitystorm> so I think we should try having a theme, but with a FAQ at the bottom saying you're welcome to attend and work on other osm-things
18:41:12 <gravitystorm> and I think it would be good if, like at sotm-eu, there are multiple rooms e.g. one for talking/demoing/helping setup and other quieter one for heads-down hacking
18:42:52 <RichardF> makes sense.
18:43:59 * TomH doesn't remember that, but it makes sense I guess
18:44:36 <zere> i had an especially quiet room for heads-down hacking ;-)
18:44:52 * RichardF had a quiet mountainside :)
18:45:32 <zere> this all sounds very reasonable so far. so do we start with a theme, or start planning and leave the theme until later...?
18:46:27 <RichardF> are there any themes that immediately spring to mind?
18:47:20 <gravitystorm> well, I want to hack on cgimap-ruby :-)
18:47:53 <gravitystorm> so a general 'rails_port' theme could work. The downside is that it's a big beast.
18:47:53 <zere> OWL has been mentioned already. i don't know what the current state of that is, but it could probably do with some help.
18:48:38 <gravitystorm> could owl be one of those things where a bunch of effort gets it working again? i.e. a hack weekend with a goal?
18:49:01 * gravitystorm reminisces about the i18n hack weekend
18:49:09 <zere> i think "rails_port" as a whole is too big. but some aspect of it might work... but i can't think of such an aspect right now... is "groups" still a thing?
18:49:43 <zere> yeah, i don't know enough about the current state of OWL to know how far it might be from "working again".
18:50:00 <RichardF> I'd love it if groups was... it's been in abeyance for a while because I hit a coding wall, but it'd be great to resuscitate it, and there've been sporadic bits of interest
18:50:32 <gravitystorm> does EWG have an up-to-date list of osm projects that it's interested in? Or is https://github.com/gravitystorm/osm100/blob/master/projects.yml still a reasonable list?
18:50:54 <gravitystorm> (it came from the developer survey a while back)
18:51:46 <zere> RichardF, gravitystorm, pnorman, TomH, zere: we all get homework (a.k.a: an action) - think of a theme for a hack weekend to discuss next week :-)
18:52:10 <RichardF> ok :)
18:52:36 <zere> i think that list is about right, except perhaps jxapi should be taken off and/or replaced with pyxapi. i don't think jxapi is actively maintained any more
18:52:55 <zere> perhaps pyxapi isn't either... overpass has rather taken over that space.
18:53:48 <zere> and i'm sure there's lots of interest in vector tiles, too. not to be too parochial about it, but it would be awesome to get avecado into a "apt-get install working-osm-tileserver" state.
18:53:56 <RichardF> hell you're right
18:54:04 <RichardF> vector-tiles-on-osm.org is a hack weekend in itself
18:54:56 <pnorman> zere: I have instructions for installing avecado
18:55:16 <zere> pnorman: sure, but avecado != working-osm-tileserver ;-)
18:55:48 <zere> RichardF: that's excellent! a more modest goal than working-osm-tileserver, but would still be very useful
18:56:35 <zere> hopefully we can continue next week, when we've all done our homework.
18:56:42 <RichardF> I do have an idea for a future project and hack weekend that has "osm.org can serve vector tiles" as a dependency, but that's a story for another time ;)
18:56:58 <zere> but, until then, is there anything else anyone wanted to discuss?
18:57:02 <zere> #topic AoB
18:57:29 <pnorman> zere: well yes, but that gets into having a render stack that's sane to deploy
18:57:44 <zere> yup, that's why it's so hard :-/
18:58:02 <pnorman> currently we don't - mod_tile/renderd is scary, as are others
18:58:47 <RichardF> it may be obsoleted by vector tiles, but right now I have a project where I'd love UTFGrid in mod_tile/renderd
18:58:49 <zere> mod_tile/renderd is scary, mapnik-master is scary, osm2pgsql (+ postgres, on some platforms) is scary, downloading planet is scary :-)
18:59:15 <RichardF> at present the alternatives are (a) learn Tilestache (b) pregenerate all the tiles. I'm leaning towards (b)
18:59:40 <pnorman> osm2pgsql data loading isn't too bad on ubuntu - I've pointed completely new people at http://switch2osm.org/loading-osm-data/ and had them follow it successfuly
19:02:06 <TomH> RichardF: I think vector tiles is a bit more than a weekend!
19:02:45 <zere> sure, due to the huge efforts of a small number of people, it's much less scary than it used to be. but i'd say it's still pretty scary for a lot of people.
19:02:50 <pnorman> zere: for one of my personal projects I'll be running avecado_server to generate openstreetmap-carto vector tiles
19:02:54 <RichardF> TomH: oh, absolutely. but perhaps we could get the ball rolling within a weekend, such that people had something to go away and hack on afterwards
19:03:51 <zere> to be honest, i don't think we are more than a weekend away from *an* implementation for osm.org. we might be more than weekend away from a *good* implementation, though ;-)
19:05:31 <zere> i set up avecado_server behind an apache reverse proxy & cache, and it was pretty good. i'm not sure it would scale, but that's a problem it would be easy enough to attack at a hack weekend.
19:05:36 <TomH> RichardF: the technology stack might be a weekend - actually migrating the style is the big job
19:06:13 <pnorman> TomH: a dumb migration of the style is an afternoon. I did it
19:06:32 <TomH> really? I imagined it would be a much bigger job than that
19:06:36 <zere> carto -> webgl compiler as a stream of that hack weekend. sounds good to me :-)
19:06:44 <pnorman> Unless you're talking about migrating to mapbox-gl, in which case, oh god no
19:06:50 <TomH> well in a month or so when the tile servers collapse maybe we can use that as an excuse
19:08:23 <pnorman> TomH: actually all that's required is adding min/max zoom to each layer and then listing the layers in the new style yml MML file. I did the former in an afternoon, the latter is trivial.
19:08:32 <zere> tomh: speaking of which, when was the database on orm last vacuum full'ed or the indexes rebuilt?
19:08:56 <TomH> zere: there is insufficent space to rebuild the indexes
19:09:02 <TomH> well we might be able to do the mall ones
19:09:08 <TomH> have never been able to do the biggest
19:09:18 <TomH> autovacuum should be on
19:09:36 <pnorman> the problem is that you gain few advantages from doing that simple a conversion. and openstreetmap-carto is a huge complex beast
19:10:02 <pnorman> is OWG looking at a 3rd server or upgrading the two existing ones?
19:10:13 <TomH> but last June by the looks of it for the indexes
19:10:28 <TomH> got maybe 5% or so back then
19:10:37 <TomH> but as I say I couldn't do some of the largest ones
19:10:53 <RichardF> <devils_advocate> you could take it as an opportunity to deploy a clean-room style as the default for osm.org, and move openstreetmap-carto to a secondary, Osmarender-like style... </devils_advocate>
19:10:56 <pnorman> it's the planet_osm_ways nodes GIN index, right? that one also bloats the fastest
19:11:03 <zere> ah, so, not even worth stopping updates, creating a tablespace on / (1.5TB free), rebuilding the indexes and moving them back?
19:11:14 <pnorman> RichardF: thank you for volunteering to create the new clean-room st yle
19:11:20 <TomH> pnorman: in the first insance, fix yevaud to be less shit (https://github.com/openstreetmap/operations/issues/5)
19:11:20 * RichardF forks osm-bright
19:11:37 <TomH> and make more space (https://github.com/openstreetmap/operations/issues/6)
19:11:45 <zere> RichardF: with vector tiles you can have client-side styles - as many and as eyewatering as you like ;-)
19:12:02 <RichardF> true :)
19:12:17 <TomH> zere: well yes I could spend hours fucking around and have us running on yevaud for a weekend, or we could just sped a few quid
19:12:44 <TomH> if yevaud was less shit I might be more inclined to go with the first option
19:13:55 <zere> i think we're out of scope for EWG by now anyway. thanks for coming, and hope to see you next week (especially gravitystorm, RichardF, pnorman, TomH & myself, who have homework! :-) )
</pre>

Working Group Minutes/EWG 2015-01-12

Matt — Mon, 19 Jan 2015 17:00:20 GMT

Matt: /* IRC Log */

== Attendees ==

{| class="wikitable" style="font-size:0.9em;"
|-
! IRC nick
! Real name
|-
| pnorman || Paul Norman
|-
| zere || Matt Amos
|-
|}

== Summary ==

* Happy new year!

== IRC Log ==

<pre class="forcewrap">
17:31:50 <zere> minutes of the last meeting: http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2015-01-05
17:32:01 <zere> not much in there, but if anything needs changing, let me know
17:32:16 <zere> on the agenda for day: breaking up the rails_port :-)
17:32:26 <zere> #topic breaking up the rails_port
17:33:24 <zere> the idea here is that the rails_port is pretty monolithic, but there are areas of it (the GPX traces, the API, perhaps others) which we can start breaking out as separate services
17:33:40 <zere> each of which is then smaller, easier to maintain, lower risk to deploy, etc...
17:34:01 <zere> i was reading http://blog.carbonfive.com/2014/05/29/an-incremental-migration-from-rails-monolithic-to-microservices/ earlier, but haven't fully digensted it yet
17:35:01 <insertcoffee> will read in more detail but the bullets for "A Three Phased Attack" are a good strategy of attack
17:35:53 <insertcoffee> while it's tempting to change an API while also doing a migration it's probably best to do one at a time
17:36:13 <zere> yup, i agree... makes it easier to iterate
17:36:32 <zere> i was thinking about what we'd need to break off GPX API/database to its own service
17:36:51 <zere> and i was wondering if it would require breaking off the user stuff also / first.
17:37:19 <insertcoffee> yes, from what we discussed I think the traces feature is a good starting point as it has the least interdependencies
17:38:28 <insertcoffee> re: user relations, are you thinking we may need to open a user API to ensure the data is valid?
17:39:11 <gravitystorm> it's not clear to me yet how much is work required at the rails_port level and how much is a deployment thing. For example, doing FDI wrapper stuff at the postgresql level rather than through rails
17:39:19 <insertcoffee> or could this be tied to the session data?
17:39:38 <gravitystorm> and I mean "not clear to me" as in "I haven't tried to see what works"
17:39:50 <insertcoffee> ie. you are auth'd as insertcoffee, so you can act on those records and create as insertcoffee
17:40:01 <zere> i was thinking that the point of intersection between the GPX API and "the rest" is the users table. thinking in terms of services, this means having a service (or services) to manage user state - both long-lived and at the session level
17:40:36 <insertcoffee> ACK, but the question is whether is NEEDS to be done before the GPX API
17:40:59 <zere> yes, that's the question :-)
17:41:16 <insertcoffee> We can have an engineer explore this issue and report back here for further dicussion
17:41:19 <gravitystorm> our approach to users wrt rails_port( + gpx) + help + wiki + osmfoundation + forum needs a fair bit of careful thinking, and for once I'd recommend a bit of forward planning over jfdi
17:42:22 <zere> i agree, that's why i brought it up. i'd love to see user accounts extended to other services, but that seems unlikely in the short term (e.g: people often have different account names for the wiki and main API)
17:43:17 <zere> insertcoffee: sounds like a great idea. i've no real experience designing micro-services stuff - i'm kinda trying to think about this intuitively, but there's only so far that can work
17:43:20 <insertcoffee> I personally feel the User API will end up being far more complex than we think and starting small would be better, then tackling the 'harder' APIs once we have something done
17:44:25 <gravitystorm> we already have various levels of integration with help and the forum (iirc) albeit not with the wiki
17:45:00 <gravitystorm> so it's worth making sure we don't break existing stuff
17:45:09 <insertcoffee> So as a first step. mapzen will take a stab at a recommendation of how the traces feature could be split out and we will discuss that as a group at a future meeting
17:45:30 <insertcoffee> Can we document this stuff somewhere, so whoever works on it is well informed?
17:46:30 <zere> backing up to a previous point: there's a difference between splitting at the database level (e.g: with something like FDW) and splitting at the code level - the latter decouples to a greater extent and (hopefully, at least) makes both components smaller and easier to develop & maintain
17:47:05 <zere> insertcoffee: yeah, these meetings are all archived in full at http://www.osmfoundation.org/wiki/Engineering_Working_Group#Minutes
17:47:11 <insertcoffee> I think we try to handle both those points at the same time
17:47:25 <insertcoffee> is there an easier way than reading through all the past meeting notes?
17:48:55 <zere> i'm not sure i understand - an easier way to do what?
17:49:35 <insertcoffee> re: "so it's worth making sure we don't break existing stuff"
17:49:51 <insertcoffee> I mean, so the engineer understands what not to break ;)
17:51:26 <zere> oh, that's about the user API... not sure that's really documented anywhere at all. basically, some services (the forums for sure, but i'm not sure about help) abuse the user/details API in an attempt to use OSM like an OpenID provider.
17:51:38 <insertcoffee> oh ok
17:52:01 <zere> as long as the current API for rails_port is maintained, it shouldn't break anything
17:52:14 <zere> for some values of "shouldn't", anyway ;-)
17:52:15 <insertcoffee> FYI, I have to run in 5 minutes, really sorry but we have a 2015 planning meeting that I must attend at 18:00 GMT
17:52:31 <zere> no worries
17:53:06 <insertcoffee> so, I will figure out who will work on this; someone senior; and get them to look over it to understand it better
17:53:19 <insertcoffee> then we will discuss specific points in a future meeting
17:53:21 <insertcoffee> sound good?
17:53:54 <zere> yeah, that sounds great :-)
17:54:17 <zere> in my searches on the internet earlier, i was hoping to find an article written by someone who'd already done something like this
17:54:28 <zere> i.e: broken up a large, already-existing, complex application into services.
17:54:51 <insertcoffee> ok cool, I better run away then, please email me if you want to discuss further :)
17:54:53 <zere> but most of what i can find is either trivial (as in the article i linked to earlier) or greenfield.
17:55:02 <zere> insertcoffee: cool, thanks!
17:55:09 <insertcoffee> I have a fair bit of experience there, mostly in nodejs
17:55:17 <insertcoffee> kk, thanks, cya!
17:56:54 <zere> gravitystorm, pnorman: what do you think about what we've discussed so far?
17:58:46 <gravitystorm> zere: it's a reasonable place to start, lets see how things go. I have a desire to ensure that the separation remains seamless for hackers and private deployers (i.e. doesn't make the rails_port a nightmare to set up) but that, of course, is secondary to OSMF operations
17:59:23 * pnorman doesn't know rails
17:59:40 <TomH> well I assume we're only talking about a couple of components right? not fragmenting into a billion pieces?
17:59:49 <TomH> rails for web, cgimap for api?
17:59:57 <TomH> maybe something separate for gpx api
18:00:10 <zere> gravitystorm: i completely agree, and i think how the application gets carved up will make a big difference to how "locally deployable" it is.
18:01:36 <zere> yeah, i think we're talking about carving off one component at a time. it will probably make sense when to stop, as we'll see the benefits start to dry up.
18:02:31 <TomH> well I don't even see it that black and white
18:02:44 <zere> it's still not clear to me whether we'd do this at an "internal API" level, and leave all the GPX-related UI stuff in rails_port, or whether it would be a completely separate application.
18:02:44 <TomH> it's more like "finish off moving api to cgimap"
18:02:53 <TomH> then "gradually rewrite web code to use api"
18:03:18 <TomH> I don't think you can sanely split the web into multiple pieces
18:03:34 <TomH> unless you decide to literally make it completely separate with it's own design etc
18:04:19 <TomH> but anyway, do we actually somebody volunteering to do all this?
18:04:27 <TomH> or is this just pie in the sky?
18:04:57 <gravitystorm> TomH: yep, insertcoffee/mapzen are tasking an engineer to investigate
18:05:16 <zere> i've been working (slowly) on the cgimap stuff, and it sounds like insertcoffee and mapzen are willing to put some effort into it as well. (or, what gravitystorm said)
18:05:30 <TomH> cool
18:05:52 <TomH> I mean that definitely one of the the first things (and relatively easy for the read stuff at least) to think about
18:06:35 <zere> sadly, i think for compatibility, i'm going to have to make some changes to cgimap internals. basically, so that i can extract the (marked up) status code, headers and body separately. currently it writes it all to a stream, which i don't fancy parsing.
18:07:43 <zere> gravitystorm: you might find this interesting - the cgimap gem now has a (pretty close to full) test suite: https://github.com/zerebubuth/cgimap-ruby
18:07:56 <gravitystorm> zere: I was just looking at that :-)
18:07:59 <TomH> zere: what do you need to extract them for?
18:09:43 <zere> TomH: unless the rack request supports socket hijacking, the status code, headers and body have to be added separately to the response.
18:10:15 <zere> of course, we'd prefer socket hijacking in practice, but i'm fairly sure whatever internal mocking rails tests use don't support it
18:10:33 <TomH> oh for cgimap-ruby you mean
18:10:42 <zere> yup
18:10:43 <TomH> sorry was just think of fastcgi version
18:11:05 <TomH> forgotten now why we even want the ruby one?
18:11:18 <zere> or, indeed, if we wanted to use a different front-end other than fastcgi. i was looking at adding a libmicrohttpd one
18:12:10 <gravitystorm> TomH: we could use cgimap-ruby to gut out all the xml-building code from within the rails port
18:12:17 <zere> the ruby gem can be included in rails_port, and then it "just works" without needing anyone to run a fleet of separate (and hard to deploy) servers.
18:13:06 <gravitystorm> my plan is to use that to mean we can do authenticated things where the auth stuff is done in rails but the xml-stuff handed over to the gem. zere has other ideas though which are similar but different.
18:13:18 <zere> right, and then you can have a smaller rails_port which either runs cgimap in-process (e.g: for local dev or small deployments), or as separate fastcgi/http servers for better control.
18:14:11 <zere> eventually ("gradually rewrite web code to use api") the rails_port itself will end up not using the gem, which will be removed.
18:14:20 <TomH> yeah I'm conflicted - my real preference would be to rip the api code out of the rails stuff completely
18:14:21 <zere> so it's kind of like a transitional scaffold.
18:14:29 <TomH> but I understand that makes it hard for people to wor on it
18:14:37 <TomH> hell I'd have to look at my own dev setup
18:14:47 <gravitystorm> zere: from what I can see of cgimap-ruby it looks like it's about ready to try crowbaring it into the rails_port (purely as a demo/hack I know). Is that right?
18:15:51 <zere> gravitystorm: i think you might hit this issue where the rack implementation (rails mocks, webrick, etc...) don't support socket hijacking. but i haven't tried - it's certainly close to that point.
18:16:08 <gravitystorm> sounds like a hack weekend kind of thing
18:16:43 <zere> i've been working on it today, but i've wasted some time exploring some dead ends ;-)
18:16:47 <zere> hopefully next monday.
18:16:54 <zere> speaking of hack weekends...
18:17:09 <zere> i know there's one that woodpeck is running in karlsruhe soon
18:17:45 <gravitystorm> yep, can't make that unfortunately. I had an idea to run one in London simultaneously but I'm busy that weekend too.
18:18:21 <zere> more info for the minutes: http://wiki.openstreetmap.org/wiki/Karlsruhe_Hack_Weekend_February_2015
18:18:25 * pnorman is going to be in Karlsruhe
18:21:12 <zere> we could just do what we've done in the past, but i'm not great at running these things on a regular schedule. i was wondering if there might be an opportunity to get a group of people together, to spread the burden of organisation?
18:21:37 <zere> or, more succinctly: gravitystorm, do you fancy helping out?
18:21:56 <RichardF> I wonder if _possibly_ the way to get hack weekends that attract a wider crowd (and hence fulfil EWG's remit) is to theme them
18:21:56 <gravitystorm> zere: yes
18:22:31 <RichardF> with the notion that people who aren't likely to come to a general OSM hack weekend might come to a "OSM C++ hack weekend" or an "OSM mobile app hack weekend" or something
18:22:34 <zere> RichardF: welcome, lurker! :-) i'm intrigued - could you expand on what you mean by "theme them", please?
18:22:40 <zere> #topic hack weekends
18:22:40 <RichardF> i.e. you get C++ developers to the former, mobile developers to the latter
18:23:21 <RichardF> or even a more definite theme than that, e.g. "we are going to write an <n>"
18:24:11 <zere> i've always shied away from that, thinking that we might put off people who don't feel like they could contribute, or add a layer of organisational burden, or something... clearly it would need to be more "organised" than i'm generally able to manage ;-)
18:25:27 <zere> putting it another way, it's a lot less "casual"...
18:25:59 <zere> how would you see it working? we pick a topic, or a goal, and spend some time briefing people on the first day?
18:26:21 <RichardF> it might not be something we need to consider until we actually have a project that needs it. but (say) if we decided OWL needed resuscitating, yet we didn't have anyone with the skillset to do so, organising a hack weekend for that could be a good way to get capable people
18:26:37 <zere> i know the workshops/lectures at previous hack weekends were very enthusiastically received.
18:26:49 <RichardF> ideally you want to provide a briefing in advance (i.e. coming along to the hackday? you might want to read this / check this out first)
18:27:10 <RichardF> given that IME large% of any given hackday is spent installing the thing I want to hack on :|
18:27:56 <zere> is it better to have one project/focus, or allow several to provide coverage/variety?
18:28:31 <RichardF> with my marketing hat on I'd say "one, for clarity". though I suspect you'd probably get the hackday regulars along anyway
18:29:49 <zere> e.g: if we ran one on, for the sake of argument, original XAPI... that might be a tough call. "first, install this random binary kernel module, then download MUMPS..."
18:30:01 <zere> i know many people feel the same way about C++...
18:30:11 <zere> or, for that matter, actionscript :-)
18:30:31 <RichardF> true. you'd probably want to say "don't worry if you can't get it set up, we'll help at the hackday". but if you can get a few people to hit the ground running, so much the better
18:30:49 <RichardF> I guess "familiarising more people with codebase X" is probably a good outcome for any hackday anyway.
18:31:08 <zere> so you at least need a core of >1 person to do 1:1 or small-group tutoring.
18:31:19 <zere> it becomes semi-educational
18:31:59 <RichardF> ideally 2+ people who are clued up on the project in question, yes.
18:32:06 <zere> and, i guess, the thing needs to be broken down into "bite size" chunks previously, so that people can work on multiple aspects concurrently
18:32:27 <zere> damn, that requires a project with a truck number >1 in the first place ;-)
18:32:41 <RichardF> either that or a new project where everyone is starting from 0 ;)
18:33:39 <RichardF> it's just an idea - can you think of any projects that could benefit from such an approach?
18:34:21 <RichardF> osm-carto might be one but I'm not convinced there's a sufficient number of github-savvy cartographers/designers to run one (in the UK, that is - perhaps more likely in the US)
18:34:22 <zere> in terms of the educational aspect - and raising the truck number: all of them
18:35:23 <RichardF> come to think of it, it's maybe a good argument for de-monolithing the Rails port - smaller codebases to grasp => more approachable to new developers => run hackdays on single aspects
18:36:24 <zere> as a very hands-on workshop flavoured hack weekend, i can see that working. prepare materials up-front, spend the saturday morning on setup / orientation, then the afternoon in "education" mode, then the sunday on "now implement this".
18:36:44 <zere> gravitystorm: what do you think?
18:37:00 <TomH> but do we have any project where there are enough people interested in learning it to make this work?
18:37:14 <zere> i don't know. but it might be interesting to find out
18:38:56 <gravitystorm> so my feelings are: * we should go with osm-themes (e.g. owl) rather than technology themes (e.g. c++). Most of the osm projects need a fair amount of cross-discipline work anyway, like designing svg icons + carto + db profiling for osm-carto
18:39:48 <gravitystorm> I do find myself running into a wall with no-theme hackdays since it's often very distracting, but I also know that people like them since they can't otherwise commit to 2x10 hours coding at home of a weekend
18:40:37 <gravitystorm> so I think we should try having a theme, but with a FAQ at the bottom saying you're welcome to attend and work on other osm-things
18:41:12 <gravitystorm> and I think it would be good if, like at sotm-eu, there are multiple rooms e.g. one for talking/demoing/helping setup and other quieter one for heads-down hacking
18:42:52 <RichardF> makes sense.
18:43:59 * TomH doesn't remember that, but it makes sense I guess
18:44:36 <zere> i had an especially quiet room for heads-down hacking ;-)
18:44:52 * RichardF had a quiet mountainside :)
18:45:32 <zere> this all sounds very reasonable so far. so do we start with a theme, or start planning and leave the theme until later...?
18:46:27 <RichardF> are there any themes that immediately spring to mind?
18:47:20 <gravitystorm> well, I want to hack on cgimap-ruby :-)
18:47:53 <gravitystorm> so a general 'rails_port' theme could work. The downside is that it's a big beast.
18:47:53 <zere> OWL has been mentioned already. i don't know what the current state of that is, but it could probably do with some help.
18:48:38 <gravitystorm> could owl be one of those things where a bunch of effort gets it working again? i.e. a hack weekend with a goal?
18:49:01 * gravitystorm reminisces about the i18n hack weekend
18:49:09 <zere> i think "rails_port" as a whole is too big. but some aspect of it might work... but i can't think of such an aspect right now... is "groups" still a thing?
18:49:43 <zere> yeah, i don't know enough about the current state of OWL to know how far it might be from "working again".
18:50:00 <RichardF> I'd love it if groups was... it's been in abeyance for a while because I hit a coding wall, but it'd be great to resuscitate it, and there've been sporadic bits of interest
18:50:32 <gravitystorm> does EWG have an up-to-date list of osm projects that it's interested in? Or is https://github.com/gravitystorm/osm100/blob/master/projects.yml still a reasonable list?
18:50:54 <gravitystorm> (it came from the developer survey a while back)
18:51:46 <zere> RichardF, gravitystorm, pnorman, TomH, zere: we all get homework (a.k.a: an action) - think of a theme for a hack weekend to discuss next week :-)
18:52:10 <RichardF> ok :)
18:52:36 <zere> i think that list is about right, except perhaps jxapi should be taken off and/or replaced with pyxapi. i don't think jxapi is actively maintained any more
18:52:55 <zere> perhaps pyxapi isn't either... overpass has rather taken over that space.
18:53:48 <zere> and i'm sure there's lots of interest in vector tiles, too. not to be too parochial about it, but it would be awesome to get avecado into a "apt-get install working-osm-tileserver" state.
18:53:56 <RichardF> hell you're right
18:54:04 <RichardF> vector-tiles-on-osm.org is a hack weekend in itself
18:54:56 <pnorman> zere: I have instructions for installing avecado
18:55:16 <zere> pnorman: sure, but avecado != working-osm-tileserver ;-)
18:55:48 <zere> RichardF: that's excellent! a more modest goal than working-osm-tileserver, but would still be very useful
18:56:35 <zere> hopefully we can continue next week, when we've all done our homework.
18:56:42 <RichardF> I do have an idea for a future project and hack weekend that has "osm.org can serve vector tiles" as a dependency, but that's a story for another time ;)
18:56:58 <zere> but, until then, is there anything else anyone wanted to discuss?
18:57:02 <zere> #topic AoB
18:57:29 <pnorman> zere: well yes, but that gets into having a render stack that's sane to deploy
18:57:44 <zere> yup, that's why it's so hard :-/
18:58:02 <pnorman> currently we don't - mod_tile/renderd is scary, as are others
18:58:47 <RichardF> it may be obsoleted by vector tiles, but right now I have a project where I'd love UTFGrid in mod_tile/renderd
18:58:49 <zere> mod_tile/renderd is scary, mapnik-master is scary, osm2pgsql (+ postgres, on some platforms) is scary, downloading planet is scary :-)
18:59:15 <RichardF> at present the alternatives are (a) learn Tilestache (b) pregenerate all the tiles. I'm leaning towards (b)
18:59:40 <pnorman> osm2pgsql data loading isn't too bad on ubuntu - I've pointed completely new people at http://switch2osm.org/loading-osm-data/ and had them follow it successfuly
19:02:06 <TomH> RichardF: I think vector tiles is a bit more than a weekend!
19:02:45 <zere> sure, due to the huge efforts of a small number of people, it's much less scary than it used to be. but i'd say it's still pretty scary for a lot of people.
19:02:50 <pnorman> zere: for one of my personal projects I'll be running avecado_server to generate openstreetmap-carto vector tiles
19:02:54 <RichardF> TomH: oh, absolutely. but perhaps we could get the ball rolling within a weekend, such that people had something to go away and hack on afterwards
19:03:51 <zere> to be honest, i don't think we are more than a weekend away from *an* implementation for osm.org. we might be more than weekend away from a *good* implementation, though ;-)
19:05:31 <zere> i set up avecado_server behind an apache reverse proxy & cache, and it was pretty good. i'm not sure it would scale, but that's a problem it would be easy enough to attack at a hack weekend.
19:05:36 <TomH> RichardF: the technology stack might be a weekend - actually migrating the style is the big job
19:06:13 <pnorman> TomH: a dumb migration of the style is an afternoon. I did it
19:06:32 <TomH> really? I imagined it would be a much bigger job than that
19:06:36 <zere> carto -> webgl compiler as a stream of that hack weekend. sounds good to me :-)
19:06:44 <pnorman> Unless you're talking about migrating to mapbox-gl, in which case, oh god no
19:06:50 <TomH> well in a month or so when the tile servers collapse maybe we can use that as an excuse
19:08:23 <pnorman> TomH: actually all that's required is adding min/max zoom to each layer and then listing the layers in the new style yml MML file. I did the former in an afternoon, the latter is trivial.
19:08:32 <zere> tomh: speaking of which, when was the database on orm last vacuum full'ed or the indexes rebuilt?
19:08:56 <TomH> zere: there is insufficent space to rebuild the indexes
19:09:02 <TomH> well we might be able to do the mall ones
19:09:08 <TomH> have never been able to do the biggest
19:09:18 <TomH> autovacuum should be on
19:09:36 <pnorman> the problem is that you gain few advantages from doing that simple a conversion. and openstreetmap-carto is a huge complex beast
19:10:02 <pnorman> is OWG looking at a 3rd server or upgrading the two existing ones?
19:10:13 <TomH> but last June by the looks of it for the indexes
19:10:28 <TomH> got maybe 5% or so back then
19:10:37 <TomH> but as I say I couldn't do some of the largest ones
19:10:53 <RichardF> <devils_advocate> you could take it as an opportunity to deploy a clean-room style as the default for osm.org, and move openstreetmap-carto to a secondary, Osmarender-like style... </devils_advocate>
19:10:56 <pnorman> it's the planet_osm_ways nodes GIN index, right? that one also bloats the fastest
19:11:03 <zere> ah, so, not even worth stopping updates, creating a tablespace on / (1.5TB free), rebuilding the indexes and moving them back?
19:11:14 <pnorman> RichardF: thank you for volunteering to create the new clean-room st yle
19:11:20 <TomH> pnorman: in the first insance, fix yevaud to be less shit (https://github.com/openstreetmap/operations/issues/5)
19:11:20 * RichardF forks osm-bright
19:11:37 <TomH> and make more space (https://github.com/openstreetmap/operations/issues/6)
19:11:45 <zere> RichardF: with vector tiles you can have client-side styles - as many and as eyewatering as you like ;-)
19:12:02 <RichardF> true :)
19:12:17 <TomH> zere: well yes I could spend hours fucking around and have us running on yevaud for a weekend, or we could just sped a few quid
19:12:44 <TomH> if yevaud was less shit I might be more inclined to go with the first option
19:13:55 <zere> i think we're out of scope for EWG by now anyway. thanks for coming, and hope to see you next week (especially gravitystorm, RichardF, pnorman, TomH & myself, who have homework! :-) )
</pre>

Working Group Minutes/EWG 2015-01-12

Matt — Mon, 19 Jan 2015 16:59:52 GMT

Matt: Created page with "== Attendees == {| class="wikitable" style="font-size:0.9em;" |- ! IRC nick ! Real name |- | pnorman || Paul Norman |- | zere || Matt Amos |- |} == Summary == * Happy new y..."

Engineering Working Group

Matt — Mon, 19 Jan 2015 16:59:25 GMT

Matt: /* 2015 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2015 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-01-19|19th January 2015]] || - || ''upcoming''
|-
| [[Working_Group_Minutes/EWG_2015-01-12|12th January 2015]] || - || ''draft''
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || - || {{Accepted}}
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || osm2pgsql, budget || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Engineering Working Group

Matt — Mon, 12 Jan 2015 15:54:37 GMT

Matt: /* 2015 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2015 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-01-12|12th January 2015]] || - || ''upcoming''
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || - || ''draft''
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || osm2pgsql, budget || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Engineering Working Group

Matt — Mon, 12 Jan 2015 15:54:08 GMT

Matt: /* 2015 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2015 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || - || ''draft''
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || osm2pgsql, budget || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Working Group Minutes/EWG 2015-01-05

Matt — Mon, 12 Jan 2015 15:52:49 GMT

== Attendees ==

{| class="wikitable" style="font-size:0.9em;"
|-
! IRC nick
! Real name
|-
| pnorman || Paul Norman
|-
| zere || Matt Amos
|-
|}

== Summary ==

* Happy new year!

== IRC Log ==

<pre class="forcewrap">
17:32:15 <zere> happy new year, everyone :-)
17:32:46 <zere> minutes of the last meeting: http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2014-12-22 - if there are any problems, please let me know
17:33:51 <zere> i don't have any carry-overs from last year's meeting, i think... so we can probably open up the meeting to anything that anyone would like to discuss
17:53:30 * pnorman would like more than two people
17:57:47 <zere> well, indeed. i suppose i should poke insertcoffee... i'll see if i can interest him in coming along to the next meeting.
18:33:22 <zere> i guess that's it. let's hope it's more lively next week.
</pre>

Engineering Working Group

Matt — Mon, 12 Jan 2015 15:51:34 GMT

Matt: /* 2014 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2015 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || || ''draft''
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || osm2pgsql, budget || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Engineering Working Group

Matt — Mon, 12 Jan 2015 15:51:03 GMT

Matt: /* 2014 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2015 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || || ''draft''
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || || ''draft''
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Engineering Working Group

Matt — Mon, 12 Jan 2015 15:50:52 GMT

Matt: /* Minutes */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2015-01-05|5th January 2015]] || || ''draft''
|-
|}

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || || ''draft''
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Working Group Minutes/EWG 2014-12-22

Matt — Mon, 05 Jan 2015 17:12:25 GMT

== Attendees ==

{| class="wikitable" style="font-size:0.9em;"
|-
! IRC nick
! Real name
|-
| pnorman || Paul Norman
|-
| zere || Matt Amos
|-
|}

== Summary ==

* Osm2pgsql PR #164
** https://github.com/openstreetmap/osm2pgsql/pull/164
** The PR splits the dual meaning of the existing "polygon" flag into two separate flags.
** The name of one flag, "hstore", is misleading as it indicates whether or not the presence of a tag with that key will cause the object to be stored. While it overlaps with hstore, calling it that would lead to (even more) confusion.
** pnorman suggests "nomatch" instead, which fits better.
* Osm2pgsql release practices
** Using a numeric ''x.y.z'' triple for several revisions is potentially problematic, as it does not indicate a specific revision which can then be tested / bug fixed.
** pnorman suggests appending '-dev' or '-rcN' or something similar to distinguish the "non-release" versions.
* Budget 2015
** EWG has tried various things in the past, e.g: funding for hack weekends, without much take-up. This year it seems simpler to not budget for things we've demonstrably not spent in the past.

== IRC Log ==

<pre class="forcewrap">
17:32:52 <zere> minutes of the last meeting - they're a short read: http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2014-12-12
17:33:23 <pnorman> also osm2pgsql releases
17:33:35 <zere> on the agenda today: https://github.com/openstreetmap/osm2pgsql/pull/164 & osm2pgsql releases
17:33:47 <zere> #topic osm2pgsql PR #164
17:34:14 <zere> i must confess, i'm not entirely sure what the PR accomplishes
17:35:18 <pnorman> if you're running with hstore match only you effectively can't have name as a real column with the current version, because it forces everything with a name (i.e. lots of stuff) to appear in the tables
17:37:19 <zere> okay, but the patch doesn't appear to change the logic at all
17:38:18 <pnorman> my understanding is that by adding hstore as its own flag https://github.com/openstreetmap/osm2pgsql/pull/164/files#diff-723033792967b078548cb322ad03c2d3L86 (taginfo.cpp:87) works with linear,hstore
17:39:34 <zere> i dunno... i would have expected that FLAG_HSTORE (which didn't exist before) would have to be checked somewhere else as well?
17:42:09 <pnorman> I haven't played around with it, but i think it's sufficient. phstore was always 17 which is 16 and 1, now polygon and hstore
17:43:39 <pnorman> I think one conclusion is that it needs clear examples of usage with polygon and linear, interactions with hstore options, and tests for the above
17:46:44 <zere> yup, i guess the logic must be something like "if tag not in normal_columns then hstore", which i guess is sufficient.
17:48:05 <pnorman> in some ways the logic would be better redone inverted - one flag to indicate polygon status, and others to indicate that it belongs in the linear and/or polygon tables
17:48:18 <pnorman> but this would break every existing style file
17:49:09 <zere> s/polygon status/hstore status/?
17:49:35 <zere> i guess it needs a mention here: https://github.com/openstreetmap/osm2pgsql/blob/master/docs/usage.md#hstore although there's no existing mention ofphstore
17:51:24 <zere> in fact, i can't find where the 'style' file format is documented at all...
17:52:00 <pnorman> in default.style
17:53:40 <zere> yeah, didn't look there ;-)
17:53:41 <pnorman> and to your s/..., no - "add to hstore" is really about "don't add objects based on this flag"
17:54:04 <zere> probably worth having that doc in the "docs" directory at some point, but not important for this PR.
17:55:42 <zere> i mean, the polygon flag presumbly already indicates polygon status and whether it belongs in the linear and/or polygon tables. the hstore flag might not mean what it says, but it's unrelated to whether something goes into the polygon or linear tables (i thought that was the point of this PR)
18:03:47 * zere obtains a case of West Berk's "Yule Fuel" to celebrate planetdump-ng deployment.
18:04:10 <zere> now all i have to do is make sure i drink it before it all falls over ;-)
18:05:03 <pnorman> no, the hstore flag causes something to not go in the polygon tables unless some other command line option causes it to (an hstore option without --hstore-match-only)
18:06:05 <zere> polygon or linear, though? i thought the whole point of this PR was that it makes the hstore flag independent of the linear/polygon status?
18:06:29 <pnorman> both
18:06:46 <pnorman> but the polygon case is clearer since I understand it since it's just phstore
18:07:14 <pnorman> maybe a name like nomatch would be clearer for the flag?
18:07:31 <zere> right. so hstore is a bad name for it: "hstore_if_you_have_enabled_that_through_the_command_line_switch_or_else_drop_the_whole_feature" is better, although more of a pain to type ;-)
18:10:14 <zere> there's two separate things at work here: 1) whether the presence of this tag should cause the feature to be dropped or put in the table, 2) whether the tag should have its own column or be in an hstore column
18:10:52 <zere> nomatch would be good for (1), and hstore for (2). so perhaps leave hstore as it is for now and add an issue to split "nomatch" out as a separate flag.
18:12:08 <zere> except, of course, hstore currently implies nomatch... which is a bit of a pain. it would then require 2 new flags.
18:12:48 <zere> yes.
18:13:16 <zere> having thought about it fr all of 5 minutes: pnorman is right - it should be called nomatch at the moment. then hstore can be pulled out of it later.
18:14:23 <pnorman> so, we suggest renaming it to nomatch to be clearer, documenting it better?
18:16:23 <zere> the documentation is... well, probably a separate task. but yes, renaming to nomatch would (for the moment) be clearer.
18:16:35 <zere> especially for anyone not running with the hstore command line args.
18:16:56 <pnorman> well documenting nomatch/hstore/whatever is in scope, since it's a new flag
18:17:44 <zere> right, but in default.style - i think it would be great to have more documentation about the style file, flags and expected behaviour, but it might be a bit much to ask for that in this PR
18:18:31 <pnorman> yes, not after an entirely new set of docs for .style files, which we do need, but just something clearer than "add tag to hstore only instead of its own column"
18:21:47 <pnorman> okay, i'll summarize it on the PR
18:27:04 <pnorman> release practices?
18:27:55 <zere> #topic osm2pgsql release practices
18:28:36 <zere> pnorman: what about the release practices did you want to talk about?
18:29:05 <pnorman> currently we do use x.y.z tagging, do dev work, advance .z, tag it, do dev work, advance .z, tag it. the problem is that this gives no indication if someone is using a released build or built from git master
18:29:36 <pnorman> should we be appending -dev, -rc1 or similar to the version?
18:31:38 <zere> the version in the configure.ac, you mean?
18:31:47 <pnorman> yes
18:35:33 <zere> yes, i guess they should... but it's a bit of a pain to have that extra commit for a revision. i suppose there's no other way to do it
18:35:55 <pnorman> i'd rather have that then try to guess from version output what they're doing :)
18:37:06 <zere> i was wondering if it would be possible to include the output of `git describe` in there somewhere
18:37:57 <pnorman> probably, i'll look into other practices
18:38:21 <zere> but then you run into problems when people `git archive` it and it doesn't have the revision information any more.
18:38:44 <zere> i think setting it manually in the configure.ac is probably the least error-prone option.
18:42:22 <pnorman> k.
18:47:05 <pnorman> AOB?
18:49:22 <zere> yup
18:49:25 <zere> #topci AoB
18:49:35 <zere> #topic AoB
18:49:43 <zere> anything else anyone wanted to discuss?
18:50:12 <pnorman> we need our budget. given we've not spent it in the past, do we want to not request anything?
18:52:25 <pnorman> I mean, I'd like to request some money to help out hack days, on the other hand, I'd guess our chance of using it is probably <10%. maybe request it anyways?
18:52:47 <zere> as i understand it, we get a "default budget" ok £1k
18:52:52 <zere> s/ok/of/
18:52:54 <pnorman> yes
18:53:13 <zere> and in the last few years we've had exactly zero people apply for funds to help out hack days
18:53:36 <pnorman> probably because we've had approximately zero people aware who were running new hack days
18:56:23 <zere> perhaps. although we tried promoting it more (https://blog.openstreetmap.org/2014/01/20/hack-weekend-december-2013/) and still had zero interest
18:57:20 <zere> i think perhaps by the time people are willing and ready to run a hack event, they're already beyond needing that sort of help.
18:57:26 <pnorman> yes
18:58:28 <zere> i'm afraid i have to go... but i'll put this on the agenda for the next meeting (jan 5th?) and we can discuss it some more
18:58:33 <pnorman> k
18:58:47 * pnorman needs to go too
18:59:09 <zere> thanks to everyone for coming. have a wonderful winter holiday & a happy new year. hope to see you on the 5th :-)
</pre>

Working Group Minutes/EWG 2014-12-12

Matt — Mon, 05 Jan 2015 17:02:20 GMT

Matt: Matt moved page Working Group Minutes/EWG 2014-12-12 to Working Group Minutes/EWG 2014-12-15: Got date wrong

#REDIRECT [[Working Group Minutes/EWG 2014-12-15]]

Working Group Minutes/EWG 2014-12-15

Matt — Mon, 05 Jan 2015 17:02:20 GMT

Matt: Matt moved page Working Group Minutes/EWG 2014-12-12 to Working Group Minutes/EWG 2014-12-15: Got date wrong

== Attendees ==

{| class="wikitable" style="font-size:0.9em;"
|-
! IRC nick
! Real name
|-
| pnorman || Paul Norman
|-
| zere || Matt Amos
|-
|}

== Summary ==

* splitting the website up
** zere outlined some ideas to an empty room

== IRC Log ==

<pre class="forcewrap">
17:35:01 <zere> minutes of the last meeting: http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2014-11-17 please let me know if anything needs changing
17:35:28 <zere> i've only got one item for the agenda tonight, which is; splitting the website up.
17:35:34 <zere> #topic splitting the website
17:36:08 <zere> the idea here is that it would be easier to run & manage services if they were smaller in scope.
17:37:07 <pnorman> yes
17:37:43 <zere> for example, the GPS track stuff is only 'joined' to the website via the users <-> gpx_files tables.
17:38:35 <zere> so (although we probably want to do this for the API at some point) it might an easier path to try it out on the GPX stuff first.
17:39:18 <zere> basically, it seems like we'd need to extract the user auth stuff into some sort of internal service, which then gets called by the API & GPX code to track sessions and/or OAuth tokens.
17:39:57 <zere> as far as i can see, we only support 3 forms of auth: cookies, OAuth & (yuvk) http basic
17:42:45 <zere> so it should be pretty easy to forward the tokens for that on to the service. the only real question is how much effort/logic is worth putting into the using services (e.g: caching, oauth verification, etc...) to save round-trips to the internal auth service.
18:19:38 <zere> there is a deafening silence. i assume that's because everyone's waiting for santa to bring them ponies? ;-)
18:33:15 <zere> hmm... okay. thanks for coming, and hope to see more next week.
</pre>

Engineering Working Group

Matt — Mon, 05 Jan 2015 17:01:56 GMT

Matt: /* 2014 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-12-22|22nd December 2014]] || || ''draft''
|-
| [[Working_Group_Minutes/EWG_2014-12-15|15th December 2014]] || splitting website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-17|17th November 2014]] || not much || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || admin, osm2pgsql, website || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}

Engineering Working Group

Matt — Mon, 22 Dec 2014 17:26:37 GMT

Matt: /* 2014 */

Matt — Mon, 17 Nov 2014 16:06:09 GMT

Matt: /* 2014 */

One of the foundation [[Working Groups]], the '''Engineering Working Group''' assists and guides the community-driven development of OSM-related source code and tools. It is recognised that there is a steep learning curve and wide set of knowledge required to develop OSM software. The primary aim of this working group is to reduce those barriers by facilitating learning and helping new developers to join and participate in the OpenStreetMap development community.

This includes:
* Running events that help developers connect with people with ideas (e.g: designers, usability experts).
* Creating and maintaining resources to lower the barrier to entry into the OSM development community.
* Guiding the development process by suggesting priorities and setting goals.
* Providing assistance for [[Engineering_Working_Group/Developer_Events|Developer Events]].

This does not include:
* Managing development resources such as servers (see [[Operations Working Group]]).
* Setting strategic direction (see [[Strategic Working Group]]).
* "Delivering" code to any time scale.
__NOTOC__

== Typical activities ==

EWG typically acts as a technical forum, and meetings generally cover areas including:

* Review of patches / PRs and discussion of how to improve them.
* Improvements to documentation and other technical information.
* Knowledge sharing and technical problem-solving.
* Gathering feedback and building consensus on technical approaches.
* Finding ways to improve our knowledge of and build motivation of new contributors.
* Helping people run developer events by giving advice and financial assistance. See [[Engineering_Working_Group/Developer_Events|Developer Events]] for more information.

== Thinking of joining? ==

Great! EWG is a completely open meeting on IRC, see [[#Meetings]] below for details. As much of the discussion is highly technical, it is highly beneficial to have a good background in programming and some experience of the OSM data model and technology stack. However, we welcome anyone who wants to help out - come along and see if it's a good fit for you.

== Who we are ==

The EWG meetings are open to anyone who wants to attend, so there is no fixed membership. Based on those who attended the most meetings, the membership list would be:

* Matt Amos
* Paul Norman
* Kai Krueger
* Shaun McDonald
* Andy Allan
* Tom Hughes
* Ian Dees
* Richard Fairhurst

== 2013 Plan ==

[[File:EWGPlan2013.pdf]]

== Contact ==

You can get in touch with members of the EWG by attending a [[#Meetings|meeting]], or by sending an email to "engineering at osmfoundation dot org".

== Meetings ==

Meetings take place most Mondays at 17:30 UTC on the OFTC IRC channel #osm-ewg ([http://wiki.openstreetmap.org/wiki/IRC Help on using IRC])

== Minutes ==

Minutes for meetings (& IRC logs) in reverse chronological order:

=== 2014 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2014-11-10|10th November 2014]] || || ''draft''
|-
| [[Working_Group_Minutes/EWG_2014-11-03|3rd November 2014]] || osm2pgsql, routingjs || ''draft''
|-
| [[Working_Group_Minutes/EWG_2014-10-06|6th October 2014]] || osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-29|29th September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-09-22|22nd September 2014]] || SOTM || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-15|15th September 2014]] || osm2pgsql docs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-08|8th September 2014]] || SOTM, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-09-01|1st September 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-08-18|18th August 2014]] || changeset comments, imagery blacklist || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-14|14th July 2014]] || API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-07-07|7th July 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-30|30th June 2014]] || API 0.7, bug reporting improvements || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-23|23rd June 2014]] || osm2pgsql, osm-carto, cgimap, API 0.7 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-16|16th June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-06-09|9th June 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-06-02|2nd June 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-05-26|26th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-19|19th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-05-12|12th May 2014]] || "big resources" || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-28|28th April 2014]] || OSM100, RANDA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-04-07|4th April 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-31|31st March 2014]] || - ||
|-
| [[Working_Group_Minutes/EWG_2014-03-24|24th March 2014]] || OWL, meeting admin || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-17|17th March 2014]] || meeting frequency || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-03-10|10th March 2014]] || DST, routing, EWG effectiveness || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-24|24th February 2014]] || hack weekend, GSoC, dev DB || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-17|17th February 2014]] || GSoC, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-10|10th February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-02-03|3rd February 2014]] || Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-27|27th January 2014]] || Routing, blogs, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-20|20th January 2014]] || Routing, Groups || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-13|13th January 2014]] || hack weekend write-up, EWG contact email || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2014-01-06|6th January 2014]] || osm2pgsql threading, hack weekend write-up || {{Accepted}}
|-
|}

=== 2013 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2013-12-16|16th December 2013]] || osm2pgsql threading, xmas || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-09|9th December 2013]] || hack events, osm2pgsql threading || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-12-02|2nd December 2013]] || hack weekend, user testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-25|25th November 2013]] || || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-18|18th November 2013]] || redesign branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-11|11th November 2013]] || no meeting || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-11-04|4th November 2013]] || code4osm, hackdays, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-28|28th October 2013]] || hackdays, time change, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-21|21st October 2013]] || EWG remit, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-14|14th October 2013]] || Hack event funding, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-10-07|7th October 2013]] || 2013 review, developer documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-30|30th September 2013]] || Switch2OSM Carto, postgis dumps || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-23|23rd September 2013]] || Hackday retention || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-16|16th September 2013]] || Trac tickets, Rails 4 || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-09-09|9th September 2013]] || JSON, issue trackers || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-19|19th August 2013]] || translations, switch2osm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-12|12th August 2013]] || welcome branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-08-05|5th August 2013]] || continuous integration, MapUI issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-29|29th July 2013]] || API latency / consistency, continuous integration || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-22|22nd July 2013]] || carto, labelling issues, merge publicity || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-15|15th July 2013]] || low zoom tiles, rails_port docs, testing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-08|8th July 2013]] || /changes deprecation, pgsnapshot cgimap backend || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-07-01|1st July 2013]] || rails_port install docs, /changes deprecation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-24|24th June 2013]] || git practices, /changes, carto, hstore || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-17|17th June 2013]] || hackday retention, notes filtering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-06-03|3rd June 2013]] || rails_port README, Carto, OWL, Routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-20|20th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-13|13th May 2013]] || rails_port README, Carto benchmarking || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-05-06|6th May 2013]] || help.osm.org i18n || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-29|29th April 2013]] || Carto style || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-22|22nd April 2013]] || osm2pgsql, READMEs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-15|15th April 2013]] || Carto style, osm2pgsql || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-08|8th April 2013]] || re-writing rails_port in Go || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-04-01|1st April 2013]] || long lines rendering issue || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-03-25|25th March 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-25|25th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-18|18th February 2013]] || 2013, role || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-02-11|11th February 2013]] || notes/bugs branch tickets || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-21|21st January 2013]] || Osm2pgsql dev || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-14|14th January 2013]] || Retrospective, development server || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2013-01-07|7th January 2013]] || Retrospective / Planning || {{Accepted}}
|-
|}

=== 2012 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| [[Working_Group_Minutes/EWG_2012-12-17|17th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-10|10th December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-12-03|3rd December 2012]] || Getting started / documentation || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-26|26th November 2012]] || Junior jobs / Getting started || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-19|19th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-12|12th November 2012]] || Notes/bugs branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-11-05|5th November 2012]] || Vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-29|29th October 2012]] || Clickable POIs and notes branch || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-22|22nd October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-15|15th October 2012]] || TTT review continued || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-10-08|8th October 2012]] || TTT review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-16|16th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-09|9th April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-04-02|2nd April 2012]] || license change, design || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-26|26th March 2012]] || license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-12|12th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-03-05|5th March 2012]] || TTTs review || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-27|27th Febuary 2012]] || UX, license change || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-20|20th Febuary 2012]] || routing, license change, coding standards || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-13|13th Febuary 2012]] || routing, license change, vector tiles || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-02-06|6th Febuary 2012]] || license change, routing || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-30|30th January 2012]] || review/catch-up, MT deputization || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-23|23rd January 2012]] || S2O || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-16|16th January 2012]] || S2O, TTTs review, patch processes || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-09|9th January 2012]] || TTTs feedback, clickable POIs || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2012-01-02|2nd January 2012]] || 2012 plan review, TTTs feedback || {{Accepted}}
|-
|}

=== 2011 ===

{| class="wikitable" style="font-size:0.9em;"
|-
!width=220px| Minutes link
!width=220px| Topics / notes
!width=50px| Draft / Approved
|-
| 26th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-12-19|19th December 2011]] || Budgeting continued: F2F, SOTM & hack weekends || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-12-12|12th December 2011]] || Incentives, budgeting, communicating TTTs || {{Accepted}}
|-
| 5th December 2011 || No meeting || -
|-
| [[Working_Group_Minutes/EWG_2011-11-28|28th November 2011]] || Further setting goals & tasks || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-21|21st November 2011]] || Board requests, setting goals & tasks. || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-14|14th November 2011]] || Rails 3 PPA, promoting hack event || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-11-07|7th November 2011]] || Blocked apps page, Communicating || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-24|24th October 2011]] || DB schemas, IRC block tile || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-17|17th October 2011]] || Rails 3, talk-de feedback || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-10|10th October 2011]] || tile usage policy || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-10-03|3rd October 2011]] || Rails 3, barriers to tile rendering || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-26|26th September 2011]] || osm2pgsql bugs, ubuntu PPA || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-19|19th September 2011]] || piwik, planet.osm.org, build farm || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-09-05|5th September 2011]] || trace categories & new bugs page || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-29|29th August 2011]] || rails port install, trac tickets, workshops || {{Accepted}}
|-
| [[Working_Group_Minutes/EWG_2011-08-22|22nd August 2011]] || Start-up meeting || {{Accepted}}
|-
|}