Tecnología Comunitaria

This page is a translated version of the page Community Tech and the translation is 23% complete.
Other languages:
Bahasa Indonesia • ‎English • ‎dansk • ‎español • ‎français

El Tecnología Comunitaria es un equipo de la Fundación Wikimedia que corre la Encuesta de Deseos de la Comunidad. Construye y mejora curación y herramientas de moderación para experimentó usuarios, apoya operadores de los bots, y más. La creación del equipo es un resultado directo de peticiones de colaboradores de núcleo. El equipo trabaja de cerca con los editores, desarrolladores de voluntario, y otro equipos de Wikimedia.

For the latest news on our projects:

Equipo


Proyectos

Próximas

En curso

Pasados

Proposal and prioritization process

The main prioritization process for the Community Tech team is the cross-project Community Wishlist Survey. It's an annual project which invites contributors from all Wikimedia wikis to propose and support the changes that they would most like to see.

The team also takes on occasional projects to help smaller groups that may not have enough support in the Survey. For a more detailed breakdown of the team's current work, check our Kanban board in Phabricator.

Scope

The team mainly works on development tasks that can be iterated on quickly and that have a direct benefit for the most active contributors who participate in the curatorial and administrative layers of the Wikimedia projects, as well as contributors who work on technical features for the projects such as templates, modules, gadgets, user scripts, and bots.

Tasks that are in scope include (but are not limited to):

  • Creating gadgets, bots, and wizards to streamline existing community workflows
  • Modifying existing gadgets and bots so that they can work across multiple projects
  • Converting heavily-used gadgets and user-scripts into MediaWiki extensions
  • Building article curation and monitoring tools for WikiProjects
  • Identifying and fixing issues with critical power-user tools that have already been developed, but are not actively maintained, such as AbuseFilter or Citation bot
  • Creating better documentation for power-user tools and features so that they can be better utilized across all projects

Tasks that are not in scope include:

  • Maintaining orphaned/abandoned projects from other WMF teams.
  • Supporting internal needs of WMF teams.
  • Large, long-term development projects like converting Commons to use structured meta-data or creating an entirely new watchlist interface.
  • Being the point of contact for all community technical requests.
  • Sysadmin type tasks such as managing Toolforge, improving site performance, creating new wikis, managing IRC channels, etc.

Collaboration

The Community Tech team has a similar mandate to Wikimedia Deutschland's Community Tech team – Technischer Communitybedarf, or TCB – which provides technical assistance and software development for the German Wikimedia community. We will be collaborating with them on projects that overlap between our teams and assisting each other with technical assessment and code review. We will also be collaborating with other WMF development teams when high-priority community requests fall within their scope. In such cases, we will work with the leaders of the other teams to negotiate timelines, expectations, priorities, and ownership. We also spend a good deal of our time working with and supporting Wikimedia volunteer developers.

Guidelines

Es importante para nosotros...

  • Trabajar en proyectos de gran impacto
  • Ayudar los Wikis grandes y pequeños, en muchos idiomas
  • Estar abierto y comunicativo
  • Estar responsivo a las solicitudes y preocupaciones de todos
  • Estar tranquilidad y civilizado, y asumir de buena fe

We're a small team, and there's a lot to do! We want to be as helpful and effective as we can, so we can't take everything on. Saying no to requests that we can't help with is an important part of our job, because it frees up time and energy for the requests that we can help with.

But "no" is hard to hear sometimes, so here are some guidelines about working and communicating with the Community Tech team.

  • Please be calm and civil, and assume good faith on our part. We care about the projects too.
  • Nos encantan nuestros trabajos y trabajamos duro, pero no trabajamos 24/7, y no podemos garantizar una respuesta inmediata.
  • Si una persona concreta o asunto está tomando un porcentaje sobredimensionado de nuestro tiempo en el wiki, aquello toma tiempo y atención fuera de otras personas. A veces tendremos que cerrar una conversación, y decir que no podemos gastar más tiempo en un tema particular.
  • We can't take on projects that are currently on another product team's roadmap, or a project that directly conflicts with another team's work.
  • If there's an issue with another product team's work, we can direct you to the appropriate person to talk to.
  • We can't answer questions about staffing issues, or confidential matters.

The Community Tech team is committed to upholding the civility standards set by the Terms of Use and will observe and maintain the friendly space expectations for Grants spaces in our interactions. We ask that all contributors to Community Tech spaces do the same.

Links