@@ -16,9 +16,6 @@ Contributing
16
16
First, become familiar with the :doc: `markup language </contributing/documentation/format >`
17
17
used by the documentation.
18
18
19
- Then, subscribe to the `Symfony docs mailing-list `_, as collaboration happens
20
- there.
21
-
22
19
Finally, find the *master * repository for the language you want to contribute
23
20
for. Here is the list of the official *master * repositories:
24
21
@@ -39,7 +36,6 @@ Joining the Translation Team
39
36
If you want to help translating some documents for your language or fix some
40
37
bugs, consider joining us; it's a very easy process:
41
38
42
- * Introduce yourself on the `Symfony docs mailing-list `_;
43
39
* *(optional) * Ask which documents you can work on;
44
40
* Fork the *master * repository for your language (click the "Fork" button on
45
41
the GitHub page);
@@ -59,8 +55,8 @@ Adding a new Language
59
55
This section gives some guidelines for starting the translation of the
60
56
Symfony documentation for a new language.
61
57
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.
64
60
65
61
When the team is ready, nominate a team manager; they will be responsible for
66
62
the *master * repository.
@@ -89,4 +85,3 @@ repository and apply changes to the translated documents as soon as possible.
89
85
repositories as obsolete documentation is dangerous.
90
86
91
87
.. _`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