@@ -16,9 +16,6 @@ Contributing
1616First, become familiar with the :doc: `markup language </contributing/documentation/format >`
1717used by the documentation.
1818
19- Then, subscribe to the `Symfony docs mailing-list `_, as collaboration happens
20- there.
21-
2219Finally, find the *master * repository for the language you want to contribute
2320for. Here is the list of the official *master * repositories:
2421
@@ -39,7 +36,6 @@ Joining the Translation Team
3936If you want to help translating some documents for your language or fix some
4037bugs, consider joining us; it's a very easy process:
4138
42- * Introduce yourself on the `Symfony docs mailing-list `_;
4339* *(optional) * Ask which documents you can work on;
4440* Fork the *master * repository for your language (click the "Fork" button on
4541 the GitHub page);
@@ -59,8 +55,8 @@ Adding a new Language
5955This section gives some guidelines for starting the translation of the
6056Symfony documentation for a new language.
6157
62- As starting a translation is a lot of work, talk about your plan on the
63- ` Symfony docs mailing-list `_ and try to find motivated people willing to help.
58+ As starting a translation is a lot of work, try to find motivated people
59+ willing to help.
6460
6561When the team is ready, nominate a team manager; they will be responsible for
6662the *master * repository.
@@ -89,4 +85,3 @@ repository and apply changes to the translated documents as soon as possible.
8985 repositories as obsolete documentation is dangerous.
9086
9187.. _`an ongoing discussion` : https://github.com/symfony/symfony-docs/issues/4078
92- .. _Symfony docs mailing-list : https://groups.google.com/forum/#!forum/symfony-docs
0 commit comments