From c7fba2aee03eebc6ad0e4163f952e640f108112f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20Biron?= Date: Wed, 5 Jun 2024 15:59:25 +0200 Subject: [PATCH 1/9] Add how to publish a memo --- config/_default/params.yaml | 1 + content/memos/how-to-publish-a-memo.md | 23 +++++++++++++++++++++++ 2 files changed, 24 insertions(+) create mode 100644 content/memos/how-to-publish-a-memo.md diff --git a/config/_default/params.yaml b/config/_default/params.yaml index f48d499..dc91243 100644 --- a/config/_default/params.yaml +++ b/config/_default/params.yaml @@ -3,3 +3,4 @@ github: mastodon: url: https://mastodon.lescommuns.org/@opentermsarchive username: "@opentermsarchive@mastodon.lescommuns.org" +email: contact@opentersmarchive.org diff --git a/content/memos/how-to-publish-a-memo.md b/content/memos/how-to-publish-a-memo.md new file mode 100644 index 0000000..c05041f --- /dev/null +++ b/content/memos/how-to-publish-a-memo.md @@ -0,0 +1,23 @@ +--- +title: "How to publish a memo" +--- + +# How to publish a memo + +This guide will help you publish a memo on [opentermsarchive.org/en/memos](https://opentermsarchive.org/en/memos/). No special computer skills are required to achieve this. + +## Prerequisites + +- A drafted memo compliant with the [writing reference]({{< relref "/memos/writing-reference" >}}). + +## 1. Sending + +Send your memo to [{{< param email >}}](mailto:{{< param email >}}?subject=Publish%20a%20memo) by attaching it to the body of the email or as a file attachment. Please feel free to add any comments or questions you may have about the content or format. + +## 2. Reviewing + +The Open Terms Archive core team will review your memo as quickly as possible. If necessary, we will suggest changes and discuss them with you. Note that review times may vary depending on the number of changes required, the speed of exchanges, and the availability of reviewers. If you do not hear from us within two weeks, please do not hesitate to contact us again by the means of your choice. + +## 3. Promoting + +Once the technical team has published your memo on [opentermsarchive.org/en/memos](https://opentermsarchive.org/en/memos/), we will inform you and provide you with the URL address for your memo. You should then promote it through the media and to the people you consider appropriate. Whenever possible, we suggest associating the hashtag `#TermsSpotting` with your memo promotions. From bdfe3cd80e8af7c526ee14f13d393072e44e09ae Mon Sep 17 00:00:00 2001 From: Matti Schneider Date: Mon, 10 Jun 2024 17:05:12 +0200 Subject: [PATCH 2/9] Improve copywriting --- content/memos/how-to-publish-a-memo.md | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/content/memos/how-to-publish-a-memo.md b/content/memos/how-to-publish-a-memo.md index c05041f..42ebc93 100644 --- a/content/memos/how-to-publish-a-memo.md +++ b/content/memos/how-to-publish-a-memo.md @@ -4,20 +4,24 @@ title: "How to publish a memo" # How to publish a memo -This guide will help you publish a memo on [opentermsarchive.org/en/memos](https://opentermsarchive.org/en/memos/). No special computer skills are required to achieve this. +This guide will help you publish a memo on [opentermsarchive.org/en/memos](https://opentermsarchive.org/en/memos/). + +No technical skills are required. ## Prerequisites - A drafted memo compliant with the [writing reference]({{< relref "/memos/writing-reference" >}}). -## 1. Sending +## 1. Send + +Send your memo to [{{< param email >}}](mailto:{{< param email >}}?subject=Publish%20a%20memo) by writing it in the body of the email or as a file attachment. Feel free to add any comments or questions you may have about the content or format. -Send your memo to [{{< param email >}}](mailto:{{< param email >}}?subject=Publish%20a%20memo) by attaching it to the body of the email or as a file attachment. Please feel free to add any comments or questions you may have about the content or format. +## 2. Review -## 2. Reviewing +The Open Terms Archive core team will review your memo as quickly as possible. -The Open Terms Archive core team will review your memo as quickly as possible. If necessary, we will suggest changes and discuss them with you. Note that review times may vary depending on the number of changes required, the speed of exchanges, and the availability of reviewers. If you do not hear from us within two weeks, please do not hesitate to contact us again by the means of your choice. +If necessary, we will suggest changes and discuss them with you. Note that review times may vary depending on the number of changes required, the speed of exchanges, and the availability of reviewers. If you do not hear from us within two weeks, please do not hesitate to contact us again by the means of your choice. -## 3. Promoting +## 3. Promote -Once the technical team has published your memo on [opentermsarchive.org/en/memos](https://opentermsarchive.org/en/memos/), we will inform you and provide you with the URL address for your memo. You should then promote it through the media and to the people you consider appropriate. Whenever possible, we suggest associating the hashtag `#TermsSpotting` with your memo promotions. +Once the core team has published your memo on [opentermsarchive.org/en/memos](https://opentermsarchive.org/en/memos/), we will inform you and provide you with the URL address of your memo. You should then promote it through the media and to the people you consider appropriate. Whenever possible, please associate the hashtag `#TermsSpotting` with your memo promotion, in order to provide visibility to the overall Open Terms Archive project and analysis. From 0e853f8ab01e1ce8a43a4e1bdf3becfd44cb1e19 Mon Sep 17 00:00:00 2001 From: Matti Schneider Date: Mon, 10 Jun 2024 17:09:05 +0200 Subject: [PATCH 3/9] Add memo email content --- content/memos/how-to-publish-a-memo.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/memos/how-to-publish-a-memo.md b/content/memos/how-to-publish-a-memo.md index 42ebc93..f38a70c 100644 --- a/content/memos/how-to-publish-a-memo.md +++ b/content/memos/how-to-publish-a-memo.md @@ -14,7 +14,7 @@ No technical skills are required. ## 1. Send -Send your memo to [{{< param email >}}](mailto:{{< param email >}}?subject=Publish%20a%20memo) by writing it in the body of the email or as a file attachment. Feel free to add any comments or questions you may have about the content or format. +Send your memo to [{{< param email >}}](mailto:{{< param email >}}?subject=Publish%20a%20memo&body=Dear%20Core%20team%2C%0A%0AI%20would%20like%20to%20publish%20the%20memo%20below.%0A%0AIt%20is%20based%20on%20my%20original%20work%2C%20and%20I%20have%20reviewed%20the%20reference%20at%20docs.opentermsarchive.org%2Fmemos%2Fwriting-reference%2F%20and%20I%20have%20made%20sure%20the%20content%20complies%20with%20it%20before%20sending%20this%20text%20to%20you.%0A%0AI%20understand%20that%20it%20might%20take%20up%20to%20two%20weeks%20for%20this%20text%20to%20be%20reviewed.%0A%0AHave%20a%20good%20day%21) by writing it in the body of the email or as a file attachment. Feel free to add any comments or questions you may have about the content or format. ## 2. Review From 363ab2ab69c70760efa14381ab0765a247b7dba7 Mon Sep 17 00:00:00 2001 From: Matti Schneider Date: Mon, 10 Jun 2024 17:13:14 +0200 Subject: [PATCH 4/9] Fix email address --- config/_default/params.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/_default/params.yaml b/config/_default/params.yaml index dc91243..ed7db4a 100644 --- a/config/_default/params.yaml +++ b/config/_default/params.yaml @@ -3,4 +3,4 @@ github: mastodon: url: https://mastodon.lescommuns.org/@opentermsarchive username: "@opentermsarchive@mastodon.lescommuns.org" -email: contact@opentersmarchive.org +email: contact@opentermsarchive.org From 401f121f5e3ee5e3f5b9f8c45dcc018997a6457f Mon Sep 17 00:00:00 2001 From: Matti Schneider Date: Mon, 10 Jun 2024 17:17:09 +0200 Subject: [PATCH 5/9] =?UTF-8?q?Rename=20=E2=80=9Cwriting=20reference?= =?UTF-8?q?=E2=80=9D=20to=20=E2=80=9Ccopywriting=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../{writing-reference.en.md => copywriting-reference.en.md} | 4 ++-- content/memos/how-to-publish-a-memo.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) rename content/memos/{writing-reference.en.md => copywriting-reference.en.md} (99%) diff --git a/content/memos/writing-reference.en.md b/content/memos/copywriting-reference.en.md similarity index 99% rename from content/memos/writing-reference.en.md rename to content/memos/copywriting-reference.en.md index f33649c..3f6b15d 100644 --- a/content/memos/writing-reference.en.md +++ b/content/memos/copywriting-reference.en.md @@ -1,8 +1,8 @@ --- -title: "Writing reference" +title: "Copywriting reference" --- -# Writing reference +# Copywriting reference Each memo must be composed of the elements detailed below. You must follow this structure when writing your memos. diff --git a/content/memos/how-to-publish-a-memo.md b/content/memos/how-to-publish-a-memo.md index f38a70c..39bf68a 100644 --- a/content/memos/how-to-publish-a-memo.md +++ b/content/memos/how-to-publish-a-memo.md @@ -10,7 +10,7 @@ No technical skills are required. ## Prerequisites -- A drafted memo compliant with the [writing reference]({{< relref "/memos/writing-reference" >}}). +- A drafted memo compliant with the [copywriting reference]({{< relref "/memos/copywriting-reference" >}}). ## 1. Send From dfc94bc1604dfd5bc611e5a4f6006a30cf6c98f5 Mon Sep 17 00:00:00 2001 From: Matti Schneider Date: Mon, 10 Jun 2024 17:17:24 +0200 Subject: [PATCH 6/9] Improve title name --- content/memos/copywriting-reference.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/memos/copywriting-reference.en.md b/content/memos/copywriting-reference.en.md index 3f6b15d..e4cb81a 100644 --- a/content/memos/copywriting-reference.en.md +++ b/content/memos/copywriting-reference.en.md @@ -78,7 +78,7 @@ Each memo must be composed of the elements detailed below. You must follow this > > OpenAI Ireland Ltd is a Dublin-based subsidiary of OpenAI [set up](https://openai.com/blog/introducing-openai-dublin) in 2023. -## Full examples +## Complete examples ### Memo 1 From 36b58f0679f27d5b58352520b8e61aa3d234a122 Mon Sep 17 00:00:00 2001 From: Matti Schneider Date: Mon, 10 Jun 2024 17:17:41 +0200 Subject: [PATCH 7/9] Unify markup --- content/memos/copywriting-reference.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/memos/copywriting-reference.en.md b/content/memos/copywriting-reference.en.md index e4cb81a..5c6999c 100644 --- a/content/memos/copywriting-reference.en.md +++ b/content/memos/copywriting-reference.en.md @@ -107,7 +107,7 @@ Each memo must be composed of the elements detailed below. You must follow this > **Meta expands reach against child exploitation** > -> _Facebook · Community Guidelines · June 13, 2022_ +> _Facebook ▪ Community Guidelines ▪ June 13, 2022_ > > The section on child exploitation for both Facebook and Instagram [expanded](https://github.com/OpenTermsArchive/france-elections-versions/commit/0396436542fa7ef8dd8ae4dd02ff0ed5500e08a2) to cover not only publications that exploit minors, but also “any activity” related to such acts. > From 750204bc76124085c93cb66fad8c6ab94905876f Mon Sep 17 00:00:00 2001 From: Matti Schneider Date: Mon, 10 Jun 2024 17:17:51 +0200 Subject: [PATCH 8/9] Remove redundant term in URL --- content/memos/{how-to-publish-a-memo.md => how-to-publish.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename content/memos/{how-to-publish-a-memo.md => how-to-publish.md} (100%) diff --git a/content/memos/how-to-publish-a-memo.md b/content/memos/how-to-publish.md similarity index 100% rename from content/memos/how-to-publish-a-memo.md rename to content/memos/how-to-publish.md From 464c0d630981c0ea3c1558266d6e17b07ec78c80 Mon Sep 17 00:00:00 2001 From: Matti Schneider Date: Mon, 10 Jun 2024 17:20:38 +0200 Subject: [PATCH 9/9] Add language code to filename --- content/memos/{how-to-publish.md => how-to-publish.en.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename content/memos/{how-to-publish.md => how-to-publish.en.md} (100%) diff --git a/content/memos/how-to-publish.md b/content/memos/how-to-publish.en.md similarity index 100% rename from content/memos/how-to-publish.md rename to content/memos/how-to-publish.en.md