Added a new section with recommendations for Composer

javiereguiluz · javiereguiluz · commit 7bf1a4c1df16 · 2015-03-03T09:58:33.000+01:00
diff --git a/cookbook/bundles/best_practices.rst b/cookbook/bundles/best_practices.rst
@@ -319,8 +319,7 @@ Services
 --------
 
 If the bundle defines services, they must be prefixed with the bundle alias.
-For an AcmeBlogBundle for instance, all services must be prefixed with
-``acme_blog``.
+For example, AcmeBlogBundle services must be prefixed with ``acme_blog``.
 
 In addition, services not meant to be used by the application directly, should
 be :ref:`defined as private <container-private-services>`.
@@ -330,6 +329,21 @@ be :ref:`defined as private <container-private-services>`.
     You can learn much more about service loading in bundles reading this article:
     :doc:`How to Load Service Configuration inside a Bundle </cookbook/bundles/extension>`.
 
+Composer Metadata
+-----------------
+
+The ``composer.json`` file should include at least the following metadata:
+
+* ``name``, which includes the vendor and the short bundle name. If you are
+  releasing the bundle on your own instead of on behalf of a company, use your
+  personal name (e.g. ``johnsmith/blog-bundle``). The bundle short name excludes
+  the vendor name and separates each word with an hyphen. For example:
+  ``AcmeBlogBundle`` is transformed into ``blog-bundle`` and ``AcmeSocialConnectBundle``
+  is transformed into ``acme-social-bundle``;
+* ``description``, a brief explanation of the purpose of the bundle;
+* ``type``, use the ``symfony-bundle`` value;
+* ``license``, use the ``MIT`` value.
+
 Learn more from the Cookbook
 ----------------------------
 
