Since the last update there are quite some…

Since the last update there are quite some nice changes. Probably the biggest is a new filter that allows you to create a “child theme” with a plugin. Because of that translate.WordPress.org has the same header/footer as WordPress.org. Also it has a link to the blog/Polyglots and the translator handbook.

Changes

  • Finally fix caching bug when using Memcache including small improvement when importing strings
  • Improved project view. It’s now always 100% wide
  • Reverted code for changing the po/mo file names on export
  • Fix typos in locales.php
  • Added a new filter “tmpl_load_locations”. Now you can add your own template folder. Thanks to Nacin.
  • Moved project actions outside the template and added a filter “gp_project_actions”
  • Fix notice when importing new strings
  • Fix all kinds of strict PHP warnings. See #220
  • First small change to improve accessibility.

The next weeks I will concentrate on cleaning up milestone 1.0. Fixing some irritating bugs or moving it to milestone 1.1. Even if we don’t have versions it does help out to structure the flow.

  • Improve dealing with strings. Adding ability to import fuzzy strings (#138) and be able to mark a string as “waiting” (#84)
  • Ability to copy projects (#65) and copy translations between translations sets (#66)
  • Ability to check the same strings in of a language in main projects and it’s sub projects
  • Move Google translator out of core into the plugins folder (#170 and #133)
  • Add Microsoft translator (#103)
  • Records validator when importing (#217)
  • Improve check for empty translations (#149)
  • Improve/checking deleting of projects, translation sets and suggested translations (#186 and #223)
  • More accessibility improvements.
  • Remove “default” slug from a translations set (#67)

Lots of things that need to be done and the target is that everything should be fixed before WordCamp San Francisco. The main problem will probably creating unit tests

#progress

In the last couple of weeks several things…

In the last couple of weeks several things are fixed. Not what was on my list but still some major improvements that you guys like:

  • Export for resx format
  • Validation for when first translation is empty. Still need to get fixed for plurals
  • Added Last-modified support to the API for downloading a translation set
  • Change filename for po/mo files
  • Strings in RTL languages are now displayed from the right
  • Translations sets of a project can now be sorted. Still a little bit secret
  • Make project view 100% width when there are no subprojects
  • Fix some other minor things

Will check everything tomorrow that I didn’t break something and after that I will request that the changes are going to be applied on translate.wordpress.org.

Current focus is fixing the cache issues. Hopefully I’m able to write some unit tests for it in the next week.
Also hoping to fix empty translation for plurals and not exporting when one of them is empty.

Downloading as a zip file has no focus anymore. When most of the major issues are fixed we can look into that.

#progress

Upcoming improvements

In the next couple of weeks I’m trying to tackle some tickets and those are the following:

Currently I’m playing around in fixing some caching bugs reported by Milan Dinić in ticket #208. It’s an irritating bug what you only notice with Memcache on what is the case for translate.wordpress.org. Most important here is to have unit tests to test how it’s broken so you can fix it.

Another thing I want to work on is to have the ability to download a zip file with all translations of a project (#154). It’s a bit tricky because which projects that should be included. I guess a default of 100%. Also ticket #206 needs to be fixed what takes care of file naming. Mobile team needs to give feedback per platform.

Last one I want to tackle is ticket #149. The ticket is to not allow empty translations. It happens to me sometimes that I want to copy from original and instead add the translation or just press enter. There is a patch that I still want to commit after a check.

#progress

So yesterday I added the missing footer bar…

So yesterday I added the missing footer bar to the profile page and added a locale. Also did look at all tickets on 1.0 milestone. Closing a few that worked for me and added some comments to tickets.

There are still a lot tickets with patches and I hope we can reduce that this month. But to be able to do that we do need people testing patches and commenting on the tickets. So I’m curious who can make some time free for this. Also I have to mention that there are some tickets what do UI like profile pages. So you don’t have to be a developer to help out.

All tickets with patches for milestone 1.0

#bug-hunt, #trac

A few hours ago we had our first…

A few hours ago we had our first regular meetup of this year. With the amount of five people it shows how dead this blog and project really is. It’s quite disappointed to see because it’s quite an awesome project.

First thing we talked was the current progress of the WordPress plugin. 4 weeks ago we talked about getting a proof of concept done in two weeks. It’s hard to say if the current codebase has been proofed or not. I guess it does and we will be working on it at least for this month.

So with the current code base you the user can do all it’s own actions: registering for an account, login and updating their profile. The project pages has some work done but still needs a week work and most likely lots of rewriting. The code can be viewed at https://github.com/markoheijnen/glotpress-plugin

Second point we talked about the UI. More then a year ago Hugo Baeta wrote a post about it: http://blog.glotpress.org/2011/10/18/rethinking-the-glotpress-ui/. We talked really short about it and the result was that Cátia and Christian (cfoellmann) will be working on some mockups in how we can improve the current UI and when that is done discuss it.

The logs can be find here: https://irclogs.wordpress.org/chanlog.php?channel=glotpress&day=2013-03-07&sort=asc

Also a note that we didn’t talked about a bug scrub since there wasn’t really someone around. I guess you just post here if you have a ticket you would love to have attention.

So Cátia posted a few weeks about a…

So Cátia posted a few weeks about a regular meeting on Thursday 20.00 GMT. Not a lot of response but nevertheless the first one will be on March 7. Hopefully you can make it. Also if someone can put a notice of the meeting in the sidebar I would appreciate that.

The items that I have on my list are:

  • Status of current plugin development
  • Setting the date/time for a bug scrub on current code base.
  • UI refreshments. What to do to make the current design more workable.

Curious what other things I missed but need to be covered.

#meeting, #regular-meeting

Today we discussed the current progress of GlotPress…

Today we discussed the current progress of GlotPress and wether we can port it to a “plugin not plugin” format, which basically means that it is not a regular plugin. There are still lots of concerns if a plugin makes sense to do, because of scaling and what we really gain with it.

Still, lots of people like the plugin idea and for the next two weeks we will try to make a proof of concept to show that issues like the current routing of urls to views can be solved. This doesn’t mean it will be a workable plugin. This development will taken place on https://github.com/markoheijnen/glotpress-plugin. After two weeks we will evaluate the current progress. Current team now is japheth, vinicius, marko, zé and ldebrouwer.

The issue was raised that a plugin will not help out the current lack of development progress. This is probably still something we need to think more about it. How can we solve the current lack of progress and get more contributors? We probably need to think more about this. Obviously current development will also be looked at, i.e. looking at current op tickets on the 1.0 branch and getting some of the tickets fixed.

Another issue that was raised is that GlotPress is missing a projectleader. Currently there isn’t a plan how the project’s progress will evaluated, and as mentioned this is something that bothers people. Also a development leadership is missing but this is something that can be done with the help of Nacin and Nikolay, who both know this project really well.

Logs:
https://irclogs.wordpress.org/chanlog.php?channel=glotpress&day=2013-02-07&sort=asc
https://irclogs.wordpress.org/chanlog.php?channel=glotpress&day=2013-02-08&sort=asc

#meeting

Hey Guys I would love to have a…

Hey Guys, I would love to have a meeting about the future of GlotPress and see how it goes from there. What do people think of Thursday 7th at 22pm GMT? I would love to talk about current development, the idea of having it as a plugin and having a regular meeting. Also I would love other things for the agenda.

#meeting

Would it make sense to rewrite GlotPress to…

Would it make sense to rewrite GlotPress to be a WordPress plugin? I think so and wouldn’t mind to take the lead in it. I think it would be an hugh improvement to see it as a plugin.

#code, #plugin