CiviCRM Community Forums (archive)

I was wondering if there would be any interest in reviving the mailing-list for internationalization discussions for developers?

* a lot of the discussions for CiviCRM development mostly happens on mailing-lists (ex: API, LTS, infrastructure, partners).
* mailing-lists are generally low-traffic, but a good way of make sure everyone is informed of an upcoming change, for example. Sometimes it might just be a link to a forum post or a link to an issue on JIRA.

We already have a list for internationalisation, and another for translators, but there were never really used. I tried for a while to make sure we communicate some important changes on this forum section, but I often feel that a lot of people do not receive the notification. The focus would be the same as other CiviCRM lists: keep discussions in jira/forum/SE/etc as necessary, use the mailing-list as a low-traffic tool for "public announcements".

Any thoughts?

I agree, and doing more outreach to developers solves a lot of issues upstream (I really appreciate that you have been doing so). However many translators aren't on general development mailing-lists/forum sections. I would like to make sure we can reach out to as many folks affected by i18n as possible when necessary.

When posting here, I don't have the feeling that most people do get the notifications. I would still encourage to continue posting here, but would also post a link to the mailing-list.

Other example of issues that affect mainly translators: when 4.7 is branched, we need to send an announcement that the strings are now on Transifex, CiviCRM 4.4/4.5 support dropped, ask people to review new strings (fix typos, strings that don't make sense). Although, for this specifically, perhaps in some future, we could automatically feed a list of Transifex translators into CiviMail.

Thanks for the feedback.

I also asked the question on the civicrm-intl@ list, where a dozen people were already subscribed, and received interesting responses.

The conversation diverted into tagging strings in Transifex, and when to drop 4.4 strings from Transifex. We agreed that they would be dropped on March 31st, which is ~ 3 months after the end of 4.4 LTS support.

I also did a quick test to tag strings in Transifex using their REST API. This would make it easier for translators who are getting started with translation, to focus on the latest version of CiviCRM. For the "Event" resource, it meant 10% less strings to translate.

For more info, see:
http://lists.civicrm.org/lists/arc/civicrm-intl/2015-12/mail1.html#00001

I guess the conclusion of this discussion is that, like on other areas of CiviCRM, some people prefer email, some prefer forums, and I think it's worth using both. I also agree 100% with Coleman that we need to make sure that all CiviCRM developers know how i18n works.