Timeline
The glotpress-updates mailing list was broken, and is now fixed. You can subscribe to http://lists.automattic.com/mailman/listinfo/glotpress-updates to get emails for Trac comments and SVN commits.
This was tracked in #174. If there are any further issues, let me know.
Hello everyone! You probably know me as a WordPress core dev, but I also work on wordpress.org the site. That includes translate.wordpress.org and now I’ve ventured over to GlotPress as well. 
As you can probably see, I’ve been active in the last week in GlotPress development, on the heels of spending the last few months working on i18n in WordPress.
I hope to spend a few hours here and there making GlotPress and translate.wordpress.org better, but for that, this American monoglot needs your help. I’ve read this blog, but perused only some of Trac. I’m also still getting familiar with the codebase, so I’ll be looking to @nbachiyski to advise on architectural questions.
I do want to talk about the roadmap, but not yet. (Next week!) Help me get up to speed first. So: what are the nagging bugs and enhancements? Which tickets or patches on Trac need traction? What’s your pet project or peeve? What feature requests do you consider to be the highest priority? Who is willing to contribute code, who already has? How is GlotPress working for you? How is it not working for you? What else should I know or see? Tell me what to read and I will do what I can to absorb.
Here’s what I’ve worked on so far:
I also put in a request to have a GlotPress mailing list receive SVN commit and Trac ticket/comment emails, which should happen his week. (#174)
Hope to see you around. Happy translating!
Happy GlotPressing @nacin, we’re happy to have you around!
Great!
Like we talked about on Skype, there are a few things GP is really missing so far that would make the software a lot better.
A couple of things that spring to mind:
I’m sure I’ll come up with more stuff, but this is off the top of my head 
@Remkus de Vries I think I’m there with your point number one. The source code is at https://github.com/fmestrone/GlotPress – I have so far added basic user management and an installation wizard that pretty much does everything from the web
Great to get you on this project too Nacin, just gave #14 another whirl.
Hmm, what about some integration with profiles.wp.org to show some love for translators?
That’s more of a suggestion for wppolyglots/translate.wordpress.org, but yes, it is something I’d like to do. Just need to figure out how to display it.
Great! Our main problems for collaborative work:
Define validator rights only for a specific project(s).
Comments! We need to add some explaining words to rejected suggestions, etc.
Wiki page per project – for common terms, what should be done (changes), etc.
I’ll be checking the tickets and ideas I had after I’m back from spring break. Good to see this are moving forward.
Great to see glotpress getting some more love! Looking very forward to seeing this grow.
I’d love to use this for my wp plugins, but I found this particularly difficult to use in terms of updating the strings to be translated via e.g. a new pot file. That said, this was roughly a year ago…
Being able to actually delete project would be nice too. You know.. with going to the DB
Being able to actually delete a project without having to go in to DB mode would be nice too ..
+1 on this!
Also sorting projects would be great: after project ID, after date, or alphabetically after project title.
Thanx, Dave
I would suggest to add Remkus’ tutorial on installing and actually using GP for translations project, also with WP. It can be found here: http://remkusdevries.com/how-to-use-glotpress-for-your-translations/
Thanx, Dave
some way of adding comments will also be nice
I second that
Later edit: and a search-replace function
How about a subscription box here on the blog? WPDevel, BPDevel, bbPDevel, WPPolyglots all have subscription boxes.
Done
Sorry, took a bit of liberty with http://glotpress.trac.wordpress.org/ticket/193
Hope you don’t mind.
It would be great for corrections if you can search just in the translation strings and if you can search case sensitive.
For example:
email would be translated “E-Mail” in German. But sometimes the people translating it with “eMail” or “Email”, etc. Without case sensitive search and translation only search this is a nightmare to check …
+1
Would be really handy addition!
We’ve recently started using GlotPress to manage the 14 languages [and counting] supported by the WordPress Editorial Calendar plugin, and I find it useful but very far from full-featured for managing multi-contributor translations for open source projects.
First major area of concern is proper user management and permissions [yes, we would love to see the permissions structure gp plugin you mention]. This is touched on by 3 of Remkus’ points, and a bunch more in the comments.
My main question is, why isn’t GlotPress actually itself a WP plugin?!?!?! Why a separate and decidedly not mature/robust platform? Would solve so many things and make sense going forward!
If I have 1 suggestion, it would be to immediately focus on porting GlotPress to be a WP plugin to use WP custom types & taxonomies, regular WP admin, user management, commenting, subscriptions, etc. This is basically what everyone here is asking for; platform maturity and robustness, plus extensibility.
Anyone agree?
I added a ticket to refine the UX of bulk actions (approve, reject). #188, patch: 188.diff
Before:
After:
Cool.
Nice improvement.
In trunk with [680] and [681].
fmestrone, 
Abdessamad Idrissi 11:09 pm on June 25, 2012 Permalink |
Thanks Andrew for this update.
Is there anyway to speed the commit of the wating translations in GlotPress for BBpress?