move doctrine migrations away from src

[ro0NL]

it was briefly discussed here #172 (comment), but seems to be ignored eventually

i like to propose to move src/Migrations to migrations/. I dont understand why we are moving mountains to keep it in src (extra config etc.) :/ is there any technical blocker to not move it away from src?

semantically it does not belong in src IMHO.

(https://www.tomasvotruba.cz/blog/2019/12/23/5-things-i-improve-when-i-get-to-new-repository/#3-move-code-to-src)

[ogizanagi]

I'm already doing this for all of my projects. So 👍 from me.

[ro0NL]

alternatively to introduce a more generic/reusable directory in our landscape: ./scripts/database-migrations/? But im not sure it's valid UNIX style let's say.

We should carefully think about root directories though, at some point it gets out of control.

[ogizanagi]

The more generic/reusable proposition was made a long-time ago, but without enough traction/consensus to happen: a res directory which would contain any resources used by the app, i.e:

• migrations
• assets
• fixtures
• templates
• docs
• translations
• ...

[ro0NL]

i like res 😍 can we do that? please? 😁

[yceruto]

I like migrations/ at the root too 👍

[ro0NL]

@javiereguiluz ive reread the issue real quick, fair enough :) the ship has sailed. I still think it's more concise in general, but 👍 for many root dirs tied to SF, in a SF specific project dir.

[dmaicher]

Also related discussion: https://github.com/doctrine/DoctrineMigrationsBundle/pull/295/files#r362401350