Contribuer au cœur WordPress / Partie 2 : créer un patch avec GIT

Cet article est le second d’une série dédiée à la contribution au cœur WordPress. Aujourd’hui, l’objectif est d’expliquer comment créer un patch pour proposer un correctif ou une amélioration dans le cœur WordPress.

Voir l’article précédent : comprendre le fonctionnement de Trac, l’outil de ticket de WordPress.

Continuer la lecture « Contribuer au cœur WordPress / Partie 2 : créer un patch avec GIT »

Contribuer au cœur WordPress / Partie 1 : Trac, le gestionnaire de tickets utilisé par WP

En tant que logiciel open-source, WordPress a besoin de contributeurs et contributrices. Des personnes de tous les pays du monde contribuent à ce projet, et dans une volonté de développer cette culture de la contribution dans la communauté WordPress francophone, nous lançons une série d’articles/tutoriels sur le sujet.

In open source, we feel strongly that to really do something well, you have to get a lot of people involved.

Linus Torvalds

Cet article est le premier d’une série dédiée à la contribution au cœur WordPress. Aujourd’hui, l’objectif est de donner les pistes et liens permettant de trouver des tickets « simples » à corriger afin de pouvoir se lancer dans le grand bain de la contribution au CMS qui propulse plus de 30% du web.

Continuer la lecture « Contribuer au cœur WordPress / Partie 1 : Trac, le gestionnaire de tickets utilisé par WP »

CLPTE prerequired actions

WordPress Devs who wish to have CLPTE access to your products (themes, plugins) here are the guidelines to provide to your French translators.

In order to assure the best possible quality for all translations (and therefore for the products you so dearly worked on), we have established a few rules your French team members should follow:

  1. We follow the WordPress meta handbook for translations recommendations. Your translators should speak French.
  2. They should follow these steps:
Continuer la lecture « CLPTE prerequired actions »

How French Community handles PTE Requests

Following the path of some other locales, here are the guidelines for all WordPress Devs who wish to have their products (themes, plugins) localized in French, to give it a wider chance to be adopted by French users.

In order to assure the best possible quality for all translations (and therefore for the products you so dearly worked on), we have established a few rules to grant you PTE (Project Translator Editor) status for your product(s):

  1. If YOU want to become PTE, we follow the WordPress meta handbook for translations recommendations. We’ll not accept such a request if you don’t speak French.
  2. If you don’t speak French and will have a TRANSLATOR working on your product, please have them work on the WP translate platform
  3. You should all follow these steps (either YOU, the Dev, or the Translator):
  • Get yourselves (again, you AND/OR the translator – both would be best for perfect communication) on the French Slack Community, channel #traductions.
  • Read the Guide de Traduction;
  • Translate as a Contributor;
  • A PTE will review the translations;
  • A PTE or a GTE (General Translator Editor) will give you (or translator) the opportune feedback;
  • If the quality of the translation is up to the standards we all try to follow (remember, a poor translation is as bad for your product as it is for the entire WP ecosystem) You (or your Translator) will be granted PTE authority.

WHY WE FOLLOW THESE GUIDELINES?

  • We strive at perfection: we aim at having the best possible localization for all products in the WP ecosystem. And that requires that all translations are done in the best possible way.
  • It helps us create a community of French translators that know each other, and that can support each other when needed.
  • We think globally, and aim at consistency.
  • It streamlines and optimizes the process, reducing the amount of «unproper» translations and, by default, the time spent on rejecting and revising translations. (Thus allowing more time to be devoted to the actual localizing).

It is not different as what happens on GitHub, where access is not given directly to original code, but allowed through Forks and Pull Requests (just to give you a metaphor that’s might be closer to your approach).

We do feel you can understand that these rules are meant to give You the best possible localization for your product(s), and to give the entire WP community a better UX, a stronger platform and a healthier ecosystem to work on.

We hope everything is clear. If not, you can always catch us on Slack to discuss this further. Happy coding!