From acd484f34ec26bb0f94665198f9efdbc40d622dd Mon Sep 17 00:00:00 2001 From: John Bampton Date: Fri, 13 Mar 2026 17:43:24 +1000 Subject: [PATCH] Fix typos in Markdown files --- GSoC-Ideas/2026/Bot.md | 8 ++++---- GSoC-Ideas/2026/Zplit.md | 6 +++--- GSoC-Ideas/2026/index.md | 4 ++-- GoogleSummerOfCode.md | 6 +++--- LinkedIn.md | 2 +- 5 files changed, 13 insertions(+), 13 deletions(-) diff --git a/GSoC-Ideas/2026/Bot.md b/GSoC-Ideas/2026/Bot.md index 8a0b96c..de839f3 100644 --- a/GSoC-Ideas/2026/Bot.md +++ b/GSoC-Ideas/2026/Bot.md @@ -2,17 +2,17 @@ ## Background and Motivation -As our organizations are becoming larger, it is becoming increasingly more time-consuming and harder to manually manage our Discords and our Github orgs. +As our organizations are becoming larger, it is becoming increasingly more time-consuming and harder to manually manage our Discords and our GitHub orgs. -We need a bot capable of automating what we do in both Discord and GitHub and, especialy, in the interaction between the two. +We need a bot capable of automating what we do in both Discord and GitHub and, especially, in the interaction between the two. -Although there are many discord bots and many github apps, we are not aware of any bot/app that integrates the two in a way that satisfies our needs. +Although there are many discord bots and many GitHub apps, we are not aware of any bot/app that integrates the two in a way that satisfies our needs. We believe this bot would be useful for other large organizations as well. ## Overview of Tasks -* Implement a Discord/Github bot that is simple to use and that automates synchronization between the two. +* Implement a Discord/GitHub bot that is simple to use and that automates synchronization between the two. Candidates are expected to refine these tasks in their GSoC proposals. diff --git a/GSoC-Ideas/2026/Zplit.md b/GSoC-Ideas/2026/Zplit.md index 19b104b..a4d9046 100644 --- a/GSoC-Ideas/2026/Zplit.md +++ b/GSoC-Ideas/2026/Zplit.md @@ -20,10 +20,10 @@ AOSSIE recently invited contributors to submit designs for Zplit. While Zplit is AOSSIE had a discussion about Data Models for Zplit [here](https://github.com/StabilityNexus/Zplit/issues/19). It is required to implement the selected Data Model using `freezed` and codegen, and then implement app-wide State Management using `BLoC`. This should be done in a decoupled manner, with Automated Tests in mind, and should be reliable and robust. #### Implement Cryptographic signatures -Zplit will use Cryptographic signatures to sign all data transmitted between devices, to improve security on the platform. These signatures will be made using a combination of device-specific characteristics as well as self-identification information filled in by the user. This allows everyone too verify the source of any data blob recieved by their application, and reduce the risk of financial scams. +Zplit will use Cryptographic signatures to sign all data transmitted between devices, to improve security on the platform. These signatures will be made using a combination of device-specific characteristics as well as self-identification information filled in by the user. This allows everyone to verify the source of any data blob received by their application, and reduce the risk of financial scams. #### Write decentralized communication algorithms -As Zplit uses decentralized methods for all of its data transfer, it is required to write the business logic (aka algorithms) that the application will use to send and recieve data. There will be multiple methods and options for the end user as described in the [Zplit Repo](https://github.com/StabilityNexus/Zplit/blob/main/zplit.md). These will need to be implemented from scratch, preferrably using strongly typed Dart code. Using packages where available is allowed and preferred. +As Zplit uses decentralized methods for all of its data transfer, it is required to write the business logic (aka algorithms) that the application will use to send and receive data. There will be multiple methods and options for the end user as described in the [Zplit Repo](https://github.com/StabilityNexus/Zplit/blob/main/zplit.md). These will need to be implemented from scratch, preferably using strongly typed Dart code. Using packages where available is allowed and preferred. #### Implement stablecoin settlement Another key feature in Zplit is an option Stablecoin settlement. Contributors are required to implement this, such that users can settle their debts on-app using stablecoins to pay off each other. @@ -35,7 +35,7 @@ Contributors will be expected to write comprehensive tests for every feature the It is necessary to implement CI/CD Pipelines that can automate the build and release process, as well as add a check for every PR to verify that all changes pass the tests. Along with this, other Workflows will also be expected, to improve Developer Experience, like a workflow to check for untranslated strings after every PR. These workflows will be implemented using GitHub Actions. #### Deploy v1 of Zplit to Play Store -GSoC 2026 Contributions should conclude with a v1 deployment of Zplit to App Stores, to get the app to real users as soon as possible, and then later iterate on the App with real world feedback from users. AOSSIE already has a Play Store Developer Account, so the Candidate will be required to setup the new application here, along with filling all data safety questionairres etc., and fulfilling all publishing requirements. +GSoC 2026 Contributions should conclude with a v1 deployment of Zplit to App Stores, to get the app to real users as soon as possible, and then later iterate on the App with real world feedback from users. AOSSIE already has a Play Store Developer Account, so the Candidate will be required to setup the new application here, along with filling all data safety questionnaires etc., and fulfilling all publishing requirements. Candidates are expected to refine these tasks in their GSoC proposals. diff --git a/GSoC-Ideas/2026/index.md b/GSoC-Ideas/2026/index.md index 2dc2f53..9762a93 100644 --- a/GSoC-Ideas/2026/index.md +++ b/GSoC-Ideas/2026/index.md @@ -38,7 +38,7 @@ The skillset needed in each idea is shown in brackets. ### Theme: User-Empowering "Sunny" Tools -**Theme goal:** empower users to do localy, in their own devices, what would normally require them to depend on cloud-based services. +**Theme goal:** empower users to do locally, in their own devices, what would normally require them to depend on cloud-based services. **Ideas:** - [PictoPy](PictoPy.md) _{AI}_ _{Desktop}_ @@ -83,7 +83,7 @@ The skillset needed in each idea is shown in brackets. **Theme goal:** ease community and team work. - [Org Explorer](OrgExplorer.md) _{Web}_ - - [Discord/Github Bot](Bot.md) _{Bots}_ + - [Discord/GitHub Bot](Bot.md) _{Bots}_ - [Ellena](Ellena.md) _{Web}_ _{AI}_ - [Agora Voting on Chain](AgoraOnChain.md) _{Web}_ _{Blockchain}_ diff --git a/GoogleSummerOfCode.md b/GoogleSummerOfCode.md index e48c845..5ce1e34 100644 --- a/GoogleSummerOfCode.md +++ b/GoogleSummerOfCode.md @@ -31,7 +31,7 @@ Please read our [AI Usage Policy](AI-UsagePolicy.md) carefully and adhere to its The main selection criteria are: * Understanding the project beyond what an LLM can tell you is a must. Do not let LLMs define the "how." -* Pull Requests made to projects in any of the above-mentioned github spaces. +* Pull Requests made to projects in any of the above-mentioned GitHub spaces. * We take into account the quality, quantity and difficulty of the submitted PRs. * Quality of the PR involves not only quality of the code itself, but also of the PR's scope, the PR's description and PR's readiness. * Submitting PRs with code that was AI-generated is allowed, but you must be responsible for the code. Use AI responsibly. @@ -45,7 +45,7 @@ The main selection criteria are: * Our GSoC ideas are intentionally a bit vague, so that you need to fill many gaps yourself with the help of mentors during the application phase. We also take mentoring capacity and project capacity into account. So, if too many candidates apply with proposals related to the same project and -that project does not have capacity to have many contributors simultaenously or does not have enough mentors, then we may be unable to select even excellent candidates. +that project does not have capacity to have many contributors simultaneously or does not have enough mentors, then we may be unable to select even excellent candidates. We appreciate perseverance. We have had many cases of candidates who did not get selected in one year, but continued contributing and got selected in another year. We take into account all your PRs, independently of when they were made. Please list them all in your application. @@ -109,7 +109,7 @@ During the coding period, the selected contributors will be required to **show w * Communicate at least once per week with your mentors through messages in the public discord channel of your project. * Write a post in Twitter and LinkedIn about your weekly progress. -In order to pass an evaluation, the number of weeks in which you do not do any of these tasks should not be greater than 33% of the weeks preceeding your evaluation, unless you have completed your project ahead of schedule. +In order to pass an evaluation, the number of weeks in which you do not do any of these tasks should not be greater than 33% of the weeks preceding your evaluation, unless you have completed your project ahead of schedule. Furthermore, **once during the coding period**, you will have to present your project in one of the weekly meetings. diff --git a/LinkedIn.md b/LinkedIn.md index cba0e23..5beb3e1 100644 --- a/LinkedIn.md +++ b/LinkedIn.md @@ -39,4 +39,4 @@ From 1st of October 2026, she may state her role as "Member". He manages to have his 1st PR merged on the 10th of February 2025. On the 1st of December 2025, he decides to become a mentor and starts mentoring other contributors. He continues to contribute directly to some AOSSIE projects. He may state, in his LinkedIn profile, that he was a "Contributor" or "Software Developer" for AOSSIE, from 10th of February 2025 to the present date. -From 1st of December 2025 to the present, he may additionaly add the "Mentor" role. +From 1st of December 2025 to the present, he may additionally add the "Mentor" role.