The choice of the project was quite straight forward for me, I had used ManimCommunity in the past for a project in collaboration with a ULB professor and I had done side (unfinished) projects for algorithmic videos using manim, moreover, I had contributed to a [manim-related project](https://github.com/kevcen/manimate/pull/1) in the past (project which is now kind of dead), so I jumped straight to Manim without looking at other projects.
### What is manim?
Manim is an engine for animations, designed specifically for math animations. It was developed by famous math youtuber Grant Sanderson, also known as [3Blue1Brown](https://www.3blue1brown.com/), as a personal project for his channel.
The main problem of manim (known as ManimGL to differentiate it from ManimCE "Community Edition") was that, as it is a personal project, it was difficult to: mantain, install, use efficiently. So, a bunch developers forked the project to what is now Manim Community.
### Licenses
The community version is based on the 3Blue1Brown manim license, which is an MIT license, the Community Edition has its own MIT license.
## Journal
1 October: I contacted the developers on [discord](https://discord.com/channels/581738731934056449/1023550532914266142/1290610379361091616), which then redirected me to the issue #3495.
Manim is pretty complex for newcomers, its users may not know how to use python, they may be math teachers that just want to show cool animations to students, or if they do know Python, they may have only surface level knowledge and learning how manim works may be too hard, thus, the need for a guide for new users, which is the objective of this fork.
The objective of my PR is to complete the incomplete work written by MrDiver, the author of the fork, who had left behind the needed code to complete, I needed to fill in the text part and show the animations.
10 October: I opened a [PR](https://github.com/MrDiver/manim/pull/5) on a forked version which handles the guide part of the documentation. This PR was not perfect,
it contained minor imperfections about phrasing and I had also forgot to add dependencies I had installed on my pc to the dependencies manager "poetry". But, I was able to fix some errors which were present in the documentation, namely, dropdowns were not working
15 October: I fixed the dependency issue and added further documentation about the animations. Unfortunately, I have made another mistake and the reviewer asked me to make a minor fix. I also added the fix to the dropdown to the main documentation for other users who might want to use it in the documentation.
19 October: The PR has been accepted, but I will continue to work on the documentation as I am invested in it.
## Conclusion
This was a really fun experience that I had not expected to be this way, even though the maintainers were nitpicky, it taught me that what I think is good might not be good for everyone else (cfr. the multiple corrections on minor sentences).
It showed me how OSS communities work and that people do not have all the time in the world to follow your PR, but will still go out of their way to review your work and give you insightful tips.
#### Book
I have presented "Maledetti Toscani" from Curzio Malaparte.
