C. Kitahara 7:49 pm on December 30, 2012
Tags: code ( 3 ), meeting ( 17 ), ux ( 2 )

Hi guys as @Zé mentioned before we need…

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.

#code, #meeting, #ux

Vinicius Massuchetto 9:51 pm on December 30, 2012

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
  
  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
    
    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
    
    I think that at least @defries, @stas and @scribu (possibly @westi) have commit rights, too
cfoellmann 7:20 am on December 31, 2012

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
  
  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
  
  @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
    
    Hi Stas :D,
    
    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
    
    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
    
    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
    
    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

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.