From 693348a13e3fd817668efda32873346088cd7e94 Mon Sep 17 00:00:00 2001
From: Timid Robot Zehta
Date: Tue, 14 Jan 2025 09:40:45 -0800
Subject: [PATCH 01/18] add blog post: Skipping Google Summer of Code (GSoC)
2025
---
.../2025-01-16-skipping-gsoc-2025/contents.lr | 58 +++++++++++++++++++
1 file changed, 58 insertions(+)
create mode 100644 content/blog/entries/2025-01-16-skipping-gsoc-2025/contents.lr
diff --git a/content/blog/entries/2025-01-16-skipping-gsoc-2025/contents.lr b/content/blog/entries/2025-01-16-skipping-gsoc-2025/contents.lr
new file mode 100644
index 00000000..e6d9c74a
--- /dev/null
+++ b/content/blog/entries/2025-01-16-skipping-gsoc-2025/contents.lr
@@ -0,0 +1,58 @@
+title: Skipping Google Summer of Code (GSoC) 2025
+---
+categories:
+gsoc
+open-source
+community
+---
+author: TimidRobot
+---
+pub_date: 2025-01-16
+---
+body:
+
+The Creative Commons (CC) technology team regrets to announce **we will not be
+participating in Google Summer of Code (GSoC) 2025**. While the program remains
+excellent, we do not have the resources to participate this year and meet our
+core responsibilities.
+
+We are grateful to Google for the program and have found incredible value in
+participating in past years. We look forward to participating in future years.
+We are thankful for the work and time of contributors. This is not an exciting
+announcement, but we will be better equipped to engage with work programs in
+the future.
+
+
+## Preparing to re-engage
+
+In addition to revamping our CC Open Source website during the first quarter of
+this year, we will also be refreshing our structured community involvement, and
+improving our project lead resources.
+
+Our CC Open Source website is in the process of being updated to be less
+technologically complex and to leverage the current Vocabulary design system
+([creativecommons/vocabulary][vocabulary]).
+
+Our structured community involvement has languished since the technology team
+was downsized due to the COVID pandemic (202-12-07 [Upcoming Changes to the CC
+Open Source Community — Creative Commons Open Source][changes]). We will be
+simplifying community involvement so that we can be more responsive with
+increased visibility.
+
+The most resource intensive period of a work program is the application phase.
+During this time there is a deluge of activity that has often exceeded our
+capacity. Developing our project lead resources will allow us to better set
+expectations, ease communications, and better point applicants on productive
+trajectories.
+
+[vocabulary]: http://github.com/creativecommons/vocabulary
+[changes]: https://opensource.creativecommons.org/blog/entries/2020-12-07-upcoming-changes-to-community/
+
+
+## Past participation
+
+For information on the excellent work completed during past participations,
+please see: [Open Source Work Programs: History — Creative Commons Open
+Source][history].
+
+[history]: https://opensource.creativecommons.org/programs/history/
From a23231af53a55d3fa71c23ef1f09300340b05f55 Mon Sep 17 00:00:00 2001
From: Timid Robot Zehta
Date: Tue, 14 Jan 2025 09:48:35 -0800
Subject: [PATCH 02/18] update current (non)participation
---
content/programs/contents.lr | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/content/programs/contents.lr b/content/programs/contents.lr
index b706ba5c..248972e6 100644
--- a/content/programs/contents.lr
+++ b/content/programs/contents.lr
@@ -22,25 +22,21 @@ CC isn't currently participating in Google Season of Docs (GSoD).
### Google Summer of Code
-CC will apply for participation in Google Summer of Code (GSoC) 2025.
+CC is [Skipping Google Summer of Code (GSoC) 2025][skipping2025]. We hope to
+apply again to participate in 2026.
- [Program website](https://summerofcode.withgoogle.com/)
-
+[skipping2025]: /blog/entries/2025-01-16-skipping-gsoc-2025/
### Outreachy
-CC is participating in the December 2024 cohort.
+CC is participating in the December 2024 cohort. We are planning on also participating in the December 2025 cohort.
- [Program website](https://www.outreachy.org/)
- [CC's Outreachy page][outreachycc]
-[dec2022]: https://www.outreachy.org/apply/project-selection/#creative-commons
[outreachycc]: https://www.outreachy.org/communities/cfp/creative-commons/
From 479c655980b78e3d263a7803e25ab17b2c1d6b38 Mon Sep 17 00:00:00 2001
From: Timid Robot Zehta
Date: Wed, 15 Jan 2025 07:22:06 -0800
Subject: [PATCH 03/18] update publish date to 1/15
---
.../contents.lr | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename content/blog/entries/{2025-01-16-skipping-gsoc-2025 => 2025-01-15-skipping-gsoc-2025}/contents.lr (99%)
diff --git a/content/blog/entries/2025-01-16-skipping-gsoc-2025/contents.lr b/content/blog/entries/2025-01-15-skipping-gsoc-2025/contents.lr
similarity index 99%
rename from content/blog/entries/2025-01-16-skipping-gsoc-2025/contents.lr
rename to content/blog/entries/2025-01-15-skipping-gsoc-2025/contents.lr
index e6d9c74a..f4ff5471 100644
--- a/content/blog/entries/2025-01-16-skipping-gsoc-2025/contents.lr
+++ b/content/blog/entries/2025-01-15-skipping-gsoc-2025/contents.lr
@@ -7,7 +7,7 @@ community
---
author: TimidRobot
---
-pub_date: 2025-01-16
+pub_date: 2025-01-15
---
body:
From 2d89a64880e669af99672eec6175060bc3a5a96c Mon Sep 17 00:00:00 2001
From: Timid Robot Zehta
Date: Wed, 15 Jan 2025 07:22:34 -0800
Subject: [PATCH 04/18] update publish date to 1/15
---
content/programs/contents.lr | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/programs/contents.lr b/content/programs/contents.lr
index 248972e6..cf0b7185 100644
--- a/content/programs/contents.lr
+++ b/content/programs/contents.lr
@@ -27,7 +27,7 @@ apply again to participate in 2026.
- [Program website](https://summerofcode.withgoogle.com/)
-[skipping2025]: /blog/entries/2025-01-16-skipping-gsoc-2025/
+[skipping2025]: /blog/entries/2025-01-15-skipping-gsoc-2025/
### Outreachy
From ef9d33a45c385917756ed1a48d5bcf641d70c29c Mon Sep 17 00:00:00 2001
From: "CC creativecommons.github.io Bot"
Date: Sat, 18 Jan 2025 00:32:03 +0000
Subject: [PATCH 05/18] Syncing new data changes.
---
databags/repos.json | 23 -----------------------
1 file changed, 23 deletions(-)
diff --git a/databags/repos.json b/databags/repos.json
index 00205e4c..7dfbb3a6 100644
--- a/databags/repos.json
+++ b/databags/repos.json
@@ -840,29 +840,6 @@
"url": "https://github.com/creativecommons/wp-plugin-cc-global-network",
"website": ""
},
- {
- "created": "2014-07-28T15:18:18+00:00",
- "description": "Official Creative Commons plugin for licensing your content. With Creative Commons licenses, keep your copyright AND share your creativity.",
- "engineering_project": true,
- "english_name": "CC WordPress Plugin",
- "featured": true,
- "id": 22347352,
- "language": "PHP",
- "license": {
- "name": "GNU General Public License v2.0",
- "url": "https://github.com/creativecommons/wp-plugin-creativecommons/blob/main/license.txt"
- },
- "name": "wp-plugin-creativecommons",
- "slack": "cc-dev-wordpress",
- "technologies": [
- "PHP",
- "CSS",
- "JS",
- "WordPress"
- ],
- "url": "https://github.com/creativecommons/wp-plugin-creativecommons",
- "website": "https://wordpress.org/plugins/creative-commons/"
- },
{
"created": "2020-09-17T19:19:54+00:00",
"description": "This WordPress plugin provides custom functionality for the creativecommons.org website.",
From 7caf81e0dee88d100a9363878fbe24faafdc1640 Mon Sep 17 00:00:00 2001
From: Queen-codes
Date: Sun, 19 Jan 2025 21:41:47 +0100
Subject: [PATCH 06/18] add midterm blog post
---
.../contents.lr | 73 +++++++++++++++++++
1 file changed, 73 insertions(+)
create mode 100644 content/blog/entries/outreachy-midpoint-progess-with-creative-commons/contents.lr
diff --git a/content/blog/entries/outreachy-midpoint-progess-with-creative-commons/contents.lr b/content/blog/entries/outreachy-midpoint-progess-with-creative-commons/contents.lr
new file mode 100644
index 00000000..0fbd6f47
--- /dev/null
+++ b/content/blog/entries/outreachy-midpoint-progess-with-creative-commons/contents.lr
@@ -0,0 +1,73 @@
+title: Outreachy Midpoint Progress With Creative Commons
+---
+categories:
+outreachy
+outreachy-2024
+open-source
+community
+---
+author: Queen
+---
+series: outreachy-dec-2024-consolidating-and-implementing-vocabulary
+---
+pub_date: 2025-01-19
+---
+body:
+# Outreachy Midpoint Blog Post
+
+Hi there! My name is Queen, and I’m an Outreachy intern at Creative Commons. My project involves consolidating and implementing the Vocabulary design system across Creative Commons ancillary websites. In this post, I’ll share my progress and key takeaways from the first half of my internship.
+
+## Project Overview
+
+The goal of my project is to implement the Vocabulary design system across several Creative Commons ancillary websites like the [CC Open Source](https://opensource.creativecommons.org/), [CC Legal Database](https://legaldb.creativecommons.org/en/), [CC Search Portal](https://search.creativecommons.org/), and [CC Resource Archive](https://resources.creativecommons.org/).
+## Progress So Far
+
+### Phase One: Refactoring Markup to Align with Vocabulary
+
+In the first phase, I focused on refactoring the markup to align with Vocabulary’s components and context. Here are the pull requests (PRs) merged during this phase:
+
+- [PR 118](https://github.com/creativecommons/creativecommons.github.io-source/pull/118): Refactored the recent blog post section on the homepage.
+- [PR 856](https://github.com/creativecommons/creativecommons.github.io-source/pull/856): Refactored the homepage markup to align with Vocabulary components.
+- [PR 862](https://github.com/creativecommons/creativecommons.github.io-source/pull/862): Updated `page-with-toc.html`, which serves as a template for many pages.
+- [PR 863](https://github.com/creativecommons/creativecommons.github.io-source/pull/863): Initially, I planned to refactor the markup to Vocabulary’s context, but after feedback from my mentor, I instead removed legacy class names while retaining the table structure.
+- [PR 865](https://github.com/creativecommons/creativecommons.github.io-source/pull/865): Refactored the blog’s author page to match Vocabulary’s “person” context.
+- [PR 866](https://github.com/creativecommons/creativecommons.github.io-source/pull/866): Updated the blog structure to follow Vocabulary markup.
+- [PR 867](https://github.com/creativecommons/creativecommons.github.io-source/pull/867): Refactored the Project List page, leaving the table markup intact but removing old styles.
+- [PR 868](https://github.com/creativecommons/creativecommons.github.io-source/pull/868): Refactored the Issue Finder tool, replacing Vue.js with plain JavaScript. Although removing Webpack will happen later, this PR set the stage for future improvements.
+- [PR 870](https://github.com/creativecommons/creativecommons.github.io-source/pull/870): Aligned the Authors page with Vocabulary’s team styling.
+- [PR 871](https://github.com/creativecommons/creativecommons.github.io-source/pull/871): Refactored the Project Ideas page, incorporating Vocabulary’s project markup and removing legacy styles.
+- [PR 873](https://github.com/creativecommons/creativecommons.github.io-source/pull/873): Dynamically updated the body tag’s class in `layout.html` and added a body-class field to the `blog.ini` model file for consistent styling.
+- [PR 880](https://github.com/creativecommons/creativecommons.github.io-source/pull/880): Refactored `page-with-title.html` (used by CC Tech Archives) to align with Vocabulary.
+- [PR 886](https://github.com/creativecommons/creativecommons.github.io-source/pull/886): Updated the header component markup and removed old class names.
+
+### Phase 2: Adding Local Styles
+
+After refactoring the markup, I moved on to styling sections that Vocabulary doesn’t cover. Here are some of the merged PRs so far;
+
+- [PR 888](https://github.com/creativecommons/creativecommons.github.io-source/pull/888): Added local styles based on Creative Commons’ main website for the homepage and other sections, such as “Get Involved” and “Featured Projects.”
+- [PR 891](https://github.com/creativecommons/creativecommons.github.io-source/pull/891): Created a new `issue-finder.css` file to restyle the Issue Finder page while removing legacy styles but maintaining legacy design.
+- [PR 898](https://github.com/creativecommons/creativecommons.github.io-source/pull/898): Integrated Datatables and jQuery by adding them to a vendor folder. Styled the table and code blocks using existing website styles.
+- [PR 990](https://github.com/creativecommons/creativecommons.github.io-source/pull/990): Styled the CC Search archive table using Datatables.
+
+## Current Status
+
+I’m a little behind schedule—I had planned to start work on the Legal Database website by now. However, I’m wrapping up the CC Open Source website this week and will move on to the next phase soon.
+
+## Lessons Learned
+
+This internship has been an incredible learning journey. Here are some key takeaways:
+
+### Technical Skills:
+- I’ve become comfortable working with [Lektor](https://getlektor.com/), a static site generator that was entirely new to me.
+- Implementing the Vocabulary design system has improved my problem-solving skills, especially when dealing with legacy code and adapting the system to fit unique website needs.
+- To localize the table component, I had to read the [DataTables documentation](https://datatables.net/), which helped my ability to learn on the go.
+
+### Collaboration:
+Working with mentors has taught me the value of clear communication, especially when addressing blockers or seeking feedback.
+
+### Project Management:
+Breaking tasks into smaller chunks, prioritizing effectively, and maintaining consistent progress have been critical in managing this project.
+
+This experience has significantly boosted my confidence as a front-end developer, particularly in creating user-friendly and accessible interfaces.
+
+That’s it for now! Thank you for reading about my progress. I’m excited to see how the second half of this journey unfolds!
From 181c1fd40450dac7f83b285bc7abd2b0788e4e58 Mon Sep 17 00:00:00 2001
From: possumbilities <109087089+possumbilities@users.noreply.github.com>
Date: Tue, 21 Jan 2025 19:37:43 +0000
Subject: [PATCH 07/18] remove/modify links to wp plugin post archive
---
content/blog/authors/ahmadbilaldev/contents.lr | 2 +-
.../2020-03-05-involucrate-gsoc-outreachy-es/contents.lr | 2 +-
.../2020-12-07-upcoming-changes-to-community/contents.lr | 2 +-
content/blog/entries/cc-wp-plugin-final-phase/contents.lr | 2 +-
content/blog/entries/cc-wp-plugin-second-phase/contents.lr | 4 ++--
content/community/contents.lr | 2 --
6 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/content/blog/authors/ahmadbilaldev/contents.lr b/content/blog/authors/ahmadbilaldev/contents.lr
index e37eccad..cf78e2cb 100644
--- a/content/blog/authors/ahmadbilaldev/contents.lr
+++ b/content/blog/authors/ahmadbilaldev/contents.lr
@@ -13,5 +13,5 @@ meetups, conferences and meeting new people. Cats are his weakness, and he is a
sucker for well-engineered cars.
Ahmad worked on [the CC WordPress
-plugin](https://github.com/creativecommons/wp-plugin-creativecommons) as part
+plugin](https://github.com/cc-archive/wp-plugin-creativecommons) as part
of [Google Summer of Code (GSoC) 2019](/programs/history/).
diff --git a/content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr b/content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr
index 945ff9d1..af4f325b 100644
--- a/content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr
+++ b/content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr
@@ -27,7 +27,7 @@ Las pasantías consisten en el desarrollo de un proyecto el cual debe ser llevad
En las versiones pasadas de estos programas tuvimos excelentes resultados llevados a cabo por excelentes personas que pusieron toda su dedicación para concretar estos proyectos:
## GSoC 2019
-- [Wordpress Plugin](https://github.com/creativecommons/wp-plugin-creativecommons) por Ahmad Bilal
+- [Wordpress Plugin](https://github.com/cc-archive/wp-plugin-creativecommons) por Ahmad Bilal
- [CC Search Browser extension](https://github.com/creativecommons/ccsearch-browser-extension) por Mayank Nader
- [CC Vocabulary](https://github.com/creativecommons/vue-vocabulary) por Dhruv Bhanushali
- [Revamping the CC Chooser](https://github.com/creativecommons/cc-chooser) por Ari Madian
diff --git a/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr b/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr
index 5012ae82..27cdfc28 100644
--- a/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr
+++ b/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr
@@ -59,7 +59,7 @@ We will continue to actively develop the following projects:
- [License Buttons](https://github.com/creativecommons/licensebuttons/) (maintainer: Timid Robot Zehta)
- [Platform Toolkit](https://github.com/creativecommons/mp/) (maintainer: Timid Robot Zehta)
- [Vocabulary](https://github.com/creativecommons/vocabulary) (maintainers: Zack Krida & Dhruv Bhanushali)
-- [WordPress Plugin](https://github.com/creativecommons/wp-plugin-creativecommons) (new maintainer: Zack Krida)
+- [WordPress Plugin](https://github.com/cc-archive/wp-plugin-creativecommons) (new maintainer: Zack Krida)
**Maintenance Mode**
diff --git a/content/blog/entries/cc-wp-plugin-final-phase/contents.lr b/content/blog/entries/cc-wp-plugin-final-phase/contents.lr
index 7c4aa533..0b2b6508 100644
--- a/content/blog/entries/cc-wp-plugin-final-phase/contents.lr
+++ b/content/blog/entries/cc-wp-plugin-final-phase/contents.lr
@@ -78,6 +78,6 @@ option, which is much better than previous footer implementation.
- Integrate WPGulp workflow and improve i18n.
- Improve documentation with a visual walk-around of every feature.
-Thank you for reading. For more, see the [GitHub repository](https://github.com/creativecommons/wp-plugin-creativecommons).
+Thank you for reading. For more, see the [GitHub repository](https://github.com/cc-archive/wp-plugin-creativecommons).
If you have any feedback or suggestions, let us know in the discussion on `#cc-dev-wordpress` Slack channel. Looking forward!
diff --git a/content/blog/entries/cc-wp-plugin-second-phase/contents.lr b/content/blog/entries/cc-wp-plugin-second-phase/contents.lr
index 529bcc28..07139529 100644
--- a/content/blog/entries/cc-wp-plugin-second-phase/contents.lr
+++ b/content/blog/entries/cc-wp-plugin-second-phase/contents.lr
@@ -23,7 +23,7 @@ For the context, I am working with my mentor [Timid Robot](https://creativecommo
### Release of v2019.7.1
-We have released the latest stable version of the plugin. `v2019.7.1` is out and tagged in the [wp-plugin-creativecommons repository](https://github.com/creativecommons/wp-plugin-creativecommons/releases). Given that a stable release is available, we have submitted it to [WordPress.org plugin directory](https://en-nz.wordpress.org/plugins/). As soon as their team approves it, the plugin will be available to install for all WordPress users, which is substantial.
+We have released the latest stable version of the plugin. `v2019.7.1` is out and tagged in the [wp-plugin-creativecommons repository](https://github.com/cc-archive/wp-plugin-creativecommons/releases). Given that a stable release is available, we have submitted it to [WordPress.org plugin directory](https://en-nz.wordpress.org/plugins/). As soon as their team approves it, the plugin will be available to install for all WordPress users, which is substantial.
### What's next
@@ -34,6 +34,6 @@ Although the current implentation does the job, but we want it to use new [CC Li
- Changes in design and features.
- Improve the documentation.
-For more, see the [GitHub repository](https://github.com/creativecommons/wp-plugin-creativecommons).
+For more, see the [GitHub repository](https://github.com/cc-archive/wp-plugin-creativecommons).
If you have any feedback or suggestions, let us know in the discussion on `#cc-dev-wordpress` Slack channel. Looking forward!
\ No newline at end of file
diff --git a/content/community/contents.lr b/content/community/contents.lr
index 7265e5d6..cca20222 100644
--- a/content/community/contents.lr
+++ b/content/community/contents.lr
@@ -53,7 +53,6 @@ The channels most relevant to CC's developer community are:
| `#cc-dev-platform-toolkit` | [mp][mp] project (CC Platform Toolkit) |
| `#cc-dev-searchportal` | [search][search] project |
| `#cc-dev-vocabulary` | [cc-vocabulary][cc-vocabulary] project |
-| `#cc-dev-wordpress` | [wp-plugin-creativecommons][wp-plugin-creativecommons] project (creativecommons WordPress plugin) |
| `#cc-dev-workprograms` | **GSoC, GSoD, Outreachy, and other [work programs][workprograms] or internships** |
| `#cc-developers` | **general technical issues, new tech blog posts, etc.** |
| `#cc-translation` | Coordinating translation efforts |
@@ -66,7 +65,6 @@ The channels most relevant to CC's developer community are:
[mp]: https://github.com/creativecommons/mp
[cc-vocabulary]: https://github.com/creativecommons/cc-vocabulary
[search]: https://github.com/creativecommons/search
-[wp-plugin-creativecommons]: https://github.com/creativecommons/wp-plugin-creativecommons
[workprograms]: /programs/
From a57bb80d0dcfe493f6e5c9f9eff3d9bd7ce23a9e Mon Sep 17 00:00:00 2001
From: "CC creativecommons.github.io Bot"
Date: Thu, 30 Jan 2025 08:32:07 +0000
Subject: [PATCH 08/18] Syncing new data changes.
---
databags/community_team_members.json | 26 --------------------------
1 file changed, 26 deletions(-)
diff --git a/databags/community_team_members.json b/databags/community_team_members.json
index 6b83d0a6..d6bb4ee2 100644
--- a/databags/community_team_members.json
+++ b/databags/community_team_members.json
@@ -124,32 +124,6 @@
"name": "Vocabulary",
"repos": "vocabulary"
},
- {
- "members": [
- {
- "github": "hugosolar",
- "name": "Hugo Solar",
- "role": "Project Maintainer"
- },
- {
- "github": "kgodey",
- "name": "Kriti Godey",
- "role": "Project Maintainer"
- },
- {
- "github": "ahmadbilaldev",
- "name": "Ahmad Bilal",
- "role": "Project Core Committer"
- },
- {
- "github": "Cronus1007",
- "name": "Ritish Thareja",
- "role": "Project Core Committer"
- }
- ],
- "name": "WordPress Plugin",
- "repos": "wp-plugin-creativecommons"
- },
{
"members": [
{
From a958e70b90d3bbe4286a591f822a07e8fa55c552 Mon Sep 17 00:00:00 2001
From: Naisha
Date: Sun, 16 Feb 2025 00:28:15 -0800
Subject: [PATCH 09/18] added gsoc 2024 to programs history page
---
content/programs/history/contents.lr | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content/programs/history/contents.lr b/content/programs/history/contents.lr
index 644ca69c..ebbee967 100644
--- a/content/programs/history/contents.lr
+++ b/content/programs/history/contents.lr
@@ -25,6 +25,8 @@ first time in 2020.
CC has participated in Google Summer of Code (GSoC) ten times since 2006:
- *[All GSoC Open Source Blog posts](/blog/categories/gsoc/)*
+- [Google Summer of Code 2024](https://summerofcode.withgoogle.com/archive/2024/organizations/creative-commons)
+ - [Open Source Blog Posts](/blog/categories/gsoc-2024/)
- [Google Summer of Code
2023](https://summerofcode.withgoogle.com/archive/2023/organizations/creative-commons)
- [Open Source Blog posts](/blog/categories/gsoc-2023/)
From da792149b12914ed3fb8c4006e95f03828cc91d2 Mon Sep 17 00:00:00 2001
From: Queen
Date: Thu, 27 Feb 2025 13:59:57 +0100
Subject: [PATCH 10/18] add final blog post
---
.../contents.lr | 91 +++++++++++++++++++
1 file changed, 91 insertions(+)
create mode 100644 content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr
diff --git a/content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr b/content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr
new file mode 100644
index 00000000..d9820593
--- /dev/null
+++ b/content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr
@@ -0,0 +1,91 @@
+title: Reflecting On My Outreachy Journey With Creative Commons
+---
+categories:
+outreachy
+outreachy-2024
+open-source
+community
+---
+author: Queen
+---
+series: outreachy-dec-2024-consolidating-and-implementing-vocabulary
+---
+pub_date: 2025-02-27
+---
+body:
+
+It feels like just yesterday I was writing my first blog post, trying to wrap my head around all the things I’d be doing during this internship. And now, here I am, writing my final post—time really does fly when you’re deep in code, refactoring, and figuring things out.
+
+When I started, I was both excited and nervous. I knew I’d be working on consolidating the Vocabulary design system across different Creative Commons ancillary websites, but I didn’t fully grasp just how much I’d learn along the way. The idea of making a meaningful contribution to such an impactful organization was thrilling, yet there was that little voice in my head wondering: *Can I really do this?*
+
+Spoiler alert: Yes, I could—and I did!
+
+## From Day One to Now: The Journey
+
+My first few weeks were all about getting familiar with the codebase, understanding how Vocabulary worked, and figuring out how the different websites used it. I remember spending quite a bit of time just reading through the Vocabulary documentation, going through all of the websites to identify discrepancies, and trying to piece things together.
+
+Looking back, it’s funny how something that once felt so complex now feels like second nature.
+
+## Refactoring the Issue Finder: Removing Vue for a Simpler Setup
+
+One of my major tasks was refactoring the issue finder tool on the Creative Commons Open Source website. This tool was built using Vue.js, but the goal was to remove Vue and refactor the JavaScript to align with the vocabulary approach - using HTML and CSS as much as possible with minimal and plain JavaScript.
+
+At first, this felt like a huge task, especially since I hadn’t used Vue before. The Vue-based setup handled filtering, UI interactions, and data fetching. Without a framework, I had to ensure that the core functionality remained intact while simplifying the code.
+
+I started by carefully analyzing how Vue was being used in the project. Then, I broke down the refactor into smaller steps:
+
+- Removing Vue dependencies and setting up a plan to replace its functionality with vanilla JavaScript.
+- Refactoring the JavaScript—rewriting event listeners, handling state manually, and simplifying functions where possible.
+- Ensuring everything still worked-since Vue had handled reactivity, I had to make sure UI changes (like filtering issues) were updated correctly without unnecessary complexity.
+- Testing and fine-tuning—checking for edge cases and making sure the refactored version behaved just like the Vue version (but with cleaner, more maintainable code).
+
+## Working with DataTables: A Whole New Learning Curve
+
+One of the most interesting things I learned during my internship was working with datatables Before this project, I had never even heard of DataTables. I spent time reading through the documentation, testing out different configurations, and experimenting with how it handled datasets.
+
+Initially, I added DataTables to the project using a **content delivery network (CDN)**, which was the quickest way to integrate it. However, after a suggestion from my mentor, we decided it would be better to download the source code and add it as a vendor folder in the project.
+
+After setting it up, I worked on overriding some default styles to make sure datatables aligned with Vocabulary’s design system. I had to carefully adjust CSS properties, inspect the DOM structure, and test different solutions to make sure everything looked cohesive.
+
+This entire process taught me an important lesson:
+
+> **Documentation is your best friend.** When dealing with a new tool, reading the official documentation can save so much time.
+
+## From Midterm to Now: Wrapping Up and Final Contributions
+
+After the midterm blog, my focus shifted towards finishing up the restyling process and addressing minor bugs across the Creative Commons Open Source website. These were smaller but important refinements—ensuring consistency, fixing UI inconsistencies, and making sure everything aligned with the Vocabulary design system.
+
+### Improving the Search Portal
+
+One of the websites I worked on was the **Search Portal**. This involved:
+
+- Defining abbreviations to improve clarity and accessibility.
+- Restyling the search input to align visually with the provided context in Vocabulary, making it feel more integrated with the overall design.
+- Making downstream changes to ensure everything was up to date with Vocabulary’s latest standards.
+
+The goal was to improve both functionality and design, making sure the search experience was more intuitive and visually cohesive.
+
+### CC Legal Database(LegalDB): Planning for Future Work
+
+Although LegalDB was initially part of the project scope, time constraints didn’t allow for implementation. Instead, I'm focusing on laying the groundwork for future contributions by:
+
+- Identifying necessary changes and documenting them thoroughly.
+- Creating all the relevant issues and linking them to the larger tracking issue on Vocabulary, ensuring that future contributors have a clear roadmap to follow.
+
+This is so that even though I couldn’t complete the work myself, the transition for the next person picking it up would be smooth and well-documented.
+
+## What’s Next?
+
+This internship has solidified my love for front-end development, especially when it comes to building interfaces that are both beautiful and functional. My next goal? To dive deeper into **animations, interactivity, and making the web more immersive** (looking at you, **GSAP and Three.js**!).
+
+I also want to keep contributing to **open source** and continue growing as a developer. This isn’t the end—it’s just the beginning of the next chapter.
+
+## A Heartfelt Goodbye (For Now!)
+
+To the my mentors, and everyone who supported me during this internship— thank you! Your guidance, patience, and encouragement made this experience truly special.
+
+To future Outreachy interns: If you ever feel overwhelmed, know that it’s part of the journey. Keep asking questions, keep pushing through challenges, and most importantly—**enjoy the process**. You’ll come out on the other side with skills, confidence, and a whole new appreciation for open source.
+
+And with that, it’s time to say goodbye to this chapter.
+
+Until then, **happy coding!** 🚀
From 9a8bec5dab47b6b41cbcf0538ae8723a68035db9 Mon Sep 17 00:00:00 2001
From: Queen
Date: Thu, 27 Feb 2025 15:37:23 +0100
Subject: [PATCH 11/18] fixed grammatical errors and oversight
---
.../contents.lr | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr b/content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr
index d9820593..64fcd460 100644
--- a/content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr
+++ b/content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr
@@ -16,7 +16,7 @@ body:
It feels like just yesterday I was writing my first blog post, trying to wrap my head around all the things I’d be doing during this internship. And now, here I am, writing my final post—time really does fly when you’re deep in code, refactoring, and figuring things out.
-When I started, I was both excited and nervous. I knew I’d be working on consolidating the Vocabulary design system across different Creative Commons ancillary websites, but I didn’t fully grasp just how much I’d learn along the way. The idea of making a meaningful contribution to such an impactful organization was thrilling, yet there was that little voice in my head wondering: *Can I really do this?*
+When I started, I was both excited and nervous. I knew I’d be working on implementing and consolidating the Vocabulary design system across different Creative Commons ancillary websites, but I didn’t fully grasp just how much I’d learn along the way. The idea of making a meaningful contribution to such an impactful organization was thrilling, yet there was that little voice in my head wondering: *Can I really do this?*
Spoiler alert: Yes, I could—and I did!
@@ -59,11 +59,11 @@ After the midterm blog, my focus shifted towards finishing up the restyling proc
One of the websites I worked on was the **Search Portal**. This involved:
-- Defining abbreviations to improve clarity and accessibility.
+- Defining the CC abbreviation in the header section to improve clarity and accessibility.
- Restyling the search input to align visually with the provided context in Vocabulary, making it feel more integrated with the overall design.
- Making downstream changes to ensure everything was up to date with Vocabulary’s latest standards.
-The goal was to improve both functionality and design, making sure the search experience was more intuitive and visually cohesive.
+The goal was to keep the existing functionality and improve on the design, making sure the search input visually aligned with the design system.
### CC Legal Database(LegalDB): Planning for Future Work
@@ -82,7 +82,7 @@ I also want to keep contributing to **open source** and continue growing as a de
## A Heartfelt Goodbye (For Now!)
-To the my mentors, and everyone who supported me during this internship— thank you! Your guidance, patience, and encouragement made this experience truly special.
+To my mentors, and everyone who supported me during this internship— thank you! Your guidance, patience, and encouragement made this experience truly special.
To future Outreachy interns: If you ever feel overwhelmed, know that it’s part of the journey. Keep asking questions, keep pushing through challenges, and most importantly—**enjoy the process**. You’ll come out on the other side with skills, confidence, and a whole new appreciation for open source.
From de383521f7959092dc7281b342ea604c9a31a27a Mon Sep 17 00:00:00 2001
From: Shafiya-Heena
Date: Thu, 6 Mar 2025 16:28:01 +0000
Subject: [PATCH 12/18] aws rds blog post
---
.../2025-03-06-AWS-RDS-blog-post/contents.lr | 94 +++++++++++++++++++
1 file changed, 94 insertions(+)
create mode 100644 content/blog/entries/2025-03-06-AWS-RDS-blog-post/contents.lr
diff --git a/content/blog/entries/2025-03-06-AWS-RDS-blog-post/contents.lr b/content/blog/entries/2025-03-06-AWS-RDS-blog-post/contents.lr
new file mode 100644
index 00000000..61ce44bd
--- /dev/null
+++ b/content/blog/entries/2025-03-06-AWS-RDS-blog-post/contents.lr
@@ -0,0 +1,94 @@
+title:.Migrating from MariaDB 10.4 to 10.11 on AWS RDS
+
+---
+categories:
+open-source
+collaboration
+---
+author:.shafiya
+---
+pub_date:.2025-03-06
+---
+body:
+As part of AWS’s request to migrate the RDS DB engine from MariaDB 10.4 to 10.11, this blog post provides a detailed, step-by-step guide to ensure a smooth transition. We’ll cover the pre-migration steps, the actual upgrade process, and post-migration verification to minimize downtime and potential issues.
+Let’s dive in!
+Pre-Migration Steps
+Before performing the upgrade, it’s essential to ensure a structured migration plan, especially if your environment has customized database parameters. Follow these preliminary steps:
+Create a DB Parameter Group – Customizes database-specific settings for the new engine version.
+Create an Option Group – Manages additional features like replication and logging.
+Backup and Test – Take a snapshot of the existing database to prevent data loss.
+Create a DB Parameter Group
+RDS DB Parameter Groups allow you to configure database-specific parameters, such as memory, cache, and other DB settings. You need to create a custom DB Parameter Group for MariaDB 10.11 because different versions require different settings.
+How to Create a DB Parameter Group
+Login to AWS Management Console
+Go to the RDS service in the AWS Management Console.
+Navigate to Parameter Groups
+In the left navigation pane, under Databases, select Parameter Groups.
+Create a New Parameter Group
+Click on Create parameter group.
+Parameter group family: Choose mariadb10.11 from the dropdown.
+Group name: Provide a meaningful name like webserver-stage-rds parameters-mariadb-10-11.
+Description: Optionally add a description such as "Custom Parameter Group for MariaDB 10.11."
+Click Create.
+Modify the Parameters
+Once the parameter group is created, click on it to edit.
+Modify the parameters as per your application’s requirements, e.g., change innodb_buffer_pool_size,time_zone, etc., to optimize for the new version.
+Click Save changes once done.
+Create an Option Group
+Option Groups are a collection of database options (such as replication, backups, and logging) that you can apply to RDS instances. To migrate from 10.4 to 10.11, you need to create and associate an Option Group with the new engine version.
+How to Create an Option Group
+Go to Option Groups in RDS
+In the AWS Management Console, go to RDS and then Option Groups under the Databases section.
+Create an Option Group
+Click Create group.
+Option group name: Provide a name like default:mariadb-10-11.
+Engine version: Select MariaDB 10.11.
+Click Create.
+Add Options to the Group
+Select the new Option Group you just created.
+Click Add option to save the selected options.
+Perform the MariaDB Version Upgrade
+Once you’ve created the required DB Parameter Group and Option Group, you’re ready to perform the migration from MariaDB 10.4 to 10.11.
+How to Perform the Migration
+Backup Your Database
+It’s important to create a snapshot of your current DB instance before starting the upgrade process. This ensures that you can roll back in case of any issues.
+Go to your RDS instance and click on Actions → Take Snapshot.
+Modify the DB Instance to Use the New Version
+Navigate to Databases in the AWS RDS dashboard.
+Select the DB instance you want to upgrade.
+Click Modify at the top right.
+Under DB Engine Version, choose 10.11 from the drop-down.
+Under DB Parameter Group, select the custom parameter group created for 10.11.
+Under Option Group, select the newly created Option Group for MariaDB 10.11.
+Click Continue.
+Apply Changes
+Choose whether you want the changes to apply immediately or during the next maintenance window. For minimal downtime, apply during the maintenance window.
+Review the changes and click Modify DB Instance.
+Reboot the Instance (if necessary)
+Once the modification is complete, your DB instance might need to be rebooted for the changes to take effect. Confirm and reboot if prompted.
+Verify the Migration
+After the upgrade is complete, it’s time to verify the migration.
+Check DB Engine Version
+Check Application Performance
+Test your application to ensure that it works properly with the new MariaDB version.
+Review Logs
+Check the RDS logs to verify that no errors have occurred during the upgrade process.
+Post-Migration Clean-Up
+Delete Old Parameter and Option Groups (if not required)
+Once the migration is successful and tested, you can clean up unused Parameter and Option Groups to avoid unnecessary overhead.
+Monitor and Scale
+Monitor the instance for any potential issues and scale the resources (e.g., CPU, memory) if required based on the performance of MariaDB 10.11.
+Conclusion
+Migrating from MariaDB 10.4 to 10.11 on AWS RDS is a straightforward process, but it requires careful planning, especially around DB Parameter Groups and Option Groups. By following the steps outlined in this blog post, you can ensure a smooth transition to the latest MariaDB version, improving the performance, security, and scalability of your application.
+Remember to always perform proper backups, test the migration in a staging environment, and monitor post-migration performance to ensure everything is functioning as expected.
+Best Practices
+✔ Always test the migration in a staging environment before applying changes in production.
+✔ Monitor RDS logs and application performance after the upgrade.
+✔ Ensure proper backups before initiating any engine version changes.
+By implementing these best practices, you can enhance performance, security, and scalability while ensuring a successful migration.
+🚀 Happy migrating!
+References
+AWS RDS Documentation - MariaDB Engine Versions
+AWS RDS Parameter Groups
+AWS RDS Option Groups
+
From f80b8d8eddd73a0a4003543ced1ac3573e2a6fd4 Mon Sep 17 00:00:00 2001
From: Shafiya-Heena
Date: Thu, 20 Mar 2025 16:21:53 +0000
Subject: [PATCH 13/18] formatting the file
---
.../2025-03-06-AWS-RDS-blog-post/contents.lr | 172 ++++++++++--------
1 file changed, 97 insertions(+), 75 deletions(-)
diff --git a/content/blog/entries/2025-03-06-AWS-RDS-blog-post/contents.lr b/content/blog/entries/2025-03-06-AWS-RDS-blog-post/contents.lr
index 61ce44bd..49d20d66 100644
--- a/content/blog/entries/2025-03-06-AWS-RDS-blog-post/contents.lr
+++ b/content/blog/entries/2025-03-06-AWS-RDS-blog-post/contents.lr
@@ -1,94 +1,116 @@
-title:.Migrating from MariaDB 10.4 to 10.11 on AWS RDS
+title: Migrating from MariaDB 10.4 to 10.11 on AWS RDS
---
categories:
open-source
collaboration
---
-author:.shafiya
+author: shafiya
---
-pub_date:.2025-03-06
+pub_date: 2025-03-24
---
body:
As part of AWS’s request to migrate the RDS DB engine from MariaDB 10.4 to 10.11, this blog post provides a detailed, step-by-step guide to ensure a smooth transition. We’ll cover the pre-migration steps, the actual upgrade process, and post-migration verification to minimize downtime and potential issues.
+
Let’s dive in!
-Pre-Migration Steps
+
+## Pre-Migration Steps
Before performing the upgrade, it’s essential to ensure a structured migration plan, especially if your environment has customized database parameters. Follow these preliminary steps:
-Create a DB Parameter Group – Customizes database-specific settings for the new engine version.
-Create an Option Group – Manages additional features like replication and logging.
-Backup and Test – Take a snapshot of the existing database to prevent data loss.
-Create a DB Parameter Group
+- Create a DB Parameter Group – Customizes database-specific settings for the new engine version.
+- Create an Option Group – Manages additional features like replication and logging.
+- Backup and Test – Take a snapshot of the existing database to prevent data loss.
+
+### Create a DB Parameter Group
RDS DB Parameter Groups allow you to configure database-specific parameters, such as memory, cache, and other DB settings. You need to create a custom DB Parameter Group for MariaDB 10.11 because different versions require different settings.
-How to Create a DB Parameter Group
-Login to AWS Management Console
-Go to the RDS service in the AWS Management Console.
-Navigate to Parameter Groups
-In the left navigation pane, under Databases, select Parameter Groups.
-Create a New Parameter Group
-Click on Create parameter group.
-Parameter group family: Choose mariadb10.11 from the dropdown.
-Group name: Provide a meaningful name like webserver-stage-rds parameters-mariadb-10-11.
-Description: Optionally add a description such as "Custom Parameter Group for MariaDB 10.11."
-Click Create.
-Modify the Parameters
-Once the parameter group is created, click on it to edit.
-Modify the parameters as per your application’s requirements, e.g., change innodb_buffer_pool_size,time_zone, etc., to optimize for the new version.
-Click Save changes once done.
-Create an Option Group
+
+**How to Create a DB Parameter Group**
+- Login to AWS Management Console
+ - Go to the RDS service in the AWS Management Console.
+- Navigate to Parameter Groups
+ - In the left navigation pane, under Databases, select Parameter Groups.
+- Create a New Parameter Group
+ - Click on Create parameter group.
+ - Parameter group family: Choose mariadb10.11 from the dropdown.
+ - Group name: Provide a meaningful name like webserver-stage-rds parameters-mariadb-10-11.
+ - Description: Optionally add a description such as "Custom Parameter Group for MariaDB 10.11."
+ - Click Create.
+- Modify the Parameters
+ - Once the parameter group is created, click on it to edit.
+ - Modify the parameters as per your application’s requirements, e.g., change innodb_buffer_pool_size,time_zone, etc., to optimize for the new version.
+ - Click Save changes once done.
+
+### Create an Option Group
+
Option Groups are a collection of database options (such as replication, backups, and logging) that you can apply to RDS instances. To migrate from 10.4 to 10.11, you need to create and associate an Option Group with the new engine version.
-How to Create an Option Group
-Go to Option Groups in RDS
-In the AWS Management Console, go to RDS and then Option Groups under the Databases section.
-Create an Option Group
-Click Create group.
-Option group name: Provide a name like default:mariadb-10-11.
-Engine version: Select MariaDB 10.11.
-Click Create.
-Add Options to the Group
-Select the new Option Group you just created.
-Click Add option to save the selected options.
-Perform the MariaDB Version Upgrade
-Once you’ve created the required DB Parameter Group and Option Group, you’re ready to perform the migration from MariaDB 10.4 to 10.11.
-How to Perform the Migration
-Backup Your Database
-It’s important to create a snapshot of your current DB instance before starting the upgrade process. This ensures that you can roll back in case of any issues.
-Go to your RDS instance and click on Actions → Take Snapshot.
-Modify the DB Instance to Use the New Version
-Navigate to Databases in the AWS RDS dashboard.
-Select the DB instance you want to upgrade.
-Click Modify at the top right.
-Under DB Engine Version, choose 10.11 from the drop-down.
-Under DB Parameter Group, select the custom parameter group created for 10.11.
-Under Option Group, select the newly created Option Group for MariaDB 10.11.
-Click Continue.
-Apply Changes
-Choose whether you want the changes to apply immediately or during the next maintenance window. For minimal downtime, apply during the maintenance window.
-Review the changes and click Modify DB Instance.
-Reboot the Instance (if necessary)
-Once the modification is complete, your DB instance might need to be rebooted for the changes to take effect. Confirm and reboot if prompted.
-Verify the Migration
+
+**How to Create an Option Group**
+- Go to Option Groups in RDS
+ - In the AWS Management Console, go to RDS and then Option Groups under the Databases section.
+- Create an Option Group
+ - Click Create group.
+ - Option group name: Provide a name like default:mariadb-10-11.
+ - Engine version: Select MariaDB 10.11.
+ - Click Create.
+- Add Options to the Group
+ - Select the new Option Group you just created.
+ - Click Add option to save the selected options.
+
+
+## Perform the MariaDB Version Upgrade
+
+ Once you’ve created the required DB Parameter Group and Option Group, you’re ready to perform the migration from MariaDB 10.4 to 10.11.
+
+### How to Perform the Migration
+- Backup Your Database
+ - It’s important to create a snapshot of your current DB instance before starting the upgrade process. This ensures that you can roll back in case of any issues.
+ - Go to your RDS instance and click on Actions → Take Snapshot.
+- Modify the DB Instance to Use the New Version
+ - Navigate to Databases in the AWS RDS dashboard.
+ - Select the DB instance you want to upgrade.
+ - Click Modify at the top right.
+ - Under DB Engine Version, choose 10.11 from the drop-down.
+ - Under DB Parameter Group, select the custom parameter group created for 10.11.
+ - Under Option Group, select the newly created Option Group for MariaDB 10.11.
+ - Click Continue.
+- Apply Changes
+ - Choose whether you want the changes to apply immediately or during the next maintenance window. For minimal downtime, apply during the maintenance window.
+ - Review the changes and click Modify DB Instance.
+- Reboot the Instance (if necessary)
+ - Once the modification is complete, your DB instance might need to be rebooted for the changes to take effect. Confirm and reboot if prompted.
+
+### Verify the Migration
After the upgrade is complete, it’s time to verify the migration.
-Check DB Engine Version
-Check Application Performance
-Test your application to ensure that it works properly with the new MariaDB version.
-Review Logs
-Check the RDS logs to verify that no errors have occurred during the upgrade process.
-Post-Migration Clean-Up
-Delete Old Parameter and Option Groups (if not required)
-Once the migration is successful and tested, you can clean up unused Parameter and Option Groups to avoid unnecessary overhead.
-Monitor and Scale
-Monitor the instance for any potential issues and scale the resources (e.g., CPU, memory) if required based on the performance of MariaDB 10.11.
-Conclusion
-Migrating from MariaDB 10.4 to 10.11 on AWS RDS is a straightforward process, but it requires careful planning, especially around DB Parameter Groups and Option Groups. By following the steps outlined in this blog post, you can ensure a smooth transition to the latest MariaDB version, improving the performance, security, and scalability of your application.
+- Check DB Engine Version
+- Check Application Performance
+ - Test your application to ensure that it works properly with the new MariaDB version.
+- Review Logs
+ - Check the RDS logs to verify that no errors have occurred during the upgrade process.
+
+
+## Post-Migration Clean-Up
+- Delete Old Parameter and Option Groups (if not required)
+ - Once the migration is successful and tested, you can clean up unused Parameter and Option Groups to avoid unnecessary overhead.
+- Monitor and Scale
+ - Monitor the instance for any potential issues and scale the resources (e.g., CPU, memory) if required based on the performance of MariaDB 10.11.
+
+
+## Conclusion
+Migrating from MariaDB 10.4 to 10.11 on AWS RDS is a straightforward process, but it requires careful planning, especially around DB Parameter Groups and Option Groups.
+By following the steps outlined in this blog post, you can ensure a smooth transition to the latest MariaDB version, improving the performance, security, and scalability of your application.
Remember to always perform proper backups, test the migration in a staging environment, and monitor post-migration performance to ensure everything is functioning as expected.
-Best Practices
-✔ Always test the migration in a staging environment before applying changes in production.
-✔ Monitor RDS logs and application performance after the upgrade.
-✔ Ensure proper backups before initiating any engine version changes.
+
+
+## Best Practices
+- ✔ Always test the migration in a staging environment before applying changes in production.
+- ✔ Monitor RDS logs and application performance after the upgrade.
+- ✔ Ensure proper backups before initiating any engine version changes.
+
By implementing these best practices, you can enhance performance, security, and scalability while ensuring a successful migration.
+
🚀 Happy migrating!
-References
-AWS RDS Documentation - MariaDB Engine Versions
-AWS RDS Parameter Groups
-AWS RDS Option Groups
+
+## References
+- [AWS RDS Documentation - MariaDB Engine Versions](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBEngineVersion.html)
+- [AWS RDS Parameter Groups](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.DBParameterGroups.html)
+- [AWS RDS Option Groups](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.OptionGroups.html)
From c9140f3c643f0c90c7ca9a79c9cd3ea853a9d924 Mon Sep 17 00:00:00 2001
From: Ari Madian <28791774+akmadian@users.noreply.github.com>
Date: Fri, 18 Apr 2025 15:05:36 -0700
Subject: [PATCH 14/18] Remove Ari Photo
---
.../entries/meet-gsoc-2019-students/ari.jpg | Bin 54130 -> 0 bytes
.../entries/meet-gsoc-2019-students/contents.lr | 4 ----
2 files changed, 4 deletions(-)
delete mode 100644 content/blog/entries/meet-gsoc-2019-students/ari.jpg
diff --git a/content/blog/entries/meet-gsoc-2019-students/ari.jpg b/content/blog/entries/meet-gsoc-2019-students/ari.jpg
deleted file mode 100644
index e0efaad4bbd9ed767933e6b6b714ad3cd6530ebd..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001
literal 54130
zcmeFXWk6KX)-XJjfS?E>N)8eNN_UUs(A^@4Fobl6Fr!iy3=Il0ND4>^(ji?+hmz7I
zodYw&d$8`k&vW1Bd%i#4pYI-+IqU4b*4nG~+Iz1vr(aLMgD$Blt15%=@IW9H;16^<
zLm;i>=U@v0X=;LQf*55iOU2ORG32L>Gg{UA9v
zHzyd#LC4;!7&FlA3ng>c*^~z%0lwAi>P3X=Ux;a@NQN
zI%|;R7m^edXXclX6cm*d6aj&lpS=DfF@E5aH-F)fr!4=F{wc?A*aifO0)dEuQ3?44
z1qGrA{%C^#GK%mooEDAu3kMIM02G4!OW#1Q_4KgSUN9t*H(
z4C!z95&)n7OFI-p{j(jg9R5U1^v`h##U#W*F){yu)BeaQz|WtC_nQx3uQdF>mhDI*
z_ygmSrC5IveT&@HvYvqQ9OJV-^sT6cUgW690$y{;3TFGByE$uHFU0
z))jCG8n|Zw!FmYrIJ*Fzcu3%GLmWYbCE_9i;v0Vtcs>L{hNnRkryu{`e~%0F{T%;a
zqmB8#m9-!-`pmS3<(snc0?4fL9!tJ(OGaUS4jJe0(mRyjEv1$ZPHD%;#t2
z2K4jufutdRZU8aNi}^mx&cQ{7WwWM%h1tPIhQ(M!lV8(K0cP)@65s*T5708O4sf)V
zuwjA7GE4hO`Z>Ef!@R7R{hXa#JSF{PSbj2>1mLq~J{IPmC|-^-EGC*d%nGg^FlG^6
zVP1X~fZD^xR#Hz<`8O@_B*XGsNMB!HUSAgU8d~#mmZ%
z$HkNN4+lk<)JGpe)mnL<5Jn)_-Z;ygi(LYHDN62Xlfs18AOr
zQw07FMDJiV-3tYNB(GAw{}ybcaFl44fY;$kA!{5JPo5tF`x8RGrcD%ZZAJiSY}H3yTVfC`yRQ
z$tjBp$cc!{iHV2`iAo6kq0#nm0MdY!)BihK8*52hR}W_^U}88pTiL<*9=O5mSeXC%
zPErGAXJzfLs$-y_=wJu)1n?Av1r)^<6eYx!`T6Aq`Gu7v#QFIpB*c{zl*NSw#gzV;
zT2(s*Vq5mf&ai)aCLI^
z0OAASE5yPKgbX04i>E3O-arG8et?yU`OjT~PlOrx`~wZpRp-}g|9{QDXQ>MC9N
z7?8>T>i;V$g(Ue!|HS$)G>3l^UxESxLK3zx7>}p~zZH)#OiY+ZTntFT);9b?qE>>U
zHa4Pye}=KLKFhs;ORRigHY|MqpKElsKl*>x=zlk3ep%$dYs7c9vix!v-+%Swuly{j
z_bcW8T!Y-KJUn4%>0gHBPyRoPfq%i&07Bv4#KG^Te_qvoll|hS3?$xv;&qm?0e7F>
zB>jQ;%`3t$CMqHzE+`-_Dkvl@E+Bm7rk~xuXWc@AV&Z}lVt_M+g!zR9MgR5!iIksL
z7?^zGA_DxPLO+qjfiV9~Z2z-cNK6!%l>+=Cf}%nKBBDSR{N3&C;s8Xe%h}|2atQbx
z2EXN2^7Hzg?3w?pDUxz7c22Of31(__CKfQ8ey=wF=+Sd^0`jDw*gtnFxVqRn*ua2f
zr~&hV{kLudU|9ij<=KiaC?G5*EG{G}EcQ>l&un*=1qB3thUrhI{*$2r)BkL8a`*%N
z_V~Z^+wZos9hd{m#=!L-OB!Gk;6W0wm=M3;1d+l4btS^&boT#{&Pcz<(_89}E1)0{{QBz(0yNFc)C|?+cV>
zK&R^c{%xM#dk_3+o)Ioqp
z3BsquBcQ}PZ2^IS5*HEP&+8`{P*KAt#3KToBPJm|PX-_~UjpF~0Br<>=Lm_<5t5wq
z!~+U?l!R2*i3BdQTskMGD@bkS&Px24Ia>b8TRou?w)^}vjUN39F~UzsX7q2fTVEB~
ziuFv_QT!0ReZxT1CeEwr-atskHMdy~B{5j3p?79{bLh^Xvd^PAsF7_M>3Lc@POh8c
z5|S#aYQ`p}W_I=t4}AUn1H!_eK6@UOkeKx9by`+-&b!>a;*aGOl~vWBT3XxMJ371i
zhK5H*zkVD0KEJTIw7jyqySIOEc!WMa(-Np({!$Y7{;B7g5`;wm&=N2SKALv
z5k4VdI8eQ&B)CL%osd~T?lKWSi=Zy`?Q=q`R`OTe^@JbmutmRBD4`*~FQUKI&wj5_
zamHi&>Jw{Gw;M_ZF&yawfbp*V)I$tVL>UUGVrX=xj1A28Odn4#Z=W-r9tDSl{?aQp
zF8-Hl8JWM8`%qf;Tfe5}KN=4HQE_(ew~{-5wHya20A>0A`-T6j3;$m(K;wVDP5~yr
zIRNPR1OVOn9#*D6K^<_$VBhnwoZB>olG)1j2JfXgOL)pbJ
z+lcRt3T!QDmi0Wz&0sP1oGvVAzoSi>{QLa-$maauV2fm9LfCbJ>n+y=WxYzr>Da_W
zuFwlG81TE{FC+LiN9+r43q1cG((`P)D61J=y?@J=XJ@WVD~GZEEpZbF8@V_>fiL8=
zOL!@p@nU|XrkTqR%Js{Q~FHR|0E>dykUWwga()Js;I!B~M%$P1p`Or{AZ%fyia;
z1$(~xM3rLcj6(Igklus5K0t46ke3D$k0#D76)d3}j5&obX8BPai9rg3SQ2xKOcIN%
zDjH^T)>=_!hJ@-busge%V%dB~*B!~X%5
z-=4qBqz#>}JUPZ3OGF2R;G`OeyO}K>4^4qrT=A!G@
z9Id2$>!fci1kYGIFutSa4#=)u9K*vYOXA7)b#pj!8q9MD-)){=Ry^P_7vc_m<>MfM
zhGW3b8t$Ukg8WZGHiC$c!tH{Y`6N^*XivS^+ObSAdeQY$gJTbD`pb$rQ{pnTD`+|>
zwT{nHERPXODd}V@r)J!i<-~$dDad7V`D8G9*yksG0db=TLBQW(NpM_Q(g~-NTk*|9}
zN=Qrf!Oor3THnpY63_MR>8xGL2glQp1Cc0UC6%KL8j&@rWaQCiahp2F9I?wZ#Y2?X
zap)E#`x~EeZ)$J!_%V}f`qGMLy=&H{>HbNgHn?dLr+s&Pes{_;>uUvSA5yi`puO_K
zs8gpnnCjMpHtCA?pqH<@`Q}mJIZfz_bV2c
z2;pnf4u2~PvGVd939nvSTL$w{t!-hElSgatUUGhC6@E>8(<=zt177m#qw&N|xNUPy
zpLCC_*|O}nueiviWYz`c=7{B`<8w{BGT2?2>YkUc7)BZvucY`NJgUCy(==1!_H|-+eKnj8rQK3|%opr)bj~PD
zle{xB8$y3@ndE-C_G>>}MvFAcu>rQnNVHO~x4!spbC0)TuZZ@&`?gH}=lSC+TZlc&
z%d$CPEcu)ylu>10P3U@KPKZbquf={qLm-yjaN=(P#A?R`6E8F?M!NGe(yfMf{S!#)
zt{Nl12H7<>+kT5<@G}Mkwm!9%EgKx{JzC)
ziCpiwA9d4_KV&Q^3rO;fHFR2?SKnO~NIyCS6}73Rbz6Pu-KOZmwx=G<_|{w0k3SSm
zK2FpUqq9~(@uhhAS;{{=1>NM)A-Ypcb~DZT&F=Y7r1{l0?8_@sSA-keJ0BK^bz*x-
z8z6k+p9?$>WGHf0GsJ5caHS2XRd_?sEtt`(a%K(Y+y{-NDv`XbbF#xV3;gPq1P?8s
zOE+HQ@&lpESu0Ds>;5nDB*&Suwl?OL9ehvx4{)PB^opx{-N_!`pYXr-aCgI7+${<}
zNjRP(&$x9ow~vA>wp$J$g0b|2UKTQ?b_Htz3#+|7pEKT%&Ygl>8&8Pyzqkpml=mcD
zG`|v@WU96UWv_Moj+>;@S#90Hc{j)%^(Yh}r=>To_eW<=LGsI6)2V&F$FL2)-p^l6
zQcgh^PC?3;lhx^4{U@VeMvjeKnCv4p4tkc81-ajTM-d;S@ys$IDLz?37ci=46*9rClGs8$?w|=&iRN%^ft*&q6eJQw}uy(RHVwGz&<^o-bWg)iZ?@KMQOQ7S9;%Y*7H1xhs
zlyO4cV;?K=wa8c|hvRN{5mkh!)1F1e#nhPPofqK)#<_PHyn`kJE08}1CpOLS9@e-x
zYB^>I4APX;_HPJ|m5S!}!uzo|FHR?|Z@~#P#yniVl?O%*=|zYZFE4%YfZG-^OUURJ
zgq0ufSscsKBRD4A{4r}z0lXp0LE1OMd-q6R$*=BLuiOdl6K?LTtWM>!-4>k6>mHFo
z2tD4B>9So?Tlkipk|(B_yDo{YYPWRUZqP(G)a*KLAS|ofS0tt%?k0P%?Mf4nZ>7JwmSW
zwOH^xgdzhSW~{!i&$V5pM@GUc#PWN|jwsd$T7>+9n{liL1!{t!#*CAdPZ1dZtc1
zBgV(x2-61B6U#^3($M`^a}eqYjV!Ll>jmnEFY>)fUuL+}*NhuK^!5)dBI~HRi<=r5
z*rA}<@E}pXr5#jrI0Bw!Oj|7`TBK7y9y}hAk{&OZ@Z@@+789N6rE2y>FYd{U%pC@O
zs4#yX`-N(S`_>b+cRVQ`1={h{FO+KcjMwO{-!)D!GaDYx&h-Kj&-GG$nL%Eha@9G(
zPUKca-@6`~R>m;)jQ3V2zP_N|`of{V#-d1L&|X4CmYehCJjV7<}4;Z|b13$cO&UTLNj*
zO~Y!nIIPvfh=%Z@4|)Q51>A};N1jc6olKK6U+3tJM#&u%9Y{gvE^%6^p{f;iYmRJ3
z&=3=d@vXARo`c0M1fI)>yGPYsE4Rq86O+>?TE{Kp4eCxORh5woqTlkHeeOF(WXr0T
zgUC$n=gbl$G`WpxTiN34aNopy>bb|}OB%KgR@jVX@h5X8M~(AIO<_R_dLit}g`Rhl
z+v1V1hBymzLM(BZZM<&+|Fzg-v!)g^zeK0#@l8=b)4Ssqtg*xCCaK1^^MTLn3?WQKq8N#{JQ
zJM>X2kiJmmLfN~oTg{WvWN~ARH&D#K;l`#*y?Fvo`1LWp^Uj*rM0Uk-{Wi_w}NB5!M=jt~(`)E>W#>^-8Ht!W%;6*0JZf`>d6;Zy4jnSk|^13dkpiJ4#
zo3bVEV+FP!xU`IS#b5+#)ZLKO6NOVF+BEGhKAZ0~3!$zJt==3XA45OB86C2r%4n2%
z>;^vtc|x|Y69rFXChphGn~FPe7TfN%3C(Zb
zImtT|AFf;{+p3UQXQHn8fOOhoS}V4|+K$oIitS6#&1^B-`XZQyGkno#0M4*sXe-cam3@5xPyL!v(vb
z=*G_H{!z_J?i@m9D5AYTA^Ydl$mWOe-^0!+&
znu7w99lIG{F}zS$qFXOzZ;udjj3X)XSy?ZP{r=)Y+YY^Y+4v7p)$zIFN;2ZGy{axJ
zO<%5-6QR}`{>&C{jKa9Vl6ZGEkPDakEDhuXu4xGPd5GlnK^_lFVf0cs$Go_mk
zY)YqtidKr3JK=`j-f-5{t@pX-&nbPX!J9
z$>$VRH=s;y=`&xy@c5Lq{8(2TF=VV=$V{w>-6)WG8Oy(QC
zt=iinIBiYFx(w+OViv2y1{g;@s;2mcYWu$zy(inepgL1G=R94$)`91iafhHgit~oZ
zP~Of#v;8>6VUGQ1+<%L2q#>-l;I+hD^i`py`>!nd`O8DYY4eGm>l%%0P81AD%gt%y
z9eKkAkH5)Yuc&;Ydc(5jByy7RrTtdqcI}Uv@L<^wqD5C58CW@gjO38tQuB@2b^huM
zFTs5%l6ETj*ly=8QyVKcqYXZ4ZWiNMYo!l_gSSV+0#(pEPm-UQ3tgf2myCtz-N@Ls
zjHrdokklIQXUtAt(~=qE&(%qmRzH#U|!7qR4l
z6K~oEnlP0t1|AGur3neMbAb&ys;Mf`kwwlb*Lwaavh0Oj0^jOlAS9EzeJ}cxvPssrsI`i#iA4jT~)Wa91JhNf*
zey*)>(c=nP%Hx5rV(2c;+($4VRk_YkLI49^sx&xV~+Y
zcIETE_4cDGu~?I(xdqFXN3Fzu#rJ6js7S3tI2XISDtm4BvG*6JB(~!5^+VHI+GA11
zX}_4RO^>i!L?#lp0p(jG
z+SapS!r^8LWg3BKuG1V`zUJbbRU6rE_j=_j=eHZN4-EG|e-TiBt{-clx^(x)oi{N>
z)HbP&HX8Bo`Ir-u9e&tG1C@|--$eSW9zS%N&O(m|uvLCc7;U-prU1FTl6Y?1{X*nQ
z)pT%Ww>^*EM=l*Rbvg$3Bt9aZ>1z3RY34@d-4pCIPm_35o|pTc^la8nY|`J@FUcO5
zZV^)W;6fuxBX9>RJ?g3AgUw!QVc8+&h6OtqlvAybiW*;<7*>`eTpR4DuvHu{8S$`O@bHoh0(M_)BI-Yo9IORN3UR_@DQF*j_v!;IUh3NwB
zd51r-3;V;A{&v|-2Y-K8zHn#f#i}W1=O4974`690i%TiFK1dl~Zq
zlIL^~CtF)8>DNb3r$6Ezj+s+~M&5a6in=fHXJxgrU(DZ_5;!a?Ns$`5WM;Qv5
z7ZvA&)Jqxuv_M-&7JEH$&-&mv&L)1GdjLO}^c5X@oZQwCG!CsC^PQuoq9;}4OOo|T
zkg1*EDah~7zZ8oOS`<|gmweymQS&n?WCo`t*NK|r=R25z-X=>;j-&9C_KfAe?8>qZ
z<@gj-i>O7EY45r2YNANTUUT=(w`peX1fy$?G{M&;yUec+FYNoAf}kU1DWBSF
z`a2VcN;{pu`jN87_CAWSuwI}_e`U!{ktaPSC+k(*6@5wlo}b)O!r+na?39do8iN;N
z>Q>Z3hf8XZ$V0LV9(hhfk~{Or4WsOEERH(|w>brsW7Kiud(sUP(M5H=Tlz?TPYm1~e=Wp$A3A1A
z4_hn~b1kg*8yrpy7lsdoU8_iZdsM>A&H+|U1bJyn<$FIa1BTqLy#7E{rL+=gUL(H
z$-Lq?meeAOqs~qw=l3U=asl$>22s(N%jkw-NRsv=b-C>v7FB79Ct6G2C4(v>6;}5p
zgq#nyE+QbEiLKtWvMWs5$#z>hQOXg+9l%?Zjk`C4=2GWowmT|dsTI>4L*%LZUV5WaF__3D1(fpq=CdEq
z9JxW1NmT4&uC;b{@0@}dksKd9$iQoe!sguer1i%Om#AoTI6d|Wl3^$&%EQ;>ve3*<
zp5hK*D2n-$sBUoC_|8!XD3(WJt2^Pj_@nhih~p5(S5H!4$QZndJi3rU%aJ%I@bWG-
zL)897S7f4YY~UAQ&LC=vJ5-~2FNR-Lk!|c2GrNReyfJS|+1@)UF_=@eAbaM(R0FTrdD
zA$j!Dr=q!1ls5Ur{7%m`Yt|TnlL*s&5idUM+%PuAkgwpwNHEv4GMrMm{`EswRRs_COP6`F!kl|NUGENQXRYKUNGCbU16B+k{diHtn7BJ^M=GFpS-Y4yqPMW7uoXiuV`*zluD+R!^
z3fIo>1-)rpbC(B4JjLr$*p<;(O8nYTF)Gj3&9}O3V9816Ilj`pWon0}7a2A;!8N
zBFe7dd>R)fs2)3sDKtV&UqfPf8^j*VMGGdZc<48e+FnbunNLN(Qorp~c3#P0DQ+~w
z3#`>uG4}w%_wp2!jD37NTj^zV4pCxAl}8`kGXIccUGZq=*zt~j@1vc^2U9WYfFJu1
z)nTky{Z9+*6W26piSs;E6BOpF0wU@yDsow=Uz)-l)Xes7r*-d=BY?=fnDb%o5{wrF
z=Xl>dgem9t`?2F+)B!$BL~X&H76RD@qYrJs!^Tv0BhY>s4J2NCclQou;Tr*!oCtqB
zu6)Pi^jFGFj)Rs79oEmq!w--r&_f-9of>2&>=ab?LCgvH&L)Z0-wv6|+x>d>PC<
zNkJZir_OvqI5uaKSf9b2wHzP^u%&{)|jLK1axxbM1
z6vWGMeQ#maQ(aUc?l}i`4u_8t#rXE@%Me*%Od9xfaTJG%7`zq9&oVBQ$)pX3O-{0=
z>L=XqI9R#2!`aa;mELtm+p`Q%Y$zZE^aK=Hngy|ep%Ep1NfQ^+r3X37%=R1#xOVQQ
z7Q$;XS2|xV;jFr4%kR3#4YWyF%L1FtF+^>Ej27v|bdzoDCo1B7&1+%knU(4ZER&@#
z;k#4N$5Rm5Hma5pVkGl^$wm8s7(<#!BQ1uOpdinZpN>ac4uP$+F-$qFry%Vu1b|JP
z@}YBGW9BOJ1w?2o*AR@CyXg>gRGqDUlS+!_tV&Y=!S*dzVhSe=k3oncOu
zo8$2=-|J-g5ZrDS*!OEB^Eg^jnGOL-`>}6f4cEBk$4xp$$$uvzD<8En)ibcmW-aYeP-R#?BlwJ-yeA$I$RqRyATG
z;uO?c9wg3W^0_ICK=0hjquxp*!xp
zYz78A%yM7v#xE+0juoJG=?f}~t
zLB3;v6{ViRI!v#jOekeuu~emF*h6(jn#H(zCQ>5_R?T3E+CqHNgD;UE%MIFv0UIX%
zNABGxMic_zJ~U*r9m8iz@f6wawX<$tJQlmYGU`ND-iaa-EM*2g7IEi8^XdArD_)2th%x5~)5$l_=nlk`9
zyw5!>QK~N7qmh%Czf!V?``Ug>@TuT-Bc{^EF^anmQc=Bgl&wc!-^K`T*Pd-Kl%BVv
zF9f3?_i(7Q&<5$^xNw<-(N>7!cHk346CbL#{pcD_
z(IlvZf(g>xd%SXltGKEr*-Wv}F}kRP@3j3%diVP_I;@$&rX7(HCc9`dOL(Ej$>TBq
zt5T}wU60#PPzM{SEV2zVs@pf)IcWVf#qKDBZ@&_<*#-^|zj}xJnik%*<_~C+*|l&bPE>XMraEMxVRWH=)cev3N1t-t`&1_nNMmpQB@O4O3I=u-fms?GdxV}v
zP1>5QQ0{?bhqG+pbI5nr-UZy&wH+qnR9d4|$Kh7g4Tk71Pn3n8RYuQ)zpUZ3=Vi5Y
zW#9@j4IyqI+{a5qryxDPUg-w<0bI@d_Wozi)9ohN7L+2?Xh80cuN3(GSY6B5wX>oPH9@}
zWbo``LPQ8X_=n{yv~0#gb;F3=yVnFx2$CXU88LbeO!KEJ1N%vmZ`$$dvXMC_?MLR2
zt2>N#>b&{cO&-<}(?~gZ4r*5ha)&pWdi$xe#qv%Nr0Aqo+}&o??uXa*q|h?Mq%1s^
zuXIRpE^&cR1V;hc6q~PJ4zvId&A-f{rF)Ad!a;X2Rn{?=!=x*@FVi@kcQm%X3#szA+&PZP
z#I(OjPls_|=g{+r_Y2*zxu~kBZ@?0M@5RpE8w-nc*=>6A
z8&Hh8@>D}1ka(c^U4%Bb8T@8q{NiN=GMeLz7@NOTNsk^~^ZF|30SjZfVPWx{vi&3(
z5*1EcZ53smc$6NfeoRlvRJexC@WWslX$ZT(OT(wA-O-cnx0^ZJzfOX{?{pw|JHvjrGg*?I
z+xVJo#{V7rk*bVk>DR&+O}q_Q>xqWH2MrAvds$
zol9{PUm&R&ukBZbL&&QF0?!?S50T5M$xhFZ`9I(;4EL$FU2Y5d6JXP=D9HI=R0*{a
zU%wH-@udcJM>(2d1$${%6>}m9PxXgy-kxh_xDOohfIlPtLUqn%Dy~9jyhLfi-7el~
z;GMI9$pA?KbS98yuQj}7el}r7g<}7~WKMs!z#i||3?zA>lSVG*4WW}8u*D3tr{@(<
zi5ZhIv7SwF8$;4PZVd~Mc`P?;!T2QhvRBe^6+Rs%DN-jk3$A_iP|_jEW)i%GC~7vv{=L89KF@6fcX#@)`AM4znp~&MKEjG?y2=P@*G3lT`JG|lw
z1>_@>%hB3~kxc4|^V^Ca(4N>hOzrfhKNA^tA@+oqFAg&9zTelq*6rJU-GSckzC;=Q
z0^`(6iitg3#D~;ISHqEx*Dqpo**<*X68i>gf2||BhqzwzqXWGl;)7h>R@vCT@R?$=
zd+@Q*_^9@HEAFbOI@kOP){LtdGero
z^`vjb%@@tX(f9lNmSmr;2wt?bZ|^Si=X}gpB0)y6@&Tt^Ar7vD(8v1lG{o|e$d&mL
zG+$O~<%-?EDI%(>dWFLAwEKzM#->1oh<)MRJ-JzeYI8~O(?JiKHSSu0z@bWYrm3{DcFbXSPeFJv$q3^2uM!Pe%=IZn&4Y}@6`T~p
z=RXrEb*Gvh#U|XbZC{VQ+>I12@ubuK{8>30FQC4jww1DDAAS=$ErR9;(xBfybm^;R
zvdm*%iFGODV!P;(Nk9|A5VBRAK8Je`)2`w0nZLYxKUEyU@k@Y&)O0DH3uyKQR5IfhTNjP~2%n40Qzw#*PGFq77=;foh
zz%cW+SIFuKIKAtRwLLTc!tO#LSBi#&)vcYqq`747dqE~o+n*lN?9<*Vo(ekT)G{BD6&J+g)iJ=
z-^MMyzd?aUj^l==(Mhjo&h_ms&vhvrKVy9tFZe3)jbz}Rc><3?T-JA;<^??hN~iL~nC9nERbBB3!GB04d_7>M2O<*g$^I>bX^W9|LhDIX5wT{D<2PV
z&q1dq&sA^aq`1xPN>d#0sc%!R5U<|w)dGHGEjLL46BdO8X6If-Cj097}Y5>a=UlgkTg(iv*r-I`z(73I;*U}
zE0rbeUP>a%X}E!kny^*9?z75?{NuJG$P$I&;Qd~VYjvH|B;3dq*}Y@84eW;?i(Jhp
zN}P?K#wmzn!aAY0e!YIKe(J^Cacael2?eBS0P))+S!CwZxQu$lt5Z-Qh4uk=y6T4?
z8D3E&^MVN-uPWWOxiiS`f3Bt2s?*j?PVWhTrx}EwEYxj}L5a|OlNe88G1UXgF9E>O
z_(bu0C#mj5-bC&t9U6>Xb32Gu=mocRnSP9Jn^>oCS09@a1vmeC!Yn3SX>k7P`U}il
z`-v9ADd@^j8-4K(q=*=MJT&XboP$yZLLea{`07rE;T)12#`==#>8lQT*{m<8Jx^E_7rp1HgNaz~)?0&csz-)2<^CKxTUh8ASFWa?EX
zobkc!3UDq)?A{f3-<|W^f@|Rg
z`(qW$`{s@lJOmym?p072GG&XHe~^K!v{+N!kOm4%#U4PtNqsY-sv3{!o;X62V7WW{
z>DG7tNz4@So=-r4&^uFZau2B2WqP{}{BscF<6?qg&_z(%*Sf;n__7;xmrvN6N!B9-
zsVYa&!2UWQXvr<=yPxJ`^x%L^uhb#p>+_|NhMbe_aD_x}I}}YH@r^H3ZAQmKm+g?`
z+Y<$=0!i&|?$7X`F<*(F?2EVAuW!vgYG*95=9wrnZ?c70Kc^bU^w8RL2_}(XftpS9
z^;eO-m6aaWoeu*`g`M1>$V1dICPSjjSA81{Nkj*4&L&v8;AU`uFu<`817^D7M@L-p_!UQccDu%D?JWPIm2FUy_#AlS)xt*Bvq=k1lLYk-|zmd6rZw~=K
z5CIOqn|P~&P#V@KvYZ@L4TaZv>wbzMc$)h0=*i40rdrt^sjd0esJX+J@bUb;hHik-
z5vmi{^9@nhek=k@LeaCA1yr7bgqk;i)G_V>YPpN3^#?YbJ>5G&m9I8o%}eV67OCQ_
zy88iz;bK~HpKrO%VRKGCX=%78RtRZn+|Z+%P@e9LzJ#;sj=b+ac~M~-LL0l_sh-_@
zoq)2sS5_65vEwnD%3azVQ^Oj&PHJ=Hb68+(~PCQOQAa|S2=XXj}
zT24U<7N#)*F<^Oflka%U0U3jsWo@F>1?JnN9G-j>x-A#rF8ErMh*4}l7$hKl_4lu3
z&Oz`YtcQFvvsG`^thMUY$cnB$Ba*zJRd2Af7l6yQR#{b}uG5b3_WCZT!}2&&cZMz0`9ecf(o~8(I4#{&V;phN=6rOVl7W#tEZrGNE5CJ)!tq4
z4fg`F@eGmMV{p68|3P4beL~EWt5JmdedywtH0r=-pm?{8SsA|%q3SdSh0-lHx0-Sb
z;GyW}{>F)1ljNfrA8Rx8CoX--ED;&x(e}{LhRfL@SqDG=J
zYhX_#W1et8Q^CaE5TZ`l_w@@=T|{k*UhKx@HxB67^G0u%n>4e(l{+tZs2<`UX3RM#gw>>}8RYOkDF9~lV}R(VclrKI!d?Hh!R4#XQP1_@gS
zA*U8zPH+h*hV;>HtP3Qu<>lQZQ?BpN4#SOrsirJi-CnKVP#Rv}SaJO^=rlpPbNQARW4l$4l;~;pH`r7bEU0Xgvz@#B
z$IK9|cZ!BDe`M{UK5W3LJht3Kcz&PJ(w*ECYqeOq7tgM)p~C1Jo1PvWtT?pIc9B<81_v1sYQ3k
z$R{UtrOU}SJvWe>n{U~QNntnerKz=A>34U?f*!ttQr^yvPaD38r;4W3J!Cr?ziVKO
z?0elmb_%LqIpRE=j6DU>J!8ehSJy*EfUv(f*PO~!t0F7w~3w*z&B`aU%
zhw&KQf7BEwOh@PMIE1w~Y#$8Y5`G;WBcvAo(O~~_(d?kKc;BEfOSUZ25d29kG?psk
zNlEWPv;{LVmUQsomL-3l;|{k)Tb#Pc`-2LBwvQKwR;p|9*|qWGff8
zg&KDCdFg5;<$Uf>&UJR(&`247cEz_V@=nzTO|EeeyZF-0m+ib9FZ7=HJ8*o%4DS~5
zJ(ET7h~)1QW9uv_GC`wM0fQ&1Om^RUMBZgd@6Ty}%p%177`}24#+rzse&@&g^obH-
ztl7>;1I!TEJGu7f-s)q25H>@dQ)bUj(Er?>tf)~=b@(>M!8ma~{``3csPR=gV@K*k
zDv!RJlQ`S58;~OkCsY^l<=eA51yor}MN!n*4aD~6GYuB6B{IhwWa*FzD;~OsI
z7_S9fx6I#%+%rD0uqaA-Zuk7r;I|IFB5DH;eT_<+2P)QTgZuT;en`6?oAV2$W*+7z
z*#l*vY`Nz}N1xSd=poom9Jf3t3ph1mJ$8-_RR^iL9#fzH&KW%*%s?<~X;<`R3kzFm
zaf2+EanW&t+dH=I<;eu;alQ5%hIFZ76nX^lAXKv2bOcd3=ST12sdwtmb3J}1Z067x
z^nl^P+RAxqmTFiQTmut?3T4n8-M!$489;sf2BlF?bsj86>~U6)NF&({$)qe7zh=
z!F#+x`&Kd0KmB@_*(Zs-OR7=Bw~h6)ymH+Nxjrnhd2xwT^P*J2?Z@?pCy1hkhP!tr
zEx1f?klj&y>#5GH>4x_Jj07!IO&JTjHC4&9J3aO@HCvR)052uo2!37XkS_l~!K_Z3
zF3@jzpJNOBX-^}5X9c&0&uLWb)qg$5faW+O>+AY!NCJ&rWFd*o@Mv
z@pOvJwU80*s@FOhRJ2hu$EZPkSjz()e66_i1f#<}m2o<8F$Ju7L#cEkJePRwMU3o~
zR0y8w!6|yu)(*glTf*1)1*zNxU-47#N~fh0=VruC`3$rAK9`_=dRe7FHx9=2dQfQK
zYRmgjF3U~ciAhF}gvDoBlqq?ZToCRf)X*u&cxpi8fpiDh%0X9!R5xvRB>rLKf=^OB
z+ofzN7Y|PcbS7o%@%{rdwM?@SIhNP)+_`!;UmHUEXA7^4V$YYQIlKbtO1!7goget9
zEGKLC4nzIE;c?pe2)Pl|6TJbFuGd4=x?31Vl|bU0b8nvx>4($Ye0&$Gl0*5aw9=Hk
zSnXxWAhMNDKHno0C!d*n3tPrT_~1bOMNLN{w?p!qn;|Mo1jO5JlzINI1}$Za#FU7j
zH!qtTqzI~&b&AaGl4G$|)>z5;TZ2lcpma1=Wj5(
zGa4>yJv)y}M~50PK#S0jCUqr>4}o<7mB(BdWCrupTtXN|th|fuC
z_>u8~q2_5&9(mR?jxF|hPrci-m*iJ(7vQOrJu!F(e%d{I9!_CF+`C^*b$MQJ7cKaz
zkX4mVF9XTQsPBoVy-sRPEgSd1TrgdcDJ4VCfVd~(mY!GAW!jt%evF9Fr`tNKME51V
ziQrq$(E~aAl`bteBnsDgc01@mA$#-G!W8%osDlVEX
zc2&5)6VK2yHZ^ZMH(e8Qkz&f|^5=N}%Zps|tzq2`7?^$DrptZ3wCA;#>7<9ZB`J{S
zT#EQ?EM_FmsU~s^EZ|xSLjtVS0(2K|R3ybkEA4T~#w8gwJaUMcPKl0CeeO&oEYN$!
z-T2esmcvTwu%0KSTRe|ygdl6CCdp36Y;_>kT)OAutRUBS!^KR)XFuXfo`ehXXEfD+
zBRL*p*dEcz5A3VI1%ofPa?&)6bPC+=k?M|8qdx_1MQ9@sN@n08wu7~UvME~F2|
zh^ILkvCC`NX0Y*oyg*`T$Q1IpHQSB!1%D{#+7ly)P?LCHQjGgzSBWdd9M~sqb$`@rnXQ0juZdJPR
zo?pr&mZRlO%vB~Gld{i;oICxIvWWdzuWs~E;j)?puD?;R)1jO~+UX_$C8
zwOK*^#m-YEt94*b#^@x*YX0t96-jHw_IJ{%@W+Dg*j$GZh0;bmcHPkTk6WRi6IBdA
zSSL+yulzWod7ksc)h{(~o2wtxPs(0+82>3@Y{7$8BH8Ih$wIChnZF^`408_Kc`hzt
z<189Op;qs$f=kFy(=MHoTa1SinJh7-7U%k!{|)Oh7GG!M+?Wxa(q
zt)6G3VJN$~-$KzhsJ(QHDmY)S6}n#=^#~GDeL(Slw12Idpd@CEcA4O1Cg{*Uay}{@1$eez+fJ=AC!#
zc=kT~#D0$G%KCGogY(h%;_B`EGT2%|NPPheziYdD{TeAx&-^+<_*#;ydTjHW`knvq?}33wGy_(#AO+7(B0X*B>(I!!vSs}ktH_yat<@Xg}>K)?~5qGAWb$(BFmTGi`rta#)J
z&@_Mi22HH^u{0ZQG8}u4E2?J5_>d$Xm)P%)%bc;h4OR2yawzE&=?duUEwWA3j*+`6
zv}