[RFC] Replace "Symfony2 Component" by "Symfony Component"

[javiereguiluz]

Currently, documentation uses both Symfony component and Symfony2 component. In the official communication of the Symfony Project we always try to use the generic term Symfony component.

This is an important issue because Symfony3 is not that far away and when it releases, we'll have probably the same components and then the documentation will be harder to manage.

Therefore, this is my proposal (if @fabpot agrees to it): replace specific Symfony2 component by the generic Symfony component in all the official documentation (book, tutorial, cookbook, etc.)

[xabbuh]

I think that's a good idea. 👍

[fabpot]

👍 I think it's time to replace all Symfony2 occurrences to just Symfony.

[wouterj]

I agree with Fabian, we should replace all Symfony2 occurences to Symfony. Symfony2 was a big step, both for the project and for the code, but we now have to move away from "2" as a library name and to "2" as a version name. :)

[lsmith77]

I guess we should also now switch to talking about #Symfony when we talk about the project in general?

[lsmith77]

ie. on twitter etc

[masthowasli]

Big +1. Although I personally still have to maintain quite some symfony 1 code, I can just second the petition and want to urge everyone to use just Symfony. We are far away from some kind of artifical BC needs for sf1, we now have composer for management of required versions. That said, there is just one (s|S)ymfony. It was - in my opinon - leading the PHP framework world in version 1, is now leading and why should that change.

Just keep with the capital S in all searches and inquries and you should be safe in the web.

[javiereguiluz]

In the original proposal I was only thinking about the Symfony components ... but maybe it's time to drop the suffix entirely for everything.

[neemzy]

I guess so, more and more people are referring to it as just "Symfony" (and so am I, FWIW).

[weaverryan]

I've already merged #4205, which changes Symfony2 -> Symfony throughout the docs. Is there anything else this issue needs?

Thanks everyone!

[xabbuh]

ping @javiereguiluz

[javiereguiluz]

@xabbuh these are the titles that contained Symfony2 and have been switched to Symfony:

• f276e34#diff-ca59fd509743d86ee5671bfa03d59950R134
• f276e34#diff-591e54df77a3a12064ac34f6f81e8152R514
• f276e34#diff-591e54df77a3a12064ac34f6f81e8152R556
• f276e34#diff-4cef9ee150dd2e6759fe0f19caf619e8R19
• f276e34#diff-9b8432790a63aa96d7d9494ce9abc5bfR6
• f276e34#diff-8a8cfda1b69d347328e148b10c71c40aR6
• f276e34#diff-aa949034c7588357745df4fb41a3c451R7
• f276e34#diff-ea87100d0f803605a846aee3fd24b1a9R82
• f276e34#diff-401aaeb1c63d8989b7ba545741156c9eR3
• f276e34#diff-8b1777d318e140ecb3bb6bc4bee1463aR3
• f276e34#diff-8ef7ec9ab693872f5dff51917a8b0ec1R3
• f276e34#diff-77eb74e183e92ac46a3e84a0fb210513R6
• f276e34#diff-77eb74e183e92ac46a3e84a0fb210513R17
• f276e34#diff-77eb74e183e92ac46a3e84a0fb210513R36
• f276e34#diff-753fc5551f127c167882f9b8f731cbe1R6
• f276e34#diff-909f80262ed3213f1e129a0159b394b6R6
• f276e34#diff-db4b047b30ffef7855b12b527860ac2cR3
• f276e34#diff-40a51d4deee33105cb6b2647ccef9edaR13
• f276e34#diff-40a51d4deee33105cb6b2647ccef9edaR46
• f276e34#diff-5d03fe3403d0a19af76d057e8ca46d12R6
• f276e34#diff-430dc9675fe0251899458375e09cb2dbR6

Does this change mean that all the URLs that pointed to those titles are broken?

[xabbuh]

@javiereguiluz If I didn't miss one, all of these headlines now have an explicit label reflecting the old headline. For example, the new, automatically generated anchor for the first example is symfony-reverse-proxy. However, because of the explicit label, using the old anchor symfony2-reverse-proxy is still working.

[javiereguiluz]

@xabbuh you are right! The old anchors have been maintained, so there should be no problem at all. Thanks for your work!

This issue can now be closed.