ON MY OWN PROJECT
WITH A COMPLETE DIFFERENT THEME
Diﬀerent roles: Translators, Validators and Admins.
Manage strings by reject/approve them.
Having a glossary with common words.
Import/Export diﬀerent formats.
History behind it
Started in April 2008 by Nikolay Bachiyski.
Uses BackPress as a framework.
And it’s OOP developed.
March 2013 I started managing GlotPress.
March this year Yoav Farhi has commit access.
This year we have our ﬁrst GSoC project.
Commits during the year
2014: 106 and counting
Uses BackPress which has a lot of classes.
And we build on top of that our features like
routers, formats and things.
Those three objects always need to extend a
This class has shared functionality or has abstract
methods the derived class needs.
Because of the generic classes we can make our
You can deﬁne in a thing which ﬁelds are required
to create a new item.
A thing is a project, user, translations etc.
GP_Glossary ﬁle has only 42 lines of code and has
all validations in place.
We still use them a lot like WordPress does for in
A lot of them are copied over from WordPress
This is a great thing cause if you are using
GlotPress yourself you can “easily” add a feature
to GlotPress because the hook system is in place
and so many other great features.
GlotPress has a lot of scripts that you can or must
Like adding a new admin is a must due missing
user management. Will have an add user script
Or things like import/export originals or
Tools we use
We do have a certain amount of Unit tests
Travis to run our unit tests
for Code quality scans
https://coveralls.io/ for code coverage history and
THE FUTURE / ROADMAP
HOW SHOULD IT LOOK LIKE? AND HOW SHOULD IT BEHAVE?
Currently we only have a limited amount of
projects on translate.wordpress.org
~10.000 plugins are translatable
The UI needs a diﬀerent approach
Managing translations will become key
How to translate strings
Is the current approach still the best.
Do we need a diﬀerent ﬂow that could speed
Does it show you the information needed?
How to display the history of the translations and
Is comments a high priority since we got
What are the projects you have worked on?
And are the new translations for it?
Or do you even need to approve strings
It’s part of the GSoC this year :)
You can’t keep up what cores does. Stand alone if
there are more projects you contribute too.
Sending out automatically e-mail is a key for this.
Obviously you should not get to much
Also part of GSoC.
Better string management
Be able to keep original translations and have
them still approved or the string need to be
Better history of translations.
Indication when locales don’t have validators.
Be able to delete suggestions.
Currently there are a lot of options to ﬁlter.
We should rethink this and check what the
common cases are.
Like only searching on original or translation.
I would also say that it needs to be more obvious.
Do we need a new theme?
With all this ideas and more do we need to rethink
the whole theme?
Adding new features to the existing UI can be
tricky depending on the feature.
I tried to put everything in Bootstrap and see how
THIS WAS A BIT MY
BRAINSTORM ABOUT THE