Skip to content

workflow for non-developers? #4

@dcsan

Description

@dcsan

@SachaG I had a couple of people email me and someone has made huge progress with the japanese translation.

https://drive.google.com/folderview?id=0B3NKQUsJ7bKsZ0l3YmxuaTlJR1k&usp=gmail

however, they aren't developers so not sure of the whole workflow with pull requests etc.

I'm sure you considered this but is there too much overhead in setting up a web based UI for managing the crowd-sourced translations? this would significantly lower the barrier for non-devs to contribute a few strings here and there, and also not step on each other's work.

For meteor I've seen Gadi's https://github.com/gadicc/meteor-messageformat project which gives a way to manage all the strings like this: http://messageformat.meteor.com/translate
It also tracks updates etc.

There maybe other tools out there (non meteor) too and I guess various platforms that are also free to use for open source:
http://www.quora.com/Are-there-any-good-open-source-collaborative-translation-apps

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions