Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment is tied to the TransforMap namespace #1

Open
almereyda opened this issue Feb 9, 2017 · 3 comments
Open

Deployment is tied to the TransforMap namespace #1

almereyda opened this issue Feb 9, 2017 · 3 comments

Comments

@almereyda
Copy link
Member

Weblate itself is an agnostic platform for string translation, which doesn't neccessarily link to the GIS functionalities of the TransforMap stack.

I am suggesting to move this from TransforMap to allmende.io and redeploy at weblate.allmende.io.

Do you support this idea @species @josefkreitmayer @gandhiano ?

@josefkreitmayer
Copy link
Member

With the current deployment being in use from the SSEDAS partners, translating their menu-interface, I currently do not support the idea.

After the full closing of SSEDAS feature development in the 2nd half of 2017, we can set and communicate a final date for the partners to translate. After that I would be fine with moving to a community-managed body. I would not support the idea to move it to the single authority of an individual.

I wonder about weblate.ecobytes.net? Or is allmende.io going to be part of ecobytes anyway?

@almereyda
Copy link
Member Author

Yes, allmende.io is part of Ecobytes.

@almereyda
Copy link
Member Author

Now they are separated:

A redirect will be provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants