Refactor file paths and fix typos in 2024 and 2025 pages.

Author: yegor256

REUSE.toml

@@ -30,7 +30,7 @@ path = [
     "Gemfile.lock",
     "README.md",
     "renovate.json",
-    "xlsx/kaicode-2024.xlsx",
+    "xlsx/*.xlsx",
 ]
 precedence = "override"
 SPDX-FileCopyrightText = "Copyright (c) 2025 Yegor Bugayenko"

images/2025/faststream.svg

@@ -14,7 +14,7 @@ breadcrumbs:
 ---
 
 In KaiCode'24, we received **412 applications**.
-After a three-phased review of them, the jury
+After a three-phase review of them, the jury
 made a decision to reward three projects:
 
 ![perfect](images/2024/toqito.svg)
@@ -526,7 +526,7 @@ The software we created for filtering repositories works as follows.
    * [for repository action workflows](https://docs.github.com/en/rest/actions/workflows?apiVersion=2022-11-28#list-repository-workflows)
      where it checks if amount of action workflows >= 1
 
-2. Then it manually clone every repository using `git clone` and checks if:
+2. Then it manually clones every repository using `git clone` and checks if:
    * amount of directories >= 10
    * amount of files >= 50
    * amount of files with more than 1k lines < 10
@@ -548,7 +548,7 @@ The software we created for filtering repositories works as follows.
 3. Then it excludes all the repositories that are not matching the criteria
 
 The second group consisted of XXX that were manually reviewed
-by one of jury members and were classified as "not enough quality" to
+by one of the jury members and were classified as "not enough quality" to
 compete for the trophy:
 {: .count-them}
 

images/2025/novops.svg

@@ -17,84 +17,59 @@ breadcrumbs:
   - participants: Participants
 ---
 
-KaiCode is an annual open source festival,
-started in [2015](https://www.yegor256.com/award.html).
-
-This is how it works: First, you submit your open-source repository to us.
-Then, our jury will review it. If your repository wins, we give you
-a monetary reward and a laurel badge that you can attach to your
-[README file][readme].
-
-In order to get into the competition, your repository must be:
-
-* Hosted on [GitHub](https://github.com)
-* Larger than 4,000 [SLOC](https://en.wikipedia.org/wiki/Source_lines_of_code)
-* Older than 12 months (since the first commit)
-* Younger than 60 months (since the first commit)
-* Not yet a winner of KaiCode
-
-To win, your repository must demonstrate the highest
-quality of code and development processes.
-In particular, the jury pays attention to the following
-(in no particular order):
-
-* Clean code
-* Design choices
-* [Coding conventions](https://en.wikipedia.org/wiki/Coding_conventions) control
-* [Static analysis](https://en.wikipedia.org/wiki/Static_program_analysis)
-* [Unit testing](https://en.wikipedia.org/wiki/Unit_testing)
-* [Integration testing](https://en.wikipedia.org/wiki/Integration_testing)
-* [Code coverage control](https://en.wikipedia.org/wiki/Code_coverage)
-* [Requirements](https://en.wikipedia.org/wiki/Requirements_engineering)
-* Documentation
-* [Git branching](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)
-* [Bug](https://en.wikipedia.org/wiki/Bug_tracking_system)
-and [issue](https://en.wikipedia.org/wiki/Issue_tracking_system) tracking
-* [Code reviews](https://en.wikipedia.org/wiki/Code_review)
-* [Continuous Integration](https://en.wikipedia.org/wiki/Continuous_integration)
-* [Releases](https://en.wikipedia.org/wiki/Software_release_life_cycle)
-and [semantic versioning](https://semver.org/)
-* [Licensing](https://en.wikipedia.org/wiki/Open-source_license)
-
-This doesn't matter:
-
-* How popular is your product?
-* What programming languages do you use?
-* What is the license?
-* What is the programming paradigm (OOP, FP, etc.)?
-
-One GitHub user may submit only one project.
-
-Neither jury members nor festival organizers are
-allowed to submit their projects.
-
-We reserve the right to reject any submission without an explanation.
-
-## Rewards
-
-There are three nominations:
-
-![perfect](images/laurel-perfect.svg)
-Perfect Product:\
-$2,048
-{: .laurel}
-
-![excellent](images/laurel-excellent.svg)
-Excellent Product:\
-$1,024
-{: .laurel}
-
-![awesome](images/laurel-awesome.svg)
-Awesome Product:\
-$512
-{: .laurel}
-
-The money will be sent to you in Bitcoins.
+In KaiCode'25, we received **112 applications**.
+After a three-phase review of them, the jury
+made a decision to reward three projects and the steering committee agreed:
+
+![perfect](images/2025/faststream.svg)
+The [ag2ai/faststream](https://github.com/ag2ai/faststream) project (4.3K★),
+a Python library that simplifies the process of writing producers and consumers for message queues,
+demonstrated **perfect** software development practices:
+   code style control,
+   continuous integration,
+   automated testing,
+   versioning and releases,
+   issue triaging,
+   and contribution management discipline.
+Source files are small, well formatted, and properly documented.
+However, licensing is not under control according to SPDX requirements.
+**$2048** was the reward.
+{: .winner}
+
+![excellent](images/2025/pytorch_optimizer.svg)
+The [kozistr/pytorch_optimizer](https://github.com/kozistr/pytorch_optimizer) project (319★),
+an optimizer for PyTorch written in Python,
+showed us an **excellent** codebase:
+  well formatted and documented code,
+  CI,
+  automated testing,
+  coverage control.
+However,
+  style checking is not part of CI,
+  build pipeline is rather weak,
+  there is a lack of clarity in package management,
+  and no license control of source files.
+**$1024** was the reward.
+{: .winner}
+
+![awesome](images/2025/novops.svg)
+The [PierreBeucher/novops](https://github.com/PierreBeucher/novops) project (418★),
+a universal secret and configuration manager written in Rust,
+showed us **awesome** coding practices:
+  issue triaging and community support,
+  continuous deployment,
+  automated testing.
+However,
+  they don't have a style checker in the CI pipeline,
+  module placement is a bit chaotic,
+  PRs don't go through the full build pipeline,
+  branching is a bit messy,
+  and no badges in the README.
+**$512** was the reward.
+{: .winner}
 
 ## Steering Committee
 
-These people help us decide who deserves the rewards:
-
 ![iakunin](https://github.com/iakunin.png)
 [@iakunin](https://github.com/iakunin)
 {: .jury}
@@ -109,11 +84,6 @@ These people help us decide who deserves the rewards:
 
 ## Jury
 
-Each member of the jury reviews up to four projects. In
-each review we expect to see "good", "average", or "bad" mark in front
-of every quality dimension listed above.
-The sum of all marks constitutes the final mark of a project.
-
 ![h1alexbel](https://github.com/h1alexbel.png)
 [@h1alexbel](https://github.com/h1alexbel)
 {: .jury}
@@ -154,22 +124,6 @@ The sum of all marks constitutes the final mark of a project.
 [@maxonfjvipon](https://github.com/maxonfjvipon)
 {: .jury}
 
-## Important Dates # {#dates}
-
-Project submission:\
-~~31 May~~ 9 June 2025 ([Anywhere on Earth][AoE])
-
-Authors notification:\
-~~1~~ ~~10 July 2025~~ 30 July 2025
-
-## How to Submit # {#submit}
-
-Submission is closed. See you [next year](/2026.html).
-
-You may submit more than one repository, but only one of them may win.
-We may reject some repositories without review, if they are coming from the
-same owner.
-
 ## Participants
 
 We received **112 applications** (excluding duplicates and broken submissions).
@@ -279,7 +233,7 @@ The software we created for filtering repositories works as follows.
    * [for repository action workflows](https://docs.github.com/en/rest/actions/workflows?apiVersion=2022-11-28#list-repository-workflows)
      where it checks if amount of action workflows >= 1
 
-2. Then it manually clone every repository using `git clone` and checks if:
+2. Then it manually clones every repository using `git clone` and checks if:
    * amount of directories >= 10
    * amount of files >= 50
    * amount of files with more than 1k lines < 10
@@ -301,7 +255,7 @@ The software we created for filtering repositories works as follows.
 3. Then it excludes all the repositories that are not matching the criteria
 
 The second group consisted of XXX that were manually reviewed
-by one of jury members and were classified as "not enough quality" to
+by one of the jury members and were classified as "not enough quality" to
 compete for the trophy:
 {: .count-them}
 
@@ -351,23 +305,18 @@ candidates for the prize:
 * [TrianguloY/URLCheck](https://github.com/TrianguloY/URLCheck)
 
 Then, we asked our jury to review all projects manually. Every project
-was reviewed by two jury members.
-The results of reviewing will be published soon.
-If you think that your project was disqualified by mistake or undeservedly underestimated - email us, we'll review it once again with special attention.
+was reviewed by two jury members. The details are here:
+[kaicode-2025.xlsx](/xlsx/kaicode-2025.xlsx)
 
 ## Sponsors
 
 ![yegor256](https://github.com/yegor256.png)
 [@yegor256](https://github.com/yegor256)
 {: .jury}
 
-We are still forming the board of sponsors.
-If you are interested in joining, please [email us](mailto:[email protected]).
-{: .firebrick}
-
 ## Organizers
 
-These people organize KaiCode (in alphabetic order):
+These people organized KaiCode (in alphabetic order):
 
 ![maxonfjvipon](https://github.com/maxonfjvipon.png)
 [@maxonfjvipon](https://github.com/maxonfjvipon)
@@ -377,8 +326,6 @@ These people organize KaiCode (in alphabetic order):
 [@volodya-lombrozo](https://github.com/volodya-lombrozo)
 {: .jury}
 
-If you are ready to help, please [email](mailto:[email protected]).
-
 [form]: https://docs.google.com/forms/d/1nUlL2xvL1OOy3LoVF-g7MfB-9yeG68XB2wXW4MAoWrY
 [AoE]: https://en.wikipedia.org/wiki/Anywhere_on_Earth
 [readme]: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes