Office Hours Recap (September 6)

The office hours are held every Tuesday at 17:00 UTC in the #glotpress channel of the WordPress Slack team.

Log: https://wordpress.slack.com/archives/glotpress/p1473181218000016
Attendees: @gregross, @swissspidy, @samuelsidler, @sergey, @petya, @ocean90

Notes

  • Office hours are starting again. @ocean90 is back from his job as Release Lead for WordPress.
  • @gregross mentioned that 2.2 has been pushed a couple of times so a new release date is needed.
  • The milestone for 2.2 has been reviewed:
    • Focus of 2.2: An improved scripts/styles handling and some other bug fixes.
    • Global glossaries require more discussion and have been punted.
    • Low prio schema changes have been punted.
    • @gregross has worked on a PR for an uninstall routine.
      • The idea remains in the milestone but the PR needs some improvements like OOP.
    • A new schedule for 2.2 has been defined:
      • September 14th, 2016 Beta 1
      • September 21st, 2016 RC 1
      • September 28th, 2016 Final
  • For the next releases @ocean90 proposed to try 2 month cycles. Each release should have one focus on which all contributors can work on.
  • A possible roadmap defines such focuses:
  • The reason why design is after the REST API: An UI (React, AngularJS, etc) which is powered by the REST API. 💥 Goals would be to enhance mobile experience and less page reloads.
  • It was mentioned that the ‘Tested up to’ for GlotPress needs to be updated on https://wordpress.org/plugins/glotpress/.
  • The old GlotPress Trac is now read-only. All development happens on the GitHub repo.
  • @petya will talk to Marko about https://twitter.com/glotpress so the team can use it.

 

If you couldn’t attend the office hours, feel free to leave a comment here or in #glotpress and let us know what you think about some of topics or if you’d like to see something else discussed.

See you next week!

#glotpress, #office-hours

GlotPress 2.1 “Camilla”

GlotPress Icon

After 3 months we’re pleased to announce the third release of GlotPress as a WordPress plugin.

Version 2.1 of GlotPress, named “Camilla“, is now available for download or update in your WordPress dashboard.

The focus of this release was to improve the database performance and other general enhancements.

Highlights of this release:

  • To increase transparency the user ID of a validator is now stored on translation status changes. You can now see who approved (or rejected 😱) a translation.
  • The permissions list has been updated to use a table view. Gone are the days where you have had to search for users in a tiny list.
  • Imported translations are now checked for warnings too.
  • You have translations which still still a review? Now you import translations with status waiting.
  • PO exports now include a Language header and a Project-Id-Version to improve handling of sub projects.
  • Multiple changes to the database schema to provide the fastest GlotPress so far.
  • Want to know more? Read the full changelog here.

Contributors of this release: Dominik Schilling, Greg Ross, Yoav Farhi, Alexander Kirk, Anton Timmermans, Mattias Tengblad.

If you want to follow along or help out, check out our repository on GitHub.

#release, #wordpress-plugin

GlotPress 2.1 RC 1

The first release candidate of GlotPress 2.1.0 is now available!

This software is still in development. Consider setting up a test site just to play with the new version.

The release candidate can be downloaded from GitHub.

Changes since Beta 1:

  • Allow project slugs to contain periods. (#492)
  • Add confirmation message when saving settings. (#490)
  • Convert sort by fields from hard coded to a filterable function call. (#488)

For more of what’s new in version 2.1, check out the Beta 1 blog post.

If you think you’ve found a bug, you can post to the issue tracker on GitHub.

The final release is targeted for July 13, 2016.

Happy testing!

#488, #490, #492, #development, #release, #wordpress-plugin

GlotPress at the WordCamp Europe Contributor Day 2016

This is a recap of the work done at the Contributor Day of WordCamp Europe 2016 in Vienna by the team that had signed up to work on GlotPress:

Team GlotPress (including Alex Kirk, Hugo Fernandes and Isaac Keyet) worked on continuing Isaac’s efforts to explore a new design for GlotPress. We conducted user interviews to find out how to improve the current experience. It showed that it is hard to draw the line between GlotPress and translate.wordpress.org and to decide where a new feature would need to go.

We therefore assumed GlotPress in the context of translate.wordpress.org and collected potential new features as well as feature changes on pieces of paper and prioritized them based on the desirability (i.e. value vs. effort required). Mind that our selection is the result of our brainstorming process and quite possibly needs some more refinement:

Everyone (User group = beneficiary)

  • Filters more visible (search box)
  • Better Glossary (global)
  • string timeline (history, status changes)

Visitors

  • Simplified translation experience for new users (maybe a step by step tutorial, incl. signup: “make visitors translators”)
  • Make some legends more visible/useful

Translators

  • “Minor edit” approve with original translator credit
  • Feedback when rejecting a request
  • Notify users of approvement/changes
  • Showing who approves/rejects

PTEs

  • Github-style labelling (mostly freeform) ~= tagging

GTEs

  • Easier way to promote translators to editors (reverse the current flow: translators can request to become a PTE after a certain number of approved strings)

Feel free to chime in on our selection and help us convert feature ideas to a GlotPress-only context and create issues accordingly on the GlotPress Github repo. Thanks!

GlotPress 2.1 Beta 1

The first beta of GlotPress 2.1.0 is now available!

This software is still in development. Consider setting up a test site just to play with the new version.

The beta can be downloaded from GitHub.

The focus of this release is performance improvements and other general enhancements.

Bugs fixed in this release:

  • Replace LIKE queries for the status of an original with an exact match. (#419)
  • Move gp_translation_set_filters hook to allow additions to the filter form. (#391)
  • Fix wrong error message for translations with a missing set ID. (#341)
  • Fix Android exports with translation that start with an @. (#469)
  • Improve performance of default GP_Translation->for_translation() query. (#376)
  • Use __DIR__ constant for GP_PATH. (#455)
  • Use lowercase field types in schema.php. (#461)
  • Change field type for user IDs to bigint(20). (#464)
  • Don’t call gp_upgrade_data() in gp_upgrade_db() on install. (#361)
  • Define max index length for user_id_action column. (#462)

Features in this release:

  • Allow export by priority of originals. (#405)
  • Check imported translations for warnings. (#401)
  • Allow translations to be imported with status waiting. (#377)
  • Add Language header to PO exports. (#428)
  • Add option to overwrite existing glossary when importing. (#395)
  • Allow modification of accepted HTTP methods in the router. (#393)
  • Update the Project-Id-Version header PO exports to better handle sub projects and be filterable. (#442)
  • Convert the permissions list to a table. (#99)
  • Split translation status counts by hidden and public. (#397)
  • Store user ID of validator/approver on translation status changes. (#293)

In this version 28 issues were solved and 26 Pull Requests were merged, a total of 89 commits.

Contributors of this release: Dominik Schilling, Greg Ross, Yoav Farhi, Alexander Kirk, Anton Timmermans, Mattias Tengblad.

If you think you’ve found a bug, you can post to the issue tracker on GitHub.

The next release (RC1) is targeted for July 6, 2016.

Happy testing!

#293, #341, #361, #376, #377, #391, #393, #395, #397, #401, #405, #419, #428, #442, #455, #461, #462, #464, #469, #development, #release, #wordpress-plugin

Exploring Design for GlotPress

Many of you probably know @isaackeyet from his contributions to translate.wordpress.org as well as work on the WordPress mobile apps. Well, he’s back again to contribute some new designs to the GlotPress plugin.

As part of the design process, Isaac wants to hear from translators and validators alike. What makes a translation interface good? Every person that reads this post (you!) can participate. You don’t have to be a designer!

It only takes five minutes to help. Here’s how:

  • Use whatever medium you’d like (paper, pen, computer).
  • Sketch out your ideal translation interface. Try not to think about specific features. You don’t need to be an artist. Rough sketches are helpful too!
  • Post your picture as a comment here.

That’s it! Lots of contributions mean lots of inspiration as Isaac designs the future of GlotPress.

Thank you for your help!

#design

GlotPress 2.0.1

GlotPress IconGlotPress 2.0.1 is now available for download or update in your WordPress dashboard!

This is a bugfix release addressing issues found in version 2.0.

Bugs fixed in this release:

  • #386: Avoid a PHP warning when a user had made translations and the user was then deleted.
  • #390: Update all delete permission levels to be consistent in different areas of GlotPress.
  • #404: Fix the CLI export command to properly use the “status” option.
  • #410: Add upgrade script to remove trailing slashes left of project paths from 1.0 which are no longer supported
  • #413: Fix conflict with other plugins that also use the `GP_Locales` class
  • #417: Exclude the art-xemoji locale from length check that caused spurious warnings.

Features in this release:

  • #411: Add Haitian Creole locale definition.
  • #412: Update Asturian locale definition.

In this version 6 issues were solved and 6 Pull Requests were merged, a total of 14 commits.

Contributors of this release: Dominik Schilling, Greg Ross, Yoav Farhi.

If you want to follow along or help out, check out our repository on GitHub.

#glotpress, #release, #wordpress-plugin

New day/time for weekly meetings

In last week’s meeting it was decided to change the meeting time to Tuesday 17:00 UTC.
Next meeting will be on April 19th at 17:00 UTC in the #glotpress channel on Slack.

GlotPress 2.0 “Beaker”

GlotPress IconAfter 2.5 months we’re pleased to announce the second release of GlotPress as a WordPress plugin.

Version 2.0 of GlotPress, named “Beaker” (the assistant to Bunsen Honeydew), is now available for download or update in your WordPress dashboard.

This release was focused on enhancements to the existing codebase and to tweak several forms to make them more intuitive. For example, you no longer have to select a format when uploading your translations, GlotPress will auto detect the format.

Also say good bye to dead ends, all forms now have a button to return to the previous page.

Ever created a wrong translation set? Now you can delete them with just two clicks, along with translations and glossaries. Even projects can be deleted.

More highlights:

  • UI to manage GlotPress administrators
  • Case-sensitive translation searches
  • Support for Java properties files
  • New and updated default locales
  • Inline documentation for actions and filters
  • Want to know more? Read the full changelog here.

We’ve also moved the “Translation Propagation” feature into its own plugin. The initial version had a few issues so we decided to remove it from core and make it available as a plugin. You can download the plugin from the WordPress.org plugin directory.

In this version 49 issues were solved and 120 Pull Requests were merged, a total of 380 commits.

Contributors of this release: Aki Björklund, Rami Yushuvaev, Dominik Schilling, Greg Ross, Peter Dave Helloand, and Sergey Biryukov.

If you want to follow along or help out, check out our repository on GitHub.

#release, #wordpress-plugin

GlotPress 2.0 Release Candidate 1

Today we’re releasing the first release candidate of GlotPress 2.0.

Since the first beta we have improved the handling of forms and action URLs to protect against several types of attacks including CSRF.

 
This software is still in development. Consider setting up a test site just to play with the new version.

The release candidate can be downloaded from the GitHub release page.

Continue reading

#196, #218, #230, #232, #233, #237, #243, #246, #254, #265, #267, #268, #276, #278, #280, #290, #294, #295, #297, #300, #301, #302, #308, #312, #318, #325, #327, #328, #329, #330, #332, #337, #343, #347, #349, #355, #364, #366, #wordpress-plugin