Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
javiereguiluz opened this issue Sep 5, 2014 · 15 comments
Closed

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

javiereguiluz opened this issue Sep 5, 2014 · 15 comments

Comments

@javiereguiluz
Copy link
Member

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
Copy link
Member

xabbuh commented Sep 5, 2014

I think that's a good idea. 👍

@fabpot
Copy link
Member

fabpot commented Sep 5, 2014

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

@wouterj
Copy link
Member

wouterj commented Sep 5, 2014

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
Copy link
Contributor

lsmith77 commented Sep 5, 2014

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

@lsmith77
Copy link
Contributor

lsmith77 commented Sep 5, 2014

ie. on twitter etc

@masthowasli
Copy link

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
Copy link
Member Author

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
Copy link

neemzy commented Sep 5, 2014

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

@weaverryan
Copy link
Member

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

Thanks everyone!

weaverryan added a commit that referenced this issue Sep 15, 2014
This PR was merged into the 2.3 branch.

Discussion
----------

replace "Symfony2" with "Symfony"

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | all
| Fixed tickets | #4203

Commits
-------

3ba3d27 replace "Symfony2" with "Symfony"
@xabbuh
Copy link
Member

xabbuh commented Sep 17, 2014

ping @javiereguiluz

@xabbuh
Copy link
Member

xabbuh commented Sep 17, 2014

@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
Copy link
Member Author

@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.

@xabbuh
Copy link
Member

xabbuh commented Sep 18, 2014

@javiereguiluz Thanks for your feedback. I'm going to close this (btw. I'm just wondering if you didn't have the permission to close the issue).

@xabbuh xabbuh closed this as completed Sep 18, 2014
@javiereguiluz
Copy link
Member Author

@xabbuh I don't remember if I had the permission to close the issue ... but in any case, I prefer to defer all the issue management to the three of you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants