Editing questions
-
Hi,
I'm taking a look at different sections in the Docs. If I have a question about wording, do you prefer that I ask here in the Forum, or should I edit the proposed changes and let any discussion happen through comments in the repository?For example, under Apps -> Location, the wording makes it sounds like actual data is going to be moved. But, no images "move" per se, its just that the app is assigned a new domain name.
No data loss Moving an app to a new location is a non-destructive action. Existing app data will be migrated to the new domain.So, it sounds clearer to have something like
No data loss Changing the domain of an app is a non-destructive action. No app data is migrated. The only thing that changes is the assigned domain name and any mention of it in env files of the Docker images.So, better to post these kinds of questions here, or in the repository?
-
This is the correct place for such discussions
From your post, it looks like the the
Locationis what might be confusing here. Not sure if this is a language thing and if the technical term ofDomainmight be more appropriate here. I guess we always had the intention to not be too technical from the start, which thus ended up as Location instead of Domain here, but given the user-base of Cloudron, which anyways requires some level of technical know-how, I would be totally ok to change the wording there, if we can get some consensus here on what is more descriptive.Also just to mention here, this is kinda a bit up to the translation for non English language settings already.
-
This is the correct place for such discussions
From your post, it looks like the the
Locationis what might be confusing here. Not sure if this is a language thing and if the technical term ofDomainmight be more appropriate here. I guess we always had the intention to not be too technical from the start, which thus ended up as Location instead of Domain here, but given the user-base of Cloudron, which anyways requires some level of technical know-how, I would be totally ok to change the wording there, if we can get some consensus here on what is more descriptive.Also just to mention here, this is kinda a bit up to the translation for non English language settings already.
-
This is the correct place for such discussions
From your post, it looks like the the
Locationis what might be confusing here. Not sure if this is a language thing and if the technical term ofDomainmight be more appropriate here. I guess we always had the intention to not be too technical from the start, which thus ended up as Location instead of Domain here, but given the user-base of Cloudron, which anyways requires some level of technical know-how, I would be totally ok to change the wording there, if we can get some consensus here on what is more descriptive.Also just to mention here, this is kinda a bit up to the translation for non English language settings already.
-
@scooke said in Editing questions:
Moving an app to a new location is a non-destructive action. Existing app data will be migrated to the new domain.
"Moving an app to a new location is a non-destructive action. Existing app data will be assigned to the new domain."
I can't think of any question up to this point from anyone about this specifically, so in that sense it isn't a problem. But the idea that data "moves" when it's the domain that changes isn't accurate. My inner editor.
A life lived in fear is a life half-lived
-
@scooke said in Editing questions:
Moving an app to a new location is a non-destructive action. Existing app data will be migrated to the new domain.
"Moving an app to a new location is a non-destructive action. Existing app data will be assigned to the new domain."
I can't think of any question up to this point from anyone about this specifically, so in that sense it isn't a problem. But the idea that data "moves" when it's the domain that changes isn't accurate. My inner editor.
@scooke said in Editing questions:
"Moving an app to a new location is a non-destructive action. Existing app data will be assigned to the new domain."
It's not the data, it's the new domain that is assigned to the same data location. No?
-
@scooke said in Editing questions:
"Moving an app to a new location is a non-destructive action. Existing app data will be assigned to the new domain."
It's not the data, it's the new domain that is assigned to the same data location. No?
@robi True.
My personal stance on editing is to try to keep to the original wording/word order as much as possible, especially if I had no hand in the original. So using "applied", rather than rephrasing the entire sentence, is part of that approach. In past conversations in other contexts ppl have told me how discouraging it is to have their sincere efforts to write clearly in a language that isn't their mother tongue totally erased and deleted by a "new" teammate, or editor, or volunteer, and especially whatever a user like myself might be called. The edited text might end up being totally different, but that is best achieved with everyone's involvement and discussion.
A life lived in fear is a life half-lived
-
@robi True.
My personal stance on editing is to try to keep to the original wording/word order as much as possible, especially if I had no hand in the original. So using "applied", rather than rephrasing the entire sentence, is part of that approach. In past conversations in other contexts ppl have told me how discouraging it is to have their sincere efforts to write clearly in a language that isn't their mother tongue totally erased and deleted by a "new" teammate, or editor, or volunteer, and especially whatever a user like myself might be called. The edited text might end up being totally different, but that is best achieved with everyone's involvement and discussion.
-
@scooke said in Editing questions:
Moving an app to a new location is a non-destructive action. Existing app data will be migrated to the new domain.
"Moving an app to a new location is a non-destructive action. Existing app data will be assigned to the new domain."
I can't think of any question up to this point from anyone about this specifically, so in that sense it isn't a problem. But the idea that data "moves" when it's the domain that changes isn't accurate. My inner editor.
@scooke said in Editing questions:
"Moving an app to a new location is a non-destructive action. Existing app data will be assigned to the new domain."
I would say :
"Changing an app's domain name (address) to a new one is not destructive. All data of your existing app will be moved to the new domain as well."As simple as that.
-
To me this seems like there is no clarity around domain vs storage location. We have two "locations" here. One is the external referenced location, which is the domain, where the app and thus the data is reachable. The second is the actual internal storage of data, which can be in various locations, like filesystem or database.
So the original inquiry here, at least to me, is mostly about the feeling that "Location" is somewhat related to data location internally within the server? The latter point would be the "Storage" tab in the app's configure view.
I personally would have never thought of changing the domain of an app to have any relation to destruction or losing of data, which to me makes this harder to understand. The domain for me is more like a public pointer.
I am more than happy to change the wording accordingly, we don't need to workaround here to limit the changes in wording.
