WordPress Community summit 2017 – representation and Polyglots topics

WordPress Community summit 2017 – representation and Polyglots topics

For those of you unfamiliar with the concept, the community summit is a global gathering of contributors from all make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ teams from all over the world for a few days of discussions and coworking on topics that are closely related to the future of WordPress.

This year’s community summit will be in Paris on June 13-14, before WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. (June 15) and WordCamp Europe 2017 (June 16-17). The previous community summits were in the US – Philadelphia in 2015 and San Francisco in 2014. The first ever community summit was in 2012 in Tybee, GA.

Polyglots representatives and topics for the 2017 community summit

A couple of weeks ago the Community team posted about the 2017 community summit and requested all teams to step up with a couple of things:

  1. A list of topics/issues which are relevant for the progress of the team and the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project as a whole, prioritizing topics or tasks which are sensitive enough to specifically require in-person discussion.
  2. A list of representatives to attend the Community Summit (not limit-determined, but please keep in mind that our venue capacity limit is of 190 attendees), with selections based on several factors, including: representation of a wide, diverse range of opinions (based on the agreed-upon topics selected by each team), diversity, inclusion, and activity of the contributors.
  3. One or two contributors who are willing to help with the organization of the event: posts, communication, travel assistance, finding sponsors, etc. The intention of this approach is to propose a more open and team-focused Community Summit with transparent participation from all active contributors and reps of each team. This way we can hopefully anticipate barriers and cross-team difficulties that might come up, and avoid them.

Representatives

Every LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ manager/General Translation EditorGeneral Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale. who is interested in going to the community summit can step up and volunteer/nominate themselves. Don’t be shy to step up to represent the team – it doesn’t matter how involved you have been with meetings or discussions so far. If you have opinions and are willing to help with some of the topics listed below, you would be a great asset during the community summit.

Topics

After discussing things during weekly chats for a couple of weeks, this is the official post where you can nominate yourself or a fellow contributor to represent the team during the community summit and you can comment on the topics that we have singled out for the two day event:

Topics related to the Polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. working with the community team

  • Increase outreach (RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. sites outreach, jump starting and upgrading our locale sites to best fit the community)
  • Organise local contributor days

Topics related to the team working with the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team

  • Improvement of translation and communication tools 2.0 (we’ve already got the first phase of this going with the O2s, GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. improvements, etc).
  • Cross locale PTEs implementation discussions and
    brainstorming ways of getting rid of the current bottleneck of improving pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/theme translations

Polyglots Processes

  • New General Translation EditorsTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles: General Translation Editor and Project Translation Editor onboarding/ Mentorship program
  • New translation contributors onboarding
  • Handbook review / updates

Polyglots Leadership team growth plan

  • We need more people representing different regions to get involved
  • A plan to attract and keep them
  • Grow the communication side of the polyglots leadership team
  • Grow the technical side of the leadership team

Volunteers to help organise the community summit

If you would like to help the organising team of the community summit, please put your name forward. Tasks expected from volunteers would include posts, communication, travel assistance, finding sponsors, etc. but at this point, we don’t know many details.

Please get involved with this as this is a chance for our team to single out the important issues we currently have and to brainstorm and find solutions for them. We need as many people as possible to give an opinion on topics and even if you can’t make it to the event, your position is valuable and will be taken into consideration.

Thank you!

Petya

#community-summit, #community-summit-2017

Topic discussions for the Community summit in Philly

Hey everyone,

The community summit in Philly is two weeks away and it would be good to create a list of topics we’d like to be discussed during the two days of the event.

For those of you who don’t know about the summit, visit the website to learn about it and ask any questions you might have in the comments below.

The community summit last year in San Francisco included 2 days of intense work and meetings, you can read the notes from some of the discussions – GlotPress, Leads, Rosetta.

The current list of Polyglots for Philly confirmed by the organisers includes myself, @Nao, @tacoverdo, @atimmer, @francescamarano, @hiwhatsup, @rafaelfunchal, @stephdau and Rocio (@_dorsvenabili).

The community summit is a good place for us to interact with the other make teams, especially the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team and the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, but also to collaborate with the docs team and plan the improvements we’d like to see in the year to follow.

It would be amazing to have the most active of you on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. during those two days so that you can at least partially participate in the discussions.

