The development and future of GlotPress

2,095 views

Published on

A talk about the history, the current status en future of GlotPress. GlotPress is a collaborative, web-based software translation tool used by WordPress and related projects.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,095
On SlideShare
0
From Embeds
0
Number of Embeds
42
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

The development and future of GlotPress

  1. 1. THE DEVELOPMENT AND FUTURE OF GLOTPRESS WORDCAMP HAMBURG 2014 - MARKO HEIJNEN
  2. 2. What we discuss today Who I am What is GlotPress History behind it Tools we use The future / Roadmap
  3. 3. Marko Heijnen Founder of CodeKitchen WordPress specialist for 1&1 Lead developer of GlotPress Core contributor for WordPress Helping out the minority
  4. 4. PART OF THE DUTCH, SERBIAN AND I GUESS NOW THE GERMAN COMMUNITY
  5. 5. What is GlotPress GlotPress is a collaborative, web-based software translation tool.
  6. 6. USED ON WORDPRESS.ORG WITH IT’S OWN HEADER AND FOOTER
  7. 7. USED ON WORDPRESS.COM WITH THE DEFAULT THEME
  8. 8. ON MY OWN PROJECT WITH A COMPLETE DIFFERENT THEME
  9. 9. Features Different roles: Translators, Validators and Admins. Translate strings. Validate strings. Manage strings by reject/approve them. Having a glossary with common words. Import/Export different formats.
  10. 10. 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 first GSoC project.
  11. 11. Commits during the year 2008: 32 2009: 341 2010: 223 2011: 58 2012: 79 2013: 91 2014: 106 and counting
  12. 12. OOP 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 generic class. This class has shared functionality or has abstract methods the derived class needs.
  13. 13. OOP Because of the generic classes we can make our code better. You can define in a thing which fields are required to create a new item. A thing is a project, user, translations etc. GP_Glossary file has only 42 lines of code and has all validations in place.
  14. 14. Functions We still use them a lot like WordPress does for in themes. 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.
  15. 15. CLI GlotPress has a lot of scripts that you can or must use. Like adding a new admin is a must due missing user management. Will have an add user script soon. Or things like import/export originals or translations.
  16. 16. Tools we use We do have a certain amount of Unit tests Travis to run our unit tests https://scrutinizer-ci.com/g/GlotPress/GlotPress/ for Code quality scans https://coveralls.io/ for code coverage history and stats
  17. 17. THE FUTURE / ROADMAP HOW SHOULD IT LOOK LIKE? AND HOW SHOULD IT BEHAVE?
  18. 18. Future problems Currently we only have a limited amount of projects on translate.wordpress.org ~10.000 plugins are translatable The UI needs a different approach Managing translations will become key
  19. 19. How to translate strings Is the current approach still the best. Do we need a different flow that could speed things up. Does it show you the information needed? How to display the history of the translations and comments. Is comments a high priority since we got glossaries?
  20. 20. Personal dashboard 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 :)
  21. 21. E-mail notifications 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.
  22. 22. Better string management Be able to keep original translations and have them still approved or the string need to be approved again. Better history of translations. Indication when locales don’t have validators. Be able to delete suggestions.
  23. 23. Better search/filter Currently there are a lot of options to filter. 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.
  24. 24. 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 it looked.
  25. 25. QUESTIONS? THIS WAS A BIT MY BRAINSTORM ABOUT THE FUTURE,

×