Internationalization

I don't see why this shouldn't be possible, especially as D7 is a lot better in multilingual support.
There might be still some route to go to have everything multilingual, but the basic setup should work fine and finally we're in an early alpha stage.
But let's see what the maintainers say...

Well, first of all, OpenAtrium isn't using the Spaces module in OA2.0 - it's now using the word "space" to mean "group" in the Organic Groups sense.

That said, there are a number of issues with Panels and multilingual - but also a number of solutions and patches in the works. I haven't attempted to build a multilingual site with OA2.0 yet, and so I can't say exactly where it stands right now.

But like Pancho, I'm interested to hear what the maintainers say!

We want OA2 to be compatible with multi-lingual and I'll commit any patches to core Atrium needed for that. But I don't plan to add i18n as a dependency to OA2 core, so it won't be multi-lingual "out of the box".

What I'd like to see is an OA2 plugin that contains the appropriate module dependencies that people can enable or disable as needed. Then I could include that and just have it disabled by default.

And yes, the Spaces module is GONE from OA2 (on purpose)! Panelizer/IPE takes care of the layout stuff Spaces used to do, and being able to override variables on a per-space basis is planned for the future of OA2.

Just disvovered this issue which is distantly related to my posted issue ( https://drupal.org/node/2036413 )

How is the status of this 'plugin'?

Is it possible for me to localize the oa2 installation in this moment?

You *can* localize it, but it will be a lot of work. After turning on the Locale module you will need to go into each Message Type (in Structure/Message Types) and Edit each message and fill in the tokens you want to use for the different display modes (email subject, email body, recent activity header, recent activity body, etc) for each language that you are using.

It's unfortunate that the Message entities don't copy the language_none values into the default language fields when locale is enabled, so you just need to configure that manually.

The status of the "plugin" for OA2 to handle internationalization is that it will not be part of the initial release launch, sorry. We are looking for people to help with localization of OA2 who could help write such a module.

>>>>>>>>>>
It's unfortunate that the Message entities don't copy the language_none values into the default language fields when locale is enabled, so you just need to configure that manually.
<<<<<<<<<<

The patch which I have found for the last entity -dev does just *this* (hope that I've understood you right). See solution in last comment of https://drupal.org/node/2036413 - I have tested with some data. It works fine. Try it on your own.

I don't think, that a oa2 needs more localization. It needs only one language (not mutilanguage) because it's an 'intranet' platform that doesn't need to be language-switchable in the 1st step.

Is it alright to adjust the version of relevant alpha issues to keep track of them?

For postponed issues, or "feature requests" you don't need to bump the version numbers. I'd only use it for bug reports to confirm that the bug still exists in the latest -dev release.

I think the response in #3 was clear.

OA " won't be multi-lingual "out of the box"."