Here’s what’s on my list. Please add the ideas you have and we can form discussion topics to suggest for the unconference days.

RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. sites

To Do

  • P2s for Rosetta sites for community and translation teams. There’s a pilot one on the de.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ site, but it’s time we bring that to the rest of the localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ sites
  • Outreach campaign to encourage more people to get involved with updating their Rosetta sites. With the new user roles coming, there’s no reason more editors can’t be recruited so that the sites are always up to date with new information on the latest releases as well as community events information. See the Romanian and Italian sites as examples.

Discussion topic suggestion:

  • Improving Rosetta sites – the tools we need

Translate.WordPress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.

Three main things as a focus here to discuss, get a status update on or plan:

  • Translation memory
  • Notifications for translation editorsTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles: General Translation Editor and Project Translation Editor
  • Feedback to contributors (edit with feedback, reject with feedback)
  • Glossaries across projects

Discussion topic suggestion:

Documentation

To Do

  • Improving documentation for pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party authors regarding their plugins on translate.wordpress.org
  • Improving the Polyglots handbook – there are still pages that need expanding, more information, screenshots.

Discussion topic suggestion:

  • Translating contributor handbooks – can we translate the handbooks to make it easier for new contributors? How?
  • Translating WordPress Documentation – tools, ways, etc.

Please add your suggestions and comments.

#community-summit, #discussion, #polyglots, #wcus

Notes from the GlotPress discussion at #WCSF Community summit

Notes from the discussion on improving GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. (Mon, Oct 29th), suggested by Marko for the Community Summit in San Francisco.

Participants

Birgit Olzem, Catia Kitahara, George Stephanis, Mayo Moriyama, Marko Heijnen, Paolo Belcastro, Petya Raykovska, Rafael Funchal, Sam Sidler, Stephane Daury, Xavier Borderie.

If you were there and I missed your name, please leave a comment.

Continue reading

#community-summit, #discussion, #glotpress, #notes

Polyglots leads discussion and selection – WP Community Summit

Polyglots leads discussion

Leading the polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. isn’t an easy task. Lots of cultures, a lot of diversity. Understanding everyone can be hard. There have been issues in the past with specific communities using their sites to make money, some using it for WordPress, some not. Part of this is cultural, part of it is ignorance, part is just bad performance. Varies from culture and site.

In light of that, we created a set of expectations for RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. sites. Part of leading polyglots is making sure sites meet these expectations.

Process for handling bad content on Rosetta sites

  • Email the validators of the site (request a response within a week)
  • After a week, email again (“You have 3 days to take care of this”)
  • After three days, email again (“You have 24 hours to clear this or we remove it”)
  • If the content is not removed within 24 hours, login as administrator and remove bad content.
  • Email validators and say if the content comes back without fixing its problems, they will be removed as validators/editors.
  • Check site regularly to ensure the content doesn’t come back.
  • When at all possible, we want validators to be responsive. If they aren’t, that can be an issue.
  • Note that just because a validatorValidator See translation editor. is unresponsive, that doesn’t mean they are bad actors. It’s possible for life to get in the way for days, weeks, or months.

Finding new validators

  • We are going to need more validators as plugins and themes become translatable. A good target is likely 20 active validators per language by mid-2015.
  • That’s a problem across the community and we need good coordinators for different regions to mentor new validators.
  • We also need to add new languages, which will need good validators. Mentoring them will be important so they can grow fast.

Things that will help with new translators/validators:

  • Having better documentation
    • Translator handbook
    • Per language guidelines for translation
    • Glossary for every language
  • Better contributor recognition
  • Roles: separate roles for translations vs the local community stuff (Rosetta administration, support, blog, forum moderation)
  • Separate the role of the editor from the validator so validators can focus on translation and mentoring new validators

Leads

As Polyglots will get more and more busy following themes and plugins in the repositoryWordPress Localization Repository The WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details., there will be a need for more coordination and help to all the new validators. This can be accomplished by splitting localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ into different regions and appointing multiple leads for each region. Separating the locales will be done geographically first and then by language so that there is no overload for any of the leads.

Proposed regions:

Region 1: Asia & Oceania: Central Asia, South Asia, East Asia, and Oceania. Perhaps does *not* include Australia / New Zealand English, but does include any future local languages. Does not include Russia or Iran. Currently, ~51 locales.

Region 2: Europe (including Turkey, Russia), Africa (entire continent), Middle East (includes Iran). Currently, ~70 locales.

Region 3: North, Central, South America, and the Caribbean. Perhaps includes Australia / New Zealand English. Also includes engineered languages (Esperanto, Klingon, Ido). Currently, ~16 locales.

Part of the goal for these regions is to have them within a reasonable timezone of each other to make coordination easier. Part of the goal is to have “similar” languages together (like the English languages).

What is a lead?

A lead is not simply a copy of Zé. We’ll all get burnt out if we try and emulate everything he did. There’s a lot of responsibilities. Let’s split the role into two.

As the role is pretty extensive, it is best for it to be split into two separate lead roles:

“Community” leads

Essentially, this role is non-technical and involves working with people. Here’s a list of a lot of responsibilities included in this role. (There may be more!)

  • Review and answer “people”-based P2p2 "p2" is the name of the theme that blogs at make.wordpress.org use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog https://make.wordpress.org/polyglots/. comments and requests
  • Answer requests for new locals (research and approve, especially using Ethnologue)
  • Weekly meetings (organize, take notes, post updates on how locales are doing)
  • Moderate disputes between validators/translators
  • Mentorships – Connect validators with other validators who can help and give pointers.
  • Validators – find and approve validators; communicate with current validators
  • Interface with the community team
  • Interface with legal (as a result of Rosetta contacts)
  • Review Rosetta sites to ensure they meet expectations
  • Contact validators if a Rosetta site does not meet expectations and work to get them fixed.
  • Write and maintain documentation
  • Create and maintain policies (like the Rosetta expectations; new things may be needed in the future)
  • Compile and post stats (on the P2)
  • Generally, find people to do things

“Technical” leads

Technical leads are responsible for doing everything needed technically. Here’s a list of things that they may need to do:

  • Answer technical questions on the P2 (deployment, other related things)
  • DeployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. Rosetta, including forums and P2s when those exist again.
  • Create locales (after community lead approves)
  • GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. – interface with the GlotPress team, including discussing future needs and helping implement those needs where applicable.
  • Interface with the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team about upcoming core changes
  • Interface with the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team about necessary wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ changes.
  • Work on technical problems that local translations have
  • Create and compile stats (with community leads)
  • Write and maintain technical documentation

How do we find/appoint leads?

Everyone here (at the community summit) should be considered a “lead” in the WordPress community. Maybe we shouldn’t have one or two leads, but instead form a leadership team with everyone here who’s interested. The leadership team can work together to ensure no one gets burnt out and that no knowledge gets lost along the way. Today, a leadership team is formed.

Moving forward, we should look at who wants to be community-focused and who wants to be technically-focused. We have good coverage for community-focused, but we’ll need to bring in people to be technically-focused. We also have great timezone coverage!

Over time, we should consider having regional leads for each of the three regions described above, both for community and technical sides. (This means a total of six “leads.”)

Weekly Polyglot meetings

First things first, we need to start a weekly meeting.

  • Ideally two or three meetings a week, 8-12 hours apart. Same agenda, but this allows people from different timezones to participate.
  • Let’s make a Doodle for choosing the time for weekly meetings.
  • Use this meeting to help new validators / translators with questions.
  • Also get stats from localizers. How are teams doing? What progress are they making? Is a team almost there? How do we get them to 100%?
  • Meetings should be held in #polyglots channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
  • Notes from the first meeting of the day can be posted to the P2 in draft form. Other note-takers can update after their meeting. Last meeting of the day publishes post.

Contributor Recognition

To start, we need to improve the badges on dot org profiles. How about three polyglots badges?

  • A badge for members of the polyglots leadership team
  • Badge for validators/editors. Potentially use this for moderators too, though can’t they get a support badge?
  • Translators (anyone who’s translated a stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. and had it approved) get a third badge.

Final notes / actions

  • Update Handbook
    • Add handbook page with leadership team (including dot org usernames) so people can reach out and get advice.
    • Include timezone information so you can find a local lead.
    • Add a map (image map!) that shows what the regions are and who can help you in your region.
    • Add a list of regions (non-graphic) as well.
  • Talk to support team (Mika) about getting badges for moderators
  • Start holding weekly meetings
  • Find technical leads in each region
  • Document Zé (and all that he did)

Participants

