Rename repository

[bakura10]

Hi @Ocramius ,

For homogeneity purpose with how composer name packages, I think it would be a good idea to rename the GitHub project from "DoctrineModule" to "doctrine-module". I tried it with my own projects, it's absolutely painless, it breaks nothing (even the old URL is redirected to the new one). It just provides more homogeneity and it seems like some projects like Doctrine adopte this (as well as zf itself).

(I'm not going to raise in issue but the same applies for DoctrineModuleORMModule, DoctrineModuleMongo...)

EDIT : in fact, the composer package canonical also needs to be updated on Packagist.

[Ocramius]

@bakura10 that's a perfectly fine request by me - we're already doing this for ORM, so let's wait and see how that turns out.

I don't see anything against it, but it's not a priority now

[bakura10]

Nice. In fact it's pretty easy. Basically the only pain is that people will just need to rename their remote branches in git (I think).

[Ocramius]

@bakura10 I think github handles that, no?

[bakura10]

Maybe! AT least the links to the repo still work.

[superdweebie]

+1

[bakura10]

For information, here are the steps I needed to do to make it work correctly:

1. Remove the module from modules.zendframework.com
2. Rename the repository on GitHub.
3. Optionally change the name on composer.json here (https://github.com/doctrine/DoctrineModule/blob/master/composer.json#L6) but that's not needed here as it does not point to GitHub.
4. Log into Packagist and manually update the link.
5. Readd the module to modules.zendframework.com

All the forks will still point to the new name without any breaks.

[danizord]

The only problem will be broken links =/

[bakura10]

No, github does redirections.

Envoyé de mon iPhone

Le 21 mai 2013 à 02:46, Daniel Gimenes [email protected] a écrit :

The only problem will be broken links =/

—
Reply to this email directly or view it on GitHub.

[danizord]

So looks perfect (: