I sugest naming the composer package same as the repository name

[paveljanda]

It is cleaner and people won't get confused when searching for particular repo. :)

[f3l1x]

Do you mean contributte/psr7-http-message?

[paveljanda]

Either that or moving github.com/contributte/psr7-http-message to github.com/contributte/psr7.

[f3l1x]

You're right, but I was thinking that name of the this repo is better reflected with full name of this PSR (seo / search / newbies), rather then in composer where you probably know what you're doing.

@matyx What do you think?

[paveljanda]

I'm used to search for/know composer packages by name and then looking for the documentation directly by typing github.com/<composer-package-name> into the address bar..

Look, you will have for about 150 repos in contributte namespace in following year. :D Maybe there will be some of them holding the name PSR-7 (PSR-7 is so cool these days..). How should one know, which one is associated with target composer package?

I understand the SEO reason. You can make the composer name contributte/psr7-http-message then. :P

[f3l1x]

I'll rename it to psr7-http-message, agreed. :taco: :+1:

[f3l1x]

Lol, 150 repos :-D

[matyx]

I agree with @paveljanda. I often go directly to github as Pavel does

[adaamz]

close?

[f3l1x]

Closed @CZechBoY

[mabar]

@paveljanda Only 130 repos in Contributte, Apitte, Nettrine, Dockette and Ninjify together 😥