GlotPress 2.2 RC 1

The release candidate of GlotPress 2.2.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. There were no changes since beta 1. For more information about what’s new in version 2.2, 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 September 28, 2016.

Happy testing!

#development, #release, #wordpress-plugin

GlotPress 2.2 Beta 1

The first beta of GlotPress 2.2.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 was to handle scripts and styles more efficient and to fix some minor bugs.

Breaking Changes

  • Change the slug of the Kyrgyz locale from ky to kir. (#550)

Bugfixes

  • Fix broken cancel link on project create form. (#547)
  • Fix native name of the Tibetan locale name from བོད་སྐད to བོད་ཡིག. (#539)
  • Fix extra entry in GP_Translation::translations(). (#516)
  • Merge similar strings to improve translation. (#535)
  • Refactor script and style registration to make them more reliable. (#476)
  • Update locale information for Kyrgyz to use correct data. (#550)

Features

  • Add locale information for the Latin version of Hausa. (#549)
  • Fix translations which are using the placeholder for tab characters. (#473)
  • Add gp_reference_source_url filter for the source URL of a project. (#522)
  • Provide minified assets. (#505)
  • Update JavaScript library for table sorting. (#502)

In this version 13 issues were solved and 19 Pull Requests were merged, a total of 65 commits.

Contributors of this release: Alexander Kirk, David Decker, Dominik Schilling, Greg Ross, Pedro Mendonça, Petya Raykovska, and Sergey Biryukov.

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

The next release (RC1) is targeted for September 21, 2016.

Happy testing!

#development, #release, #wordpress-plugin

Office Hours Recap (September 13)

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/p1473786115000207
Attendees: @gregattoolstack, @swissspidy, @samuelsidler, @sergey, @petya, @ocean90

Notes

  • The milestone for 2.2 has been reviewed, it’s 80% completed.
  • @ocean90 found two issues while testing:
  • @gregattoolstack is going to review and track them down.
  • The PR for the Hausa locale information needs a refresh. Since @petya can’t handle that at the moment @ocean90 will submit the new PRs.
  • Issue #479 for an uninstall routine has been discussed.
    • The current PR isn’t ready for a merge.
    • gp_uninstall()⁠⁠⁠⁠ should looks good.
    • For the $wp_settings property a better name should be identified.
    • @ocean90 suggest inline settings because just having one option on a admin page feels odd.
      • The feedback was mostly against this idea.
    • It was decided that for 2.2 no admin page with just one option gets added.
  • Major refactors like #540 should be discussed first in the Slack channel to avoid working on things which may not get merged.

 

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!

#office-hours

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!

#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!

#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!