4 engineers
← Older revision
Revision as of 07:54, 7 March 2014
(One intermediate revision by the same user not shown)
Line 9:
Line 9:
* Supporting the OpenStreetMap community
* Supporting the OpenStreetMap community
* Supporting an OSM Database for developers
* Supporting an OSM Database for developers
−
* Production tileset service
+
* Production tile-set service
* Supporting existing Geo tools
* Supporting existing Geo tools
* Increasing the amount of maps use and creation on Wikipedia
* Increasing the amount of maps use and creation on Wikipedia
Line 24:
Line 24:
= Team =
= Team =
To remedy this I propose building a Maps and Geo team incubated within the Mobile Department that would have 4x engineers, 1x operations staff member, 1x community liaison, and 1x product manager. These roles may live within mobile or be matrixed into mobile if they are 100% dedicated to Maps and Geo work. This engineering team would live within Mobile as they would work very closely with the Mobile Web & App teams at first in order support their initial product work but would serve as an infrastructure team that would eventually build maps and geo functional for the organization at large across handset, tablet, and desktop. The mobile team has expressed the most amount of interest and drive for this work and the department is in a good place to absorb additional growth due to its Agile practices.
To remedy this I propose building a Maps and Geo team incubated within the Mobile Department that would have 4x engineers, 1x operations staff member, 1x community liaison, and 1x product manager. These roles may live within mobile or be matrixed into mobile if they are 100% dedicated to Maps and Geo work. This engineering team would live within Mobile as they would work very closely with the Mobile Web & App teams at first in order support their initial product work but would serve as an infrastructure team that would eventually build maps and geo functional for the organization at large across handset, tablet, and desktop. The mobile team has expressed the most amount of interest and drive for this work and the department is in a good place to absorb additional growth due to its Agile practices.
−
+
+
== Scenarios ==
+
=== 2 Engineers ===
+
Given a staffing of two engineers the team would focus on
+
+
* Building and supporting a production tile service that supports Mobile Apps & Community Development
+
* Take *some* action on maps and geo technical debt
+
** Update [http://tools.wmflabs.org/geohack/geohack.php geohack] to function within Wikipedia rather then a third part site
+
** Update [http://meta.wikimedia.org/wiki/WikiMiniAtlas/en WikiMiniAtlas] to be supported by internal tile service
+
*** Currently maps are slow and don't even load consistently
+
** Update synthetic maps like [https://en.m.wikipedia.org/wiki/San_francisco#/image/File:California_county_map_(San_Francisco_County_enlarged).svg File:California_county_map] to be easily creatable
+
* Build and support storage for tile service
+
* Supporting an OSM Database for tool server developers
+
+
=== 4 engineers ===
+
+
* Create custom tile sets in collaboration with [https://www.mapbox.com/ MapBox] and [http://stamen.com/ Stamen design]
+
* Creating navigable maps within Articles using tile rendering service
+
* Create a map and location based navigation model for Wikipedia to augment search
+
* Work with WMF engineering teams like Mobile and Multimedia to extend Maps and Geo functionality
+
* Collaborate with [http://wikimaps.wikimedia.fi/ Wikimaps project] to easily allow spatial map creation
+
* Create workflows to add GPS coordinates for articles that don't have them
+
* Evolve Special:Nearyby by for desktop and mobile users
+
* Increasing the amount of Wikidata contributions
+
* Increasing the amount of GEO-tagged coordinates in the [http://www.oii.ox.ac.uk/vis/?id=4f7b30eb Global South]
+
= Outcome =
= Outcome =
As our mobile page-views continue to climb Wikipedia will be more and more present within the physical world. Not having maps will create an inferior product that doesn’t deliver the rich educational experience that we need to be showing. Instead we should focus our efforts at staffing this initiative and pairing it across Mobile, Multimedia, and others in order to capture the wealth of contributions and use that this will have.
As our mobile page-views continue to climb Wikipedia will be more and more present within the physical world. Not having maps will create an inferior product that doesn’t deliver the rich educational experience that we need to be showing. Instead we should focus our efforts at staffing this initiative and pairing it across Mobile, Multimedia, and others in order to capture the wealth of contributions and use that this will have.