Mozilla Otari Hackathon - Devs Wilding Online!

Hey! Marcus from Mozilla.org here! Thank you for sharing interest in the hackathon! **⭐️Before beginning, please star the Otari repo, it helps! ⭐️ [https://github.com/mozilla-ai/otari](https://github.com/mozilla-ai/otari)** # Welcome to MozFest's Developers Wilding: Online! 🔽 Watch this short welcome video 🔽 [https://youtu.be/6B0Nqao86zE](https://youtu.be/6B0Nqao86zE) **–** **You're not signed up yet.** Please read through this email to understand the hackathon, then follow the steps below to sign up! ## What is MozFest's Developers Wilding: Online? It's a two-week online hackathon that kicks off October 28th (the same starting day as MozFest in Barcelona) and ends November 11th. # Prizes: 1st: $1,000 + 3 hours with Mozilla.ai engineers 2nd: $200 + 2 hours with Mozilla.ai engineers 3rd: 1 hour with the Mozilla.ai engineers Use your time with the Mozilla AI engineers to get mentoring, ask questions about your project, and receive feedback from experts! # What do we do at this hackathon? Finish your side projects using Otari! This online hackathon encourages you to finish any side projects you have with the requirement that you use[ Otari.ai](http://otari.ai) as your hosted AI gateway. # What is Otari? Otari by Mozilla AI is an open-source AI infrastructure platform that lets you build applications and agents with the models you choose, including open-weight models. With capabilities like code execution, web search, and the ability to connect your own tools, Otari helps you build powerful AI agents without being locked into a single frontier AI provider. For this hackathon, you'll use the hosted platform at[ Otari.ai](https://otari.ai). And because Otari is open source, you can always run it on your own infrastructure after the hackathon. # **How do I Sign Up and Participate?** 1. Sign up through DoraHacks with this info:  1. Your name or pseudonym  2. The email you will use to sign up[ Otari.ai](http://otari.ai) 3. One sentence explaining your project 2. Sign up for the hosted Otari platform at[ Otari.ai](http://otari.ai). The first 200 people to sign up get $20 in tokens at[ ](http://otari.ai)[Otari.ai](http://otari.ai) 3. Click this[ link](https://discord.gg/TqvzGH9mwz) to join our Mozilla OSAI Discord and grant yourself the devs-wilding role. You'll receive updates and be able to ask quesions about this hackathon in the Mozilla OSAI Discord. 4. Please star the[ Otari repo](https://github.com/mozilla-ai/otari) in GitHub! 5. Start a new branch in your project and start building with[ Otari.ai](http://otari.ai)! # Hackathon Rubric Read through the rubric[ here](https://docs.google.com/document/d/1-spnCZ3f2SSki8cb6FnochjchdyttUsjjxfoE6aBnF4/edit?usp=sharing) # Hackathon Submission Requirements: DEADLINE: Nov 11th 11:59PMTO SUBMIT YOUR PROJECT 1. Project name, email address you signed up to[ Otari.ai](http://otari.ai), and one line on what your project does 2. Public GitHub repository link + the hackathon branch name 3. You must use[ Otari.ai](http://otari.ai) in your project. Please link to the first commit on that branch where Otari came in. 4. Otari features used (see the[ rubric](https://docs.google.com/document/d/1-spnCZ3f2SSki8cb6FnochjchdyttUsjjxfoE6aBnF4/edit?usp=sharing) for a list of features) 5. Any PRs or issues opened on the Otari repo 6. Link to 3-5-min project demo video - Show us the progress you made with Otari! 7. Feedback - Please submit either screen recording feedback, written feedback, or both! 1. Link to 3-5-min Otari feedback screen recording - Record your screen and verbally share your feedback answering these questions 1. **What did you build with Otari, and which features did you use?** (walk through it on screen) 2. **What worked well?** (what you liked, what surprised you) 3. **What didn’t work?** (bugs, friction, anything that cost you time - reproduce steps if you can) 4. **What’s missing, and what would you change?** (features you wanted, what you’d do differently) 2. Written feedback - Please answer the following questions: 1. **When were you most tempted to skip Otari and call the provider directly?** What happened? 2. **What did you end up building yourself that Otari should've done for you?** 3. **If the rules hadn't required Otari, would you have continued using Otari?** Why or why not? *If your submission does not include these items, you will not be eligible for prizes.* – If you have any questions, please click this[ link](https://discord.gg/TqvzGH9mwz) to get the `devs-wilding` role and join the Discord! Tag @Marcus and I'll respond as I'm able. Take care!