FactReel 0.1.2 is out, and I'm looking for first-time contributors (11 open issues, none needs API keys) A developer released FactReel 0.1.2, an open-source tool that generates short vertical videos for YouTube Shorts, TikTok and Reels from a user-supplied list of facts, with an LLM writing the script but restricted to those facts and a facts-only fallback if generation fails. The update adds Spanish documentation, optional vision-model subtitle review and Spanish-language Edge voice listing, and the maintainer is soliciting first-time contributors across 11 open issues, noting the full pipeline runs locally without API keys via an offline mode. I'm a beginner in open source, and FactReel is my first project with outside contributors. In the last month three people have sent pull requests, and I learned more from reviewing them than from writing the code myself. Disclosure: I build it with Claude's help and review the result myself. What FactReel does It makes short vertical videos YouTube Shorts, TikTok, Reels from a list of facts you provide. An LLM writes the script, but it is only allowed to use the facts you gave it: numbers and dates are checked, rumours are labelled, and if the LLM fails there is a facts-only fallback. Voices and images have free provider chains with an offline fallback. Repo: https://github.com/DeadY2J/factreel https://github.com/DeadY2J/factreel What's new in 0.1.2 Spanish documentation in docs/es/ thanks @paolitacute Optional visual subtitle review with a vision model thanks @bhupeshmukane factreel voices --lang es lists Edge voices 0.1.1, thanks @Nurana100 Issues you can pick up You can run the whole pipeline locally with no keys: bash factreel make -c my-channel --offline --voice dummy Small and self-contained: If you want something harder: 11 verify claims in code, 6 Piper TTS or 7 local word timings. How it works for newcomers Comment "I'll take this" on an issue and I'll assign it. I review every PR within a couple of days and I'll help with git if you get stuck. Your name goes in the changelog. If you'd rather just try it and tell me what's confusing in the README, that is also a contribution.