This could have easy been addressed by discussing it first, so we could put on the table what we've been thinking and discussing about this, and do it right the first time, instead of wasting your time, and ours.
I clearly addressed it and there was clearly no discussion about it, now you say it is good and you would have discussed about it, so why didn't anybody then? As you are already on that, how can you explain combination of PR, PM to you and thread post being done at the same time? What discussion did you expect to have and when? Yes, instead to speak about real things and issues and discuss proposed things your users seem to be hit in their ego, whatever the reason is, I have no clue about it, those who report instead to ask first might be those who could reply you this question.
setting the service itself up is the easy part. Embedding it into the organisation, the build process, the way po's are generated, the users, the translators, etc, is the complex bit
then you must have not missed that nothing has changed and needs to be changed in the build process, you can do it. And no, it's not a secret how po's are generated or where from do you think I get enigma2.pot file? It was described in commit itself as well as in PR and I wrote you in PM that you can have enigma2.pot somewhere (as you delete it now because it is junk, by your script). I also said that it is a scratch and your guys should probably first get familiar with it before jumping on the gun claiming some stuff which is obvious. On your translation process changes only that you guys need to take care of your english source file and that also can be done automaticly by simply pointing to a specific raw link (of any branch on any repo).
I mean, sure, you can just say that you guys have never used it and that you need time to get familiar with it. And as you say that it is easy to setup and that it is the easy part and then claiming that I might have not considered translation process is not correct . You might import those files by yourself and check for errors then maybe compile to see if everything works. However, on transifex you would never approve indonesian translations in chinese files and similar. You still can use your old way of translations, that is probably something you missed, so no, no new company restructuring is required, you will require new guides if you dislike to refer to already perfect guides from transifex, however, it is meant to make translation easy for devs and translators and those verifying translations. And you also have full history of it, who reviewed, who translated etc..., on github you would have only to commiter ID or some cherry picked commit.
I don't really understand what your problem is.
Now you become irrational with that question, why should I have some problem? Do you have some problem?
You clearly are clueless to what is involved in the legal registration and trademark process. And the number of countries around this world that couldn't care less what is registered and what is not.
That doesn't mean we won't do what is needed to protect our name (within what is possible as a non-profit organisation).
Now you clearly become personal and you seem to talk about things you do not know, don't denounce yourself. If you speak in that way, nothing prevents me to show me what is legal registration and how to run a company. You are flying a little high with your assumptions.
You clearly can explain me now what this means, dont you: https://github.com/O...develop/LICENSE
Maybe you operate under wrong license, I dont know, but that would be your own problem.
You mention countries which have nothing to do with registration of non commercial accounts on github, I am lost with you connecting it now. You probably speak about OpenPli, can you then explain me again what license here is: https://github.com/O...develop/LICENSE ? What has forking a repo with opensource to do with registration of a company?
First, I have already mentioned that we've noticed the new account long before we saw the post, I didn't even have the forum open at that point. No clue what you mean with the rest of your rant.
So, once again, please contact github if you do not believe that the only option you have to prevent "legal" forks is to put it private, you do not have to release it over github which you do not do anyway.
Sorry, but this just shows that you completely missed the point I have made.
I guess you simply expressed that you do not understand what I say and it is not due some language barrier.