Collaboration's translation problem

[paulwoman]

If I understand correctly

In the second half of August there will be some changes to the github that will prevent me from using OmegaT on it.

It seems to me that there is a temporary authentication issue but I am not sure what it is.

https://github.blog/2020-12-15-token-au ... perations/
https://sourceforge.net/p/omegat/feature-requests/1533/

If this is not the case, it will be "compulsory" to make the modifications locally and to send back online when you are finished.

There should be a system that records changes online.

Here is a template to be used to create a "repository" for collaboration.


https://github.com/paulwoman/OmegaT-base

I hope to find an "easy" solution by then.

Note : I find those information : https://docs.github.com/en/free-pro-tea ... cess-token but I can't understant what I must do

[rafaeltodero]

I hope we find a solution.

Until August, I believe OmegaT will find a solution.

[paulwoman]

Hello.

I know it's a lot of months away, but here are a few ideas on how to continue translating in collaboration with OmegaT


There is the possibilities where I am "freelance" and I "only" have to give access to the file necessary for the translation.


With a github system

• 
  https://gitlab.com/users/sign_in

I did some tests. The transfer is completely transparent.


With a drive on the cloud

1. https://partner.pcloud.com/r/39337
2. https://www.dropbox.com
3. https://www.sync.com/?_sync_refer=c05ab6f50

In the long term, the ideal would be to have a github directory in the capitalismlab server.

https://about.gitlab.com/install/

[David]

With a github system

https://gitlab.com/users/sign_in
I did some tests. The transfer is completely transparent.


With a drive on the cloud
https://partner.pcloud.com/r/39337
https://www.dropbox.com
https://www.sync.com/?_sync_refer=c05ab6f50

Does either of the above work?

In the long term, the ideal would be to have a github directory in the capitalismlab server.

https://about.gitlab.com/install/

Or the only viable solution is to install a Github on the caplab server?

Note : I find those information : https://docs.github.com/en/free-pro-tea ... cess-token but I can't understant what I must do

May I suggest that you post your question on https://stackoverflow.com/ and see if someone would answer it?

[paulwoman]

Does either of the above work?

• With a github system.

It work with Gitlab. But I don't know if there will be "one day" the same problem as with gitlab.

• With a drive on the cloud.

It work too, but the translator need install another software to add the drive in question.

Or the only viable solution is to install a Github on the caplab server?

This would indeed solve the problem. You need to have access to the GIT with a username and a password. In this way, we can be sure that important data remains as long as the "capitalismLab" site exists. This is not necessarily the case for an "external" site.

So we could imagine a system where the files that need to be modified are automatically on the GIT without my having to do it manually, but I don't know if this would be technically feasible? Unless someone on your team does it.

But I don't mind doing the verification

May I suggest that you post your question on https://stackoverflow.com/ and see if someone would answer it?

Thanks for your suggestion.

[David]

With a github system.
It work with Gitlab. But I don't know if there will be "one day" the same problem as with gitlab.

Do you mean that this works fine for now? If so, should we just use this until it announces that there will be the same problem?

If the above is not ideal, I clicked on the link you provided: https://about.gitlab.com/install/ and it states that Gitlab can be installed on AWS: https://docs.gitlab.com/ee/install/aws/

Do you like this approach? If so, perhaps you could create an AWS account and install GitLab on your side and Enlight will pay for the running cost of your AWS account. Please let me know what you think.

[paulwoman]

Do you mean that this works fine for now?

For the moment, the use of gitlab is not yet a problem.

If so, should we just use this until it announces that there will be the same problem?

We have approximately 6 months before we have to do anything. Gitlab easily copies data from github and vice versa. In the medium term, this remains the easiest and cheapest solution.

and it states that Gitlab can be installed on AWS: https://docs.gitlab.com/ee/install/aws/ Do you like this approach?

This is indeed the idea I had in mind, with the difference that I proposed that it should be on the CapitalismLab server.

If so, perhaps you could create an AWS account and install GitLab on your side and Enlight will pay for the running cost of your AWS account. Please let me know what you think.

In this eventuality, I have the site in my mind. https://www.lws-hosting.be/vps-gitlab.php

But, like I said, we can speak about that when we don't have the choise