Closed (fixed)
Project:
Migrate Upgrade
Version:
8.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
6 Jun 2014 at 21:55 UTC
Updated:
5 Jan 2015 at 17:34 UTC
Jump to comment: Most recent
Comments
Comment #1
mikeryan"original"? Anyone have any thoughts? I don't have a strong preference myself...
Comment #2
wusel commentedAnother wording:
"site to import" and "database to import".
Comment #3
hussainwebI use source or legacy interchangingly as the situation demands. In database spec, I use 'legacy' whereas when talking about it, I use the word 'source'.
Given the general meaning of the word 'migrate', I think 'source' is more apt to describe the place from where the data moves.
Comment #4
benjy commented+1 for source from me.
Comment #5
bdone commentedif it's a vote, +1 for source :)
Comment #6
wusel commentedOk, "source" is correct in code. I agree fully.
But please think on the UI (user interface) as a UI. This is, what we see, when we want to upgrate from D6 or D7 to D8.
There may be many people, which have to change e.g. from D6 to D8. They run D6 for years without changes. Now (in 2015) they have to use the new (thanks!) migration.
Did they know, what is "source"? Or can it be better, to change the wording in the UI?
Could they understand "site to import" and "database to import" or "site to upgrate" and "database to upgrate" in the UI?
Wusel
Adding:
This is an import and not an upgrate! The old database does not change during the migration. If we upgrate e.g. from D6 to D7, then the old database is after the upgrate the "new" database. This is a difference!
Comment #7
hussainwebThis might be a cultural thing but I feel that "source database" is the most apt phrase out of the options we have (or that I can think of). I like the phrase "site to import" or "site to upgrade" even though it is a mouthful, but I think it might be confusing as site might mean different things. We could probably say "Address of the site to import", but that is too much and we are saying as much in the description anyway.
Between "site to import" and "site to upgrade", I would prefer the "import" version as "upgrade" somewhat suggests that the upgrade will be made on the same database, which is misleading.
My preference in order:
Comment #8
piyushpoddar commented+1 for source.
Comment #9
mohit_aghera commentedI will go for "Source". As it is more meaningful from migration perspective.
Comment #10
gargsuchi commentedSource database makes most sense for me.
Comment #11
Anonymous (not verified) commentedSource makes the most sense. However, I noticed that in Drush we have had the word "legacy" for the db connection now. I don't agree with the use of the term legacy, but it is something to be aware of.
Example:
--legacy-db-url=mysql://d6:@localhost/d6Comment #12
mikeryan"Source" is the consensus. See https://github.com/drush-ops/drush/issues/724 for why drush says --legacy-db-url.