Merge branch '4.2' into 4.3

* 4.2:
  Change wording about time for downstream projects
  Import use statement for used trait
  [Diversity] Link to the annual CoC transparency reports

Author: javiereguiluz

components/var_dumper.rst

@@ -244,10 +244,11 @@ This will provide you with two new assertions:
 Example::
 
     use PHPUnit\Framework\TestCase;
+    use Symfony\Component\VarDumper\Test\VarDumperTestTrait;
 
     class ExampleTest extends TestCase
     {
-        use \Symfony\Component\VarDumper\Test\VarDumperTestTrait;
+        use VarDumperTestTrait;
 
         public function testWithDumpEquals()
         {

contributing/code/security.rst

@@ -78,7 +78,7 @@ projects. The process works as follows:
    date for a joint release (there is no guarantee that all releases will
    be at the same time but we will try hard to make them at about the same
    time). When the issue is not known to be exploited in the wild, a period
-   of two weeks seems like a reasonable amount of time.
+   of two weeks is considered a reasonable amount of time.
 
 The list of downstream projects participating in this process is kept as small
 as possible in order to better manage the flow of confidential information

contributing/code_of_conduct/care_team.rst

@@ -4,22 +4,24 @@ CARE Team
 Our Pledge
 ----------
 
-In the interest of fostering an open and welcoming environment, the CoC Active Response Ensurers, or CARE,
-pledge to ensure that the spirit of the :doc:`Code of Conduct </contributing/code_of_conduct/index>`
+In the interest of fostering an open and welcoming environment, the "Code of
+Conduct Active Response Ensurers", or CARE team, pledge to ensure that the
+spirit of the :doc:`Code of Conduct </contributing/code_of_conduct/index>`
 is respected. Our main priority is to ensure the safety of our community members.
-The second goal is to help educate the community as a whole to be aware of the CoC
-and how to help implement its spirit throughout the community. In case these goals
-conflict, we will prioritize safety of community members over all other goals.
+The second goal is to help educate the community as a whole to be aware of the
+Code of Conduct and how to help implement its spirit throughout the community.
+In case these goals conflict, we will prioritize safety of community members
+over all other goals.
 
-If you think there is or has been a violation to the code of conduct please contact
+If you think there is or has been a violation to the Code of Conduct please contact
 the CARE team or if you prefer contact only individual members of the CARE team.
 
 Members
 -------
 
-Here are all the members of the Code of Conduct CARE team (in alphabetic order).
-You can contact any of them directly using the contact details below or you can
-also contact all of them at once by emailing **care@symfony.com**:
+Here are all the members of the CARE team (in alphabetic order). You can contact
+any of them directly using the contact details below or you can also contact all
+of them at once by emailing **care@symfony.com**:
 
 * **Emilie Lorenzo**
 
@@ -46,3 +48,12 @@ The :doc:`Symfony project leader </contributing/code/core_team>` appoints the CA
 team with candidates they see fit. The CARE team will consist of at least
 3 people. The team should be representing as many demographics as possible,
 ideally from different employers.
+
+CARE Team Transparency Reports
+------------------------------
+
+The CARE team publishes a transparency report at the end of each year:
+
+* `Symfony Code of Conduct Transparency Report 2018`_.
+
+.. _`Symfony Code of Conduct Transparency Report 2018`: https://symfony.com/blog/symfony-code-of-conduct-transparency-report-2018