Hi guys, as @Zé mentioned before, we need to revive GlotPress development. I’m up to it and I’d like to contribute with my design skills and my experience as a user. Also, I’ve talked to some programmers I know who can contribute too. But where do we start from? I’ve read past posts from this blog and I noticed there were some efforts to improve the interface, among other things, but it seems they came to nothing. Why is that? So I think it’s a good idea to schedule a regular meeting on the IRC channel so we all can be updated on the development status, stablish priorities, etc, if there isn’t one yet. What do you think of it? @fmestrone, @nacin, @remkus and whoelse would like to help.
Updates from December, 2012 Toggle Comment Threads | Keyboard Shortcuts
-
Cátia Kitahara
-
Andrew Nacin
Howdy!
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:
- Wrote a plugin for translate.wordpress.org that overrides the permissions system to use Rosetta user roles (happy to open-source this for the GP community at large)
- Performance improvements [671], [672]
- Updated jQuery and jQuery UI, and updated JS to use newer methods [673] [675]
- Fixed #183 (“Copy to original” on plural strings)
- Committed fixes for #169 and #184
- Bulk actions UX/UI changes, see previous post here
- I have looked at and asked Nikolay to review #187, #170, #135, #139, #163, #150, #129, #115, and #14.
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!
-
Nikolay Bachiyski
Happy GlotPressing @nacin, we’re happy to have you around!
-
Remkus de Vries
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:
- Not having to go into SSH mode to change a user into an admin would be wonderful.
- Being able to define validators for a specific language throughout the entire GP installation is missing.
- Having a per language and / or project message pointing to translation specific wiki’s and how-to’s would be a huge win.
- Blocking certain users would be rather pleasant. Certain people, however good their intentions are, should not translations.
- A proper Fuzzy mode showing strings that have little change and would only be visible for validators.
I’m sure I’ll come up with more stuff, but this is off the top of my head
-
fmestrone
@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
-
Joost de Valk
Great to get you on this project too Nacin, just gave #14 another whirl.
-
Stas Sușcov
Hmm, what about some integration with profiles.wp.org to show some love for translators?
-
Andrew Nacin
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.
-
-
pavelevap
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. -
Peter van Der Does
I’ll be checking the tickets and ideas I had after I’m back from spring break. Good to see this are moving forward.
-
Marcus
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…
-
Remkus
Being able to actually delete project would be nice too. You know.. with going to the DB
-
Remkus de Vries
Being able to actually delete a project without having to go in to DB mode would be nice too ..
-
David Decker
+1 on this!
Also sorting projects would be great: after project ID, after date, or alphabetically after project title.
Thanx, Dave
-
-
David Decker
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
-
de ce?
some way of adding comments will also be nice
-
OC2PS
I second that
-
-
de ce?
Later edit: and a search-replace function
-
OC2PS
How about a subscription box here on the blog? WPDevel, BPDevel, bbPDevel, WPPolyglots all have subscription boxes.
-
Zé
Done
-
-
OC2PS
Sorry, took a bit of liberty with http://glotpress.trac.wordpress.org/ticket/193
Hope you don’t mind.
-
Torsten
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 …-
David Decker
+1
Would be really handy addition!
-
-
Colin
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?
Cátia Kitahara, 
Denis, 
fmestrone, 
Vinicius Massuchetto 9:51 pm on December 30, 2012 Permalink |
Well, in a first place, who’s applying patches and taking care of current contributions? There seems to be some mantainance stuff running, but most patches are just ‘new’, waiting for tests.
Curiously, the last message in the list, almost a year ago, is asking how to help with the project.
Cátia Kitahara 4:54 pm on January 2, 2013 Permalink |
The list is almost dead, Vinícius, and the guy had an aswer and was directed here. What we need to do is update the trac homepage with this information, but we need somebody to do that. I guess Zé Fontainhas have been doing that, though it’s really not his responsability and I don’t know if he wants that. My intention here isn’t to point finger at people who aren’t doing their jobs, but to start doing the job ourselves and make an effort to make it go foward.
Cátia Kitahara 5:02 pm on January 2, 2013 Permalink
Ah, only Zé, Nacin and Nikolay have commit permission, I guess. As Zé proposed in this blog, sometime ago, this should be like this until somebody else starts contributing regularly and with an acceptable code.
Zé 5:14 pm on January 2, 2013 Permalink
I think that at least @defries, @stas and @scribu (possibly @westi) have commit rights, too
cfoellmann 7:20 am on December 31, 2012 Permalink |
For me the main problem is SVN. No possibility for the casual contributer to submit anything easily.
@fmestrone did his fork at https://github.com/ReGlot/ReGlot and I jumped on the ReGlot-Train with https://github.com/Foe-Services-Labs/Translate and contributed a proper UI based on Bootstrap and FontAwesome. The service is hosted at https://translate.foe-services.de (deployment of the deploy-branch) – lets call it a stable beta – and the most current version of my ReGlot-fork (master-branch, a little buggy sometimes) is at https://reglot.foe-services.de. All upstream changes to GlotPress (not much at the moment) will be implemented to ReGlot by @fmestrone.
If you are comfortable with the fork join us! I am desperate for some coders since I am just a frontend designer and translator myself.
Cátia Kitahara 4:50 pm on January 2, 2013 Permalink |
I don’t think svn is a problem, it’s just a version control system, the problem is lack of a proper team leader. SVN, git, it doesn’t matter. My point isn’t just to keep developing GlotPress, but to develop it because it’s important for the future of WordPress and because it’s a real interest of the international community.
That said, we should bring these contributions to the “official” version, instead of maintaining a fork. That’s my opinion and that’s what I’m proposing here.
Stas Sușcov 4:55 pm on January 2, 2013 Permalink |
@cfoellmann Catia is right. There’s a GlotPress mirror on GitHub, if you would send a pull request there, I would see that.
Regarding ReGlot, there might be some good contributions there, but the maintainer simply dropped tests, which is unacceptable for the project.
The solution would be to sit and discuss a possible collaboration and split the tasks.
Cátia Kitahara 5:00 pm on January 2, 2013 Permalink
Hi Stas
,
Exactly! That’s why I’m proposing a meeting at the IRC channel and I think Nacin, Nikolay and Zé at least should be present. I’ll tweet this to bring their attention, I don’t know how this mentioning thing works here. It worked for Nacin, but not for Zé or Nikolay.
Vinicius Massuchetto 4:37 pm on January 4, 2013 Permalink
The changes presented by @cfoellmann looks pretty good in the GitHub project! However, I think an approach to the WordPress appearance (as it uses BackPress) would be more appropriate, but this is another discussion…
The difficulties we’re experiencing in GlotPress are much more around the workflow than the appearance. It would be a good idea to define priorities, so we can propose our changes accordingly.
Denis 3:16 pm on January 15, 2013 Permalink
I would disagree with Catia and Stas.
GitHub is more than just a versioning system. It also creates an eco system so that it is easy to make pull requests and track bugs.
Nice to hear, that GP has a mirror on GitHub. But is it official?
Main problems for me with GP are:
1) No user logins mechanism after install (had to install WP and add link to login)
2) No translation available for the GP itself. How it is possible that translators had to use English only software for translation?!
BTW I was not able to install ReGlot. Was not functional after installation. ReGlot has English strings for translation…
Cátia Kitahara 8:22 pm on January 30, 2013 Permalink
Denis, I agree that git is better than svn, and github is great for contributers, however, though the version control tool plays an important role, it’s not the main reason why GlotPress development is stuck.
Stas Sușcov 4:40 pm on January 2, 2013 Permalink |
I remember we did some cleanups during summit so milestone 1.0 tagged issues are more or less what needs to be done.
I also have a couple of patches I didn’t get a chance to commit mostly because of the lack of free time. But I would love to help if there are more people to jump in.