Please go through the list of issues/PR’s and leave a :thumbsup: if you think something is OK or add comment if something should be changed. Thanks!
Recent Updates Toggle Comment Threads | Keyboard Shortcuts
1. New Issues
The goal is to set a release tag and owner, technical discussion of the issue can be done in the GitHub ticket.
- IS33 Prefix all GlotPress Action/Filters with “gp_”
- IS34 Database is only updated on plugin activation
- IS35 Replace $gpdb with $wpdb
- IS36 Recent merge of upstream changes conflicted with the assets move PR
2. New PRs
The goal is to make a decision if a pull request is:
- ready to merge
- not ready but should be targeted at the next release milestone
- not ready and will be targeted at a future release milestone
- will not be merged (declined)
- PR38 Allow GP to take over the root URL on the frontend
- PR44 Plugin prefix actions and filters
- PR45 Move install css
- PR46 Remove the $gpdb global and replace it with $wpdb
- PR47 Database is only updated on plugin activation
- PR48 Convert gp plugin system
- PR49 Merge upstream changes as of Oct 14 2015
3. Outstanding Issues/PR’s with 1.0 tag
The goal is to assign an owner if none exists, determine if it should still be targeted at the 1.0 release or postpone to a future release.
- IS1 Attempting to “import originals” times out [SergeyBiryukov]
- IS5/PR20 Remove GP_User [A5hleyRich]
- IS7/PR48 Convert GlotPress plugin system to WordPress [toolstack/Greg Ross]
- IS9 Backwards Compatibility 
- IS10 Allow GlotPress tables to have a table prefix independent of the WP table prefix [bradt]
- IS11/PR43 Merge upstream changes [ocean90]
- IS15/PR16 Make plugin translation ready [polevaultweb]
- IS19 Convert GP permissions to WP roles 
- IS21/PR22 Flush rewrite rules on plugin (de)activation 
- IS23/PR24 Convert scripts to WP-CLI commands 
- IS30/PR38 Allow GP to take over the root URL on the frontend [bjork]
- IS31/PR32 Unit tests [gilbitron]
4. Release Target
Discussion for a soft target for 1.0 release.
5. New Items/Technical Discussion/Open Discussion
Suggestions for any other agenda items can be posted in the comments.
(Thanks to Greg Ross for the agenda proposal.)
At the GlotPress weekly chat last week (September 24), a large number of attendees were interested in developing GlotPress as a WordPress plugin. There are certain advantages to this direction, including the availability of tens of thousands of WordPress plugins and the ability to utilize many WordPress features instead of reinventing them. You can read the log of that meeting here (there was more follow up in today’s GlotPress meeting as well).
As a result of those discussions, a group from the community has formed a team to develop GlotPress-the-plugin on GitHub. Today, this team met and discussed a short roadmap to get the plugin ready for production on translate.wordpress.org, among other sites. Here’s a quick recap of some of the decisions that were made on the path toward 1.0:
- In general, the goal is to keep GlotPress the same and only replace features if WordPress already includes them. Commits to GlotPress core (SVN) will be merged into the plugin as-needed.
- GlotPress-the-plugin should live alongside WordPress instead of being a standalone application. This means a site could still use posts and pages, just like other WordPress installations. Of course, this behavior could easily be modified by a plugin.
- For the initial version, the GlotPress administration tools will remain on the front end and not move to WP-Admin (#14).
- GlotPress plugins will need to be converted to WordPress plugins; GlotPress-the-plugin will not provide backward compatibility for GlotPress plugins. However, scripts should be made to migrate installs, perhaps using wp-cli (#9).
- It is recommended that WordPress plugins that support GlotPress-the-plugin use “gp” at the start of their slug and include the “glotpress” tag in the plugin directory.
- For version 1.0, theming in GlotPress will remain the same. Integration with WordPress themes will happen later.
- Version 1.0 of the plugin will also not include migration tools for
usermetatables. While there are certainly installations which utilize these GlotPress tables, a fair number use WordPress tables to manage their users. Migration tools will be added later (#6).
- Code practices should follow the WordPress core best practices. However, just as core does, these standards only apply to new code or when modifying code; old code can remain as it is (see also).
For the foreseeable future, development of this plugin will take place on GitHub. You can view the 1.0 milestone for more information.
If you’re interested in this direction for GlotPress, get involved and help build the plugin or join us for the next GlotPress-the-plugin chat, next Thursday at 13:00 UTC, just after the GlotPress chat.
Currently we have a new header/breadcrumb design which looks better then we had before. It takes up a little bit more height but in return we now have a menu where you can add links if wanted.
Due to this redesign the output of gp_breadcrumbs is a list now and styling will be applied on display. Still makes adding new items easier since you don’t need to know the styling. Also the action after_hello got removed.
Other updates are:
- Show login after installation again and after that redirect to the home page
- Make warnings for newline mismatches more verbose.
- Ready to commit a patch for gp_title
- Currently working on favorites/watched projects and decline with feedback.
The upcoming week lot’s of code changes will happen. When you keep up-to-date with the latest code of GlotPress, it is recommended to not do this directly on production in the next days. Specially when you have custom code or theme. I would appreciate you guys testing things out and leaving feedback during this week.
My focus in random order is:
- new header with navigation
- redesigned breadcrumbs
- Changes in gp_title
- reject with feedback
- Move BackPress to GlotPress
If you feel something is missing then let me know and I will see if I can manage to get something done on that too. Otherwise I will let you know when I think I can work on it. Also if you want to help out, let me know here or ask in the GlotPress Slack channel on WordPress Slack
It has been a long time goal to have a regular meeting but till now I couldn’t find the time that I would able to be there most of the time. After rethinking the time from comments, I decided to set up a weekly meeting at 12UTC on every Thursday starting this week.
This first meeting we will discuss how to notify Validators and translators for important changes. I just created two tickets for a Notification Center and for Favorites. This will help us out with sending out notifications and building up a user dashboard. In the next couple of days I will work on this so we can discuss the progress.
In the last year there were several discussions about the design of GlotPress. I tried to use bootstrap to make it nicer but what we really need is a complete rewrite of the theme. For this purpose I created a repo on GitHub where we can build a fresh new theme that fits our needs. Also Aris Blevins already created some mockups how the translation flow could work. This is also linked on the GitHub channel.
If you want to help out just leave a comment and check out https://github.com/GlotPress/New-Default-Theme. You can create tickets with ideas and things you would like to change.
So it has been quiet for the last two months. Only some small changes have been made to the code. But before going into this years plans I first want to thank all the contributors from last year: yoavf, Secretmapper, vanillalounge, nacin, nbachiyski, DJPaul, koke, dimadin, juanramondiaz, wonderboymusic, stuwest, extendwings, Nao, ocean90, knome, joostdevalk, waclawjacek, cfoellmann, ramiy, hew. And that is without mentioning the people who submitted still waiting patches and tickets. It was a good year where great improvements where made.
So for this year already quite some tickets and patches have been created and I will try to review this month. There will be three focus topics for this year which are increasing contributions, build a new default theme and rebuild part of core (to increase performance).
To increase the amount of contributors we will try to be more proactive when tickets, patches and issues are raised so people feel more connected to the project. Also from March there will be a weekly meeting where we can sync planning and work on new ideas. currently I’m thinking to do this meeting on Thursdays at 15:00 UTC. If you have suggestions then please let my know. I will create blog posts for the other two topics.
As last, from this point on I will be actively leading the project. Due to the fact that we have active contributors now, it also means that my role need to be active instead of committing things that I like to work on. Also GlotPress has become more important for open source projects and there is a lot of things that could increase the usability of GlotPress.
As promised in last update we will now have monthly update post. The biggest change is that since this weekend we moved to PHP 5.3. While we adding new features, we also clean up the code and this time we starting to deprecate our lambda function and now moving to anonymous functions which got added in PHP 5.3.
Unfortunately we didn’t manage to do the things on our roadmap due to fixing some important bugs. But I’m sure that some of those bugs will make you guys happy. I finally had the time to dig into the caching issue of the translation set counts and fixed it. We also currently hidden public profiles but that will be back in a few days.
- Invalidate the translation set cache when approving/rejecting a string.
- Increased performance of profile pages.
- Disregard context if it’s any falsy value.
- Fix going to the previous translation with the keyboard.
- Move to the next translation when approving/rejecting a string.
- Reduce the size of index ‘singular_plural_context’ for originals.
- Added a link on users profile page to his translations of that translation set.
- Fix guess_uri() for subdirectory installations.
- Fixed not exporting translation comments for PO files.
- Don’t fatal when hitting a projects page where the parent project has been deleted (work in progress).
- Remove RRC format.
- Stop using lambda function and start switching to anonymous or normal functions.
- Add support for Oriya and Lingala.
- Update Kinyarwanda.
Thanks to: yoavf, joostdevalk, nbachiyski and waclawjacek
Changesets 970 – 999
In the last year things got changed and improved. Lately things are speeding up and part of that we decided to move to PHP 5.3+ because we want to move away from create_function() and start using anonymous functions. For the current patch you can check out https://glotpress.trac.wordpress.org/ticket/305
The current patch will be committed this week and from there we will start looking at other functions that are still calling create_function().