Wikimedia Engineering/Report/2014/January/summary/es


 * Este contenido se prepara para incluirlo en el Informe de la Fundación Wikimedia de enero del 2014. Es una versión más corta y sencilla del Informe de ingeniería de Wikimedia de enero del 2014 que no requiere conocimientos técnicos especializados.

Las noticias más importantes de enero son:
 * la transición de nuestros buscadores en los sitios de Wikimedia a ElasticSearch;
 * una presentación sobre cómo funcionan las Noticias Tech, incluyendo una perspectiva histórica;
 * una invitación a comentar los 2 años de visión del equipo de ingeniería de multimedia;
 * una petición de comentarios sobre si el formato de vídeo MP4 debería funcionar en los sitios de Wikimedia.

VisualEditor
En enero el equipo de VisualEditor continuó su trabajo en la mejora de la estabilidad y del rendimiento de esta interfaz para la edición de páginas tanto en Wikipedia como en sus hermanas. También se añadieron nuevas funciones. Ahora es posible editar ajustes de página como si se quiere ver una tabla de contenidos o se quiere mostrar etiquetas de edición de sección. También se puede especificar manualmente el tamaño de un archivo multimedia, ver una lista de teclas de acceso rápido, crear y editar galerias multimedia usando un editor sustituto muy básico mientras se diseña la forma final. Asímismo se continuó el trabajo en un cuadro de diálogo para añadir rápidamente referencias a "citas" que se basa en plantillas, más media y ajustes de página, la configuración del idioma del contenido y de los indicadores de derecha a izquierda, y la edición de ecuaciones.

The Parsoid team (developing the program that converts wikitext to annotated HTML, behind the scenes of VisualEditor) did a lot of bug fixing around images, links, references and various other areas. We also mentored students, participated in discussions relating to the architecture of MediaWiki, and started to work on "packaging" Parsoid to make it easier to install.

Editor engagement
This month, the Core Features team worked on integrating MediaWiki tools for dealing with spam and vandalism (AbuseFilter and Spam Blacklist) into Flow, a new wiki discussion system. We also launched an updated visual design and user interface for Flow, based on the first round of experienced user feedback last month, as well as ongoing user testing with new users. Lastly, we created a script to disable Flow and convert its content, so that we can begin testing Flow on two WikiProjects that volunteered on the English Wikipedia while being able to revert to wikitext if needed.

The Growth team improved the GettingStarted extension, in part to support local configuration for different Wikipedias. The latest version of GettingStarted and GuidedTour will be released in English and 23 other languages in early February. The team also completed several iterations of design and data analysis in support of upcoming work on Wikipedia article creation. We presented new designs for the Draft namespace, and completed a series of remote usability tests. We also finalized and published extensive quantitative analysis of trends in article creation across the largest Wikipedias.

Mobile
During the last month, the Wikipedia Zero team worked on supporting secure HTTPS connections for partners in the Zero program, which allows mobile subscribers to access Wikipedia content at no data cost. We also continued to work on a proof of concept HTML5 web app for Firefox OS, fixed bugs in the legacy Firefox OS Wikipedia app, and prepared alpha functionality for the integration of Wikipedia Zero with the rebooted Android Wikipedia app. The team also met with the business development team to plan for partners and Wikipedia Zero-related work at large, and conducted tech facilitation to enable partner launches and align approaches with current and future partners.

The Mobile web projects team has been directing much of their attention over the last month at delivering a tablet-friendly mobile experience. We've added support for tables of contents, made some design improvements, and have worked towards making VisualEditor work on tablets (in alpha for now). We have also released our overlay UI improvements as well as an improved inline diff view for MobileFrontend into stable. Finally, we have also been working to expand our coverage of browser tests to facilitate quality assurance and help prevent the introduction of bugs and regressions.