search

Life-the-game / Open-Discussions

Life. Feedback Tracker
https://github.com/Life-the-game/Open-Discussions/issues
1 stars 0 forks source link

Open Source Life. #78

Open matthieu-vergne opened 10 years ago

matthieu-vergne commented 10 years ago

It would be nice to have, if not all, at least part of the code open (libre) and available on GitHub. This way we could contribute more concretely. The translations for instance (cf. issue #57) seems to me particularly relevant to open. If you do not want all your code to be open, maybe the most common parts of it. I mean the one you can find elsewhere and do not correspond to your main process, like database management and other common stuff. This way you could exploit the expertise of your community members in these redundant domains.

db0company commented 10 years ago

We planned to open-source our SDKs to people can easily use our API, in JQuery (or generic javascript), OCaml, PHP, Java for Android, Obj-C for iOs and Python.

We do our best to publish some generic parts of our project as open-source small projects, but we wish to keep the core of the project protected. Lots of my (db0company) personal repos are used in the website, lots of rFlex' repos are used in the iOs app. We might publish some parts of our API later.

About the internationalization, we will provide tools directly on our website so external contributors will be able to help us with the translation, and of course, unlock achievements for that, without having to actually write code.

matthieu-vergne commented 10 years ago

For the code by itself, maybe you can fork your personal repos to have official ones for Life., on which you can have a different contributor management and Life.-specific optimizations (and use pull request between personal-official repos). Maybe the git modules could be exploited too to have a unique project which includes everything (for an easier management).

For the I18N (internationalization), or L10N (localization), there is already existing methods, typically file-based ones, which allows you to focus on the translation (no code inside) and to version it easily.

A quick reading on the topic: http://www.onlamp.com/pub/a/php/2002/11/28/php_i18n.html The PHP i18n API: http://www.php.net/manual/en/book.intl.php A Web-based translation tool: http://www.matecat.com/ (for the latter, it is developped in my current university and I tried it, I can help to contact)

I think it would be more relevant/easy to use such things rather than having a "translation module" integrated to Life. Or at least I think it is far from the purpose of a social network like Life., so I would prefer that you spend your energy on other issues {^_^}. Just a personal opinion, but I have already translated videos, apps and other stuff, and if you want something flexible and robust enough you need to spend quite an effort.

But if it is one of your objectives in Life., I won't stop you {^_°}.