Sorry for delay. As I said, I am the sole responsible person for this delay, as I had numerous tasks to do in the meantime and this is not something to be done without being fully concentrated.
== Organizational issues ==
=== Yearly meetings in Berlin ===
Yearly meetings in Berlin. We've concluded that we want to have yearly meetings during the Wikimedia Conference in Berlin. It is the most convenient place, as almost all of us are Europeans and significant number of LangCom members live in Germany.
=== New member ===
We have the new member, but that's been already known.
=== New list admins ===
Saatdeep and MF-Warburg are new list admins. Old list admins are still list admins.
=== Internal procedures ===
We should define the following internal procedures:
* Who should define the rules how we are making decisions, per our communication with Board.
* There was a question of how to call the vote and what does formal voting mean. It should be flexible, it shouldn't be necessary that everybody votes about everything, but we should definitely define it.
* We should define the rules how to remove the LangCom members. Maybe we should adopt the stewards' confirmation procedure.
=== Who, what, do ===
* MF-Warburg has created the spreadsheet [1]. All LangCom members should have access there. It's useful to know who is able to do what. (Said so, I haven't filled the info, which I should do ASAP.)
* We should create our own Timeline, to be able to follow what should be done next. (It's likely MF-Warburg and I will do that.)
== Languages Foundation ==
* We were discussing creation of the ''active'' organization, based on the Language committee members. We started talking about that on Wikimania in London 2014, we are talking about that from time to time, but at this point of time everybody either expressed active support for the idea or didn't have anything against it. I will take the next step in the form of creating a separate thread, with suggestions how to continue that. Basically, the idea is to create the organization comparable to Wiki Education Foundation [2].
* During the discussion about Wikipedias in new languages, it's been suggested that it would be good to have a wiki farm external from WMF, which would be used for small communities to write there their own knowledge, without having to follow strict Wikipedian and Wikimedian rules (NPOV, strict copyright and similar).
== Language committee and WMF ===
=== Liaison ===
We need a WMF liaison, who would take care about our needs in relation to the WMF. We've agreed with Kathrine that it would be better that it would be a WMF employee rather than a Board member, as we need operational support. She mentioned Jack (not sure about his surname), who talked with us a little bit. Although we haven't discussed that, I think the default option is just to "promote" Asaf from a "community observer" to the WMF liaison.
=== "In the name of WMF" ===
In relation to the ISO 639-3 code for Mapudungun (see below), I've asked Christophe, Board chair, if we could find the way that Language committee fill the form in the name of Wikimedia Foundation. The answer is "yes" if we communicate particular issue with the Board. It is important to know that there is such an option for the future issues and not just related with ISO 639-3.
== Linguistic issues ==
=== Mapudungun ===
Mapudungun has the code which Mapuche people treat as derogatory. My position is that we should help them and make pressure over JAC to make the change. To be honest, I am prepared to push this into much higher level than Wikimedia is, as they were able to change the codes for a language because one ethnicity is inherently racist and didn't want to be connected with the other ethnicity by ISO 639-6 code name, while JAC are not capable to address colonial and racist past of their own societies.
Said so, Michael was quite nervous about that and he will definitely vote against that when I put this on vote here.
== Technical issues ==
This is "the rest" what I have. Some of the issues have been already covered. If others have something else to add, let them do that.
=== Look & feel of Incubator ===
It was raised by, I think, Oliver (and Michael?) that Incubator looks horrible for an average user :) I mean, it looks perfectly fine for an average Wikipedian, but quite confusing to anyone who doesn't know the internal dynamics of MediaWiki pages :D
The conclusion was that it would be good to contact WMF and ask for QA help in relation to how to make Incubator pages more convenient to new users.
(I have a note "incubator and programming", but I think it's about QA help. Anyone remembers something different?)
=== Phabricator task into the project ===
Amir should convert the tracking task on Phabricator into a project. Our mailing list should be subscribed to relevant tasks/tickets/projects, making all of us informed about the state of particular request.
=== Transliteration and translation ===
Kathrine, Amir and I communicated about the transliteration and translation engines. There is a low level email communication about that. If anyone is interested in that issue, let him or her contact Amir and/or me.
In short, if transliteration engine would be made properly, it could be used for machine translation, as well.
[1] https://docs.google.com/spreadsheets/d/1km84QEg4MIbeWekZ4qZVibQ37pX3sd4p8qHS... [2] https://wikiedu.org/