diff --git a/mass_mailing_event_registration_exclude/README.rst b/mass_mailing_event_registration_exclude/README.rst
index d16302827..90f0652ee 100644
--- a/mass_mailing_event_registration_exclude/README.rst
+++ b/mass_mailing_event_registration_exclude/README.rst
@@ -17,20 +17,20 @@ Mass mailing event
:target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
:alt: License: AGPL-3
.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fsocial-lightgray.png?logo=github
- :target: https://github.com/OCA/social/tree/16.0/mass_mailing_event_registration_exclude
+ :target: https://github.com/OCA/social/tree/17.0/mass_mailing_event_registration_exclude
:alt: OCA/social
.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
- :target: https://translation.odoo-community.org/projects/social-16-0/social-16-0-mass_mailing_event_registration_exclude
+ :target: https://translation.odoo-community.org/projects/social-17-0/social-17-0-mass_mailing_event_registration_exclude
:alt: Translate me on Weblate
.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png
- :target: https://runboat.odoo-community.org/builds?repo=OCA/social&target_branch=16.0
+ :target: https://runboat.odoo-community.org/builds?repo=OCA/social&target_branch=17.0
:alt: Try me on Runboat
|badge1| |badge2| |badge3| |badge4| |badge5|
This module links ``mass_mailing`` with ``event`` in order to exclude
-recipients that are already registered, confirmed, cancelled, attended, or a
-combination of these states, when the mass mailing is sent.
+recipients that are already registered, confirmed, cancelled, attended,
+or a combination of these states, when the mass mailing is sent.
**Table of contents**
@@ -40,21 +40,19 @@ combination of these states, when the mass mailing is sent.
Usage
=====
-In a mass mailing, users can set an event related and exclude the recipients who
-have an email address already registered in that event.
+In a mass mailing, users can set an event related and exclude the
+recipients who have an email address already registered in that event.
This is useful in this scenario:
-1. Create a mass mailing for telling to 1000 partners that a new event is
-available.
-2. During a week some of them (50) have been registered in the event
-3. Then, a week after the first mass mailing, duplicate it to get a second
-mass mailing. Relate this one to the event and exclude the registered emails.
-Change the message body to remember that early bird period is going to expire
-soon.
-4. Send the second mass mailing and registered emails are automatically excluded,
-So it's been only sent to 950 partners the ones who are not registered in the
-event yet.
+1. Create a mass mailing for telling to 1000 partners that a new event
+is available. 2. During a week some of them (50) have been registered in
+the event 3. Then, a week after the first mass mailing, duplicate it to
+get a second mass mailing. Relate this one to the event and exclude the
+registered emails. Change the message body to remember that early bird
+period is going to expire soon. 4. Send the second mass mailing and
+registered emails are automatically excluded, So it's been only sent to
+950 partners the ones who are not registered in the event yet.
Bug Tracker
===========
@@ -62,7 +60,7 @@ Bug Tracker
Bugs are tracked on `GitHub Issues `_.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomed
-`feedback `_.
+`feedback `_.
Do not contact contributors directly about support or help with technical issues.
@@ -70,23 +68,23 @@ Credits
=======
Authors
-~~~~~~~
+-------
* Tecnativa
Contributors
-~~~~~~~~~~~~
+------------
-* `Tecnativa `__:
+- `Tecnativa `__:
- * Antonio Espinosa
- * David Vidal
- * Alexandre D. Díaz
- * Stefan Ungureanu
- * Carolina Fernandez
+ - Antonio Espinosa
+ - David Vidal
+ - Alexandre D. Díaz
+ - Stefan Ungureanu
+ - Carolina Fernandez
Maintainers
-~~~~~~~~~~~
+-----------
This module is maintained by the OCA.
@@ -98,6 +96,6 @@ OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.
-This module is part of the `OCA/social `_ project on GitHub.
+This module is part of the `OCA/social `_ project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
diff --git a/mass_mailing_event_registration_exclude/pyproject.toml b/mass_mailing_event_registration_exclude/pyproject.toml
new file mode 100644
index 000000000..4231d0ccc
--- /dev/null
+++ b/mass_mailing_event_registration_exclude/pyproject.toml
@@ -0,0 +1,3 @@
+[build-system]
+requires = ["whool"]
+build-backend = "whool.buildapi"
diff --git a/mass_mailing_event_registration_exclude/readme/CONTRIBUTORS.md b/mass_mailing_event_registration_exclude/readme/CONTRIBUTORS.md
new file mode 100644
index 000000000..d197cb977
--- /dev/null
+++ b/mass_mailing_event_registration_exclude/readme/CONTRIBUTORS.md
@@ -0,0 +1,7 @@
+- [Tecnativa](https://www.tecnativa.com):
+
+ > - Antonio Espinosa
+ > - David Vidal
+ > - Alexandre D. Díaz
+ > - Stefan Ungureanu
+ > - Carolina Fernandez
diff --git a/mass_mailing_event_registration_exclude/readme/CONTRIBUTORS.rst b/mass_mailing_event_registration_exclude/readme/CONTRIBUTORS.rst
deleted file mode 100644
index 06a907b56..000000000
--- a/mass_mailing_event_registration_exclude/readme/CONTRIBUTORS.rst
+++ /dev/null
@@ -1,7 +0,0 @@
-* `Tecnativa `__:
-
- * Antonio Espinosa
- * David Vidal
- * Alexandre D. Díaz
- * Stefan Ungureanu
- * Carolina Fernandez
diff --git a/mass_mailing_event_registration_exclude/readme/DESCRIPTION.md b/mass_mailing_event_registration_exclude/readme/DESCRIPTION.md
new file mode 100644
index 000000000..ea1f5e5f7
--- /dev/null
+++ b/mass_mailing_event_registration_exclude/readme/DESCRIPTION.md
@@ -0,0 +1,3 @@
+This module links `mass_mailing` with `event` in order to exclude
+recipients that are already registered, confirmed, cancelled, attended,
+or a combination of these states, when the mass mailing is sent.
diff --git a/mass_mailing_event_registration_exclude/readme/DESCRIPTION.rst b/mass_mailing_event_registration_exclude/readme/DESCRIPTION.rst
deleted file mode 100644
index 63fc11e50..000000000
--- a/mass_mailing_event_registration_exclude/readme/DESCRIPTION.rst
+++ /dev/null
@@ -1,3 +0,0 @@
-This module links ``mass_mailing`` with ``event`` in order to exclude
-recipients that are already registered, confirmed, cancelled, attended, or a
-combination of these states, when the mass mailing is sent.
diff --git a/mass_mailing_event_registration_exclude/readme/USAGE.md b/mass_mailing_event_registration_exclude/readme/USAGE.md
new file mode 100644
index 000000000..006483c82
--- /dev/null
+++ b/mass_mailing_event_registration_exclude/readme/USAGE.md
@@ -0,0 +1,13 @@
+In a mass mailing, users can set an event related and exclude the
+recipients who have an email address already registered in that event.
+
+This is useful in this scenario:
+
+1\. Create a mass mailing for telling to 1000 partners that a new event
+is available. 2. During a week some of them (50) have been registered in
+the event 3. Then, a week after the first mass mailing, duplicate it to
+get a second mass mailing. Relate this one to the event and exclude the
+registered emails. Change the message body to remember that early bird
+period is going to expire soon. 4. Send the second mass mailing and
+registered emails are automatically excluded, So it's been only sent to
+950 partners the ones who are not registered in the event yet.
diff --git a/mass_mailing_event_registration_exclude/readme/USAGE.rst b/mass_mailing_event_registration_exclude/readme/USAGE.rst
deleted file mode 100644
index cd99552d8..000000000
--- a/mass_mailing_event_registration_exclude/readme/USAGE.rst
+++ /dev/null
@@ -1,15 +0,0 @@
-In a mass mailing, users can set an event related and exclude the recipients who
-have an email address already registered in that event.
-
-This is useful in this scenario:
-
-1. Create a mass mailing for telling to 1000 partners that a new event is
-available.
-2. During a week some of them (50) have been registered in the event
-3. Then, a week after the first mass mailing, duplicate it to get a second
-mass mailing. Relate this one to the event and exclude the registered emails.
-Change the message body to remember that early bird period is going to expire
-soon.
-4. Send the second mass mailing and registered emails are automatically excluded,
-So it's been only sent to 950 partners the ones who are not registered in the
-event yet.
diff --git a/mass_mailing_event_registration_exclude/static/description/index.html b/mass_mailing_event_registration_exclude/static/description/index.html
index 1d8db0e3c..cc37f2e8c 100644
--- a/mass_mailing_event_registration_exclude/static/description/index.html
+++ b/mass_mailing_event_registration_exclude/static/description/index.html
@@ -1,4 +1,3 @@
-
@@ -369,10 +368,10 @@ ul.auto-toc {
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! source digest: sha256:a2fd89c0a593672ecc127e763e00e1602b770b4b305eae54e779ff71d091f321
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
-

+

This module links mass_mailing with event in order to exclude
-recipients that are already registered, confirmed, cancelled, attended, or a
-combination of these states, when the mass mailing is sent.
+recipients that are already registered, confirmed, cancelled, attended,
+or a combination of these states, when the mass mailing is sent.
Table of contents
@@ -388,26 +387,24 @@ combination of these states, when the mass mailing is sent.
-
In a mass mailing, users can set an event related and exclude the recipients who
-have an email address already registered in that event.
+
In a mass mailing, users can set an event related and exclude the
+recipients who have an email address already registered in that event.
This is useful in this scenario:
-
1. Create a mass mailing for telling to 1000 partners that a new event is
-available.
-2. During a week some of them (50) have been registered in the event
-3. Then, a week after the first mass mailing, duplicate it to get a second
-mass mailing. Relate this one to the event and exclude the registered emails.
-Change the message body to remember that early bird period is going to expire
-soon.
-4. Send the second mass mailing and registered emails are automatically excluded,
-So it’s been only sent to 950 partners the ones who are not registered in the
-event yet.
+
1. Create a mass mailing for telling to 1000 partners that a new event
+is available. 2. During a week some of them (50) have been registered in
+the event 3. Then, a week after the first mass mailing, duplicate it to
+get a second mass mailing. Relate this one to the event and exclude the
+registered emails. Change the message body to remember that early bird
+period is going to expire soon. 4. Send the second mass mailing and
+registered emails are automatically excluded, So it’s been only sent to
+950 partners the ones who are not registered in the event yet.
Bugs are tracked on GitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomed
-feedback.
+
feedback.
Do not contact contributors directly about support or help with technical issues.
@@ -441,7 +438,7 @@ If you spotted it first, help us to smash it by providing a detailed and welcome
OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.
-
This module is part of the OCA/social project on GitHub.
+
This module is part of the OCA/social project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.