The following people attended this meeting at the WordPress Community Summit: Andrew dela Serna (Philippines), Birgit Olzem (Germany), Catia Kitahara (Brazil), Marko Heijnen (The Netherlands), Mayuko Moriyama (Japan), Petya Raykovska (Bulgaria), Shinichi Nishikawa (Japan), Sam Sidler (USA, wordpress.org), Takayuki Miyauchi (Japan), Xavier Borderier (France).

#community-summit

Notes from the Rosetta sites discussion at #WCSF Community Summit

Hey everyone,

As you already know last week following WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. San Francisco there was a Community Summit followed by two contributor days to give Make teams the chance to work together and discuss important subjects.

In the next couple of days I will be posting my notes from all of the discussions and meetings we had so all of you are up to date with what’s been said and done.

Starting right now with the first discussion of the Community summit, suggested by Xavier.

Who was there: Andy Christian, Andrew dela Serna, Birgit Olzem, Catia Kitahara, Konstantin Obenland, Marko Heijnen, Mayuko Moriyama, Petya Raykovska,Rafael Funchal, Sam Sidler, Xavier Borderier,

RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. sites and Local Communities

We tried to see what different local communities are doing with their local sites and mark what improvements are needed for Rosetta sites to enable communities to grow.

Right now a lot of the more active communities just use their Rosetta sites for downloads of the localised WordPress version because of all of the limitations. Rosetta administrators/editors and validators get access to approve stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. for local translations but can’t actually change the website, just add pages, write blog posts and releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. translations.

We discussed different tools Rosetta sites need to be a viable tool for local communities: 

Desired Rosetta extensions

What kind of extensions do communities need for Rosetta: 

  • A public feed aggregator (aka “planet”)
  • Event calendar / community events
  • Job board
  • Documentation (to replace Codex and work with developer.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/)
  • Community map
  • Team list – can be public or not
  • Local community pages (P2s)
  • Widgets for homepage

External Community websites

Some communities have put a lot of work and effort into external community websites because they can not extend Rosetta sites. Some examples are Germany, France, and Portugal.

No community will be forced to move back to the local Rosetta site, but an effort can be made to provide more tools and options for Rosetta sites so communities are actually willing to move back. 

If that becomes the case, there needs to be an easy way to transfer the existing content or at least have a plan on what will be done with the external sites so all of that content is not lost, perhaps by archiving.

Check how it works for most of the active communities:

  • How should current community sites be integrated?
  • What different user roles will be needed in order to facilitate adding 20+ more validators per localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/?
  • How can migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of community sites happen?
  • There has to be a plan for if you want to move your site. Let’s check if .org can host it.

With the plans of themes and plugins being localized, each locale will probably need at least 20 validators in the future (with plugins and themes in there).

User roles

With themes and plugins coming, there will need to be some more user roles for Rosetta sites and probably some clear separation between translators and community leads. 

A new “super validatorValidator See translation editor.” role (name-pending) will be needed to ensure quality of the translations for the top projects (WordPress and the projects that are already in GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. plus the top 25 plugins and themes).

And the project will need to bring in a lot more validators to be able to handle translating plugins and themes. 

A super validator will be needed for adding validators and removing validators that are not performing well. We need to be more sensitive about this thing. Translators need to be trusted.

Consider the forums for the localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ that want it. Consider P2s and news blogs. We need to consider all of the features that are needed and then pick up roles that make sense.

Expectations for external links and Showcases on Rosetta sites:

  • Showcase:
    • Validators cannot have their websites in the showcase.
    • Community sites are generally not allowed in showcases, because they’re linked to elsewhere on the site.
    • Explicit sites are not allow in showcases.
  • Community Sites (when linked to from Rosetta sites):
    • Must have a prominent link back to the relevant Rosetta site (e.g., bg.wordpress.org).
    • Cannot have advertising on them. One exception is that we allow a “hosted by” graphic/link if a company is sponsoring the community site (but no money can exchange hands).
    • Donate links are not allowed unless they go to the WordPress Foundation.
  • Advertising is not allowed on Rosetta sites, including advertisements for hosts, validators, translators, or other forms of advertising. Sites are allowed to list validators and translators with links to the blogs on a separate page (say, “About”).
  • Private information (phone numbers, email addresses) is not allowed on Rosetta sites.

#community-summit, #external-community-sites, #local-sites, #rosetta