- 📍
- San Francisco, CA
Bot
How people build software.
Need help? Send us a message at https://git.io/c for support.
Joined Jun 2020
Open source is not just about code. Many projects welcome the following types of contributions:
📝 Documentation
🎨 Design
🧪 Testing
🌎 Translation
Brian Douglas shows us how impactful code reviews and issue triage are to Open Sauced:
https://youtu.be/BaIjOw1K5JY
Congrats to @anttihaavikko, the latest Ludum Dare competition winner with The Sandwicher—a fun arcade game you can play in your browser ⚔️ 🥪
What’s *your* highest score?
Play:
Source:
https://anttihaavikko.itch.io/the-sandwicher
https://github.com/anttihaavikko/the-sandwicher
https://twitter.com/i/web/status/1583955246325190656
It's #Hacktoberfest2022! Here's some OSS projects that could use your help with and without code
https://dev.to/blackgirlbytes/contribute-to-open-source-without-knowing-how-to-code-2li9
That's a wrap! 🎬
Photos and session recordings from Git Merge 2022 are now available:
https://github.blog/2022-10-21-git-merge-2022-mission-report/
https://twitter.com/i/web/status/1583604573104586752
When she got her degree, @JoeyPrink’s world opened up and she realized just how colorful and cross-disciplinary computer science really is. Now she’s reimagining the future of virtual spaces.
https://github.com/readme/stories/johanna-pirker
Save the date! 💾
The 10th annual Game Off kicks off on November 1.
It’s the perfect excuse to learn a new language, try out a new game engine, or even build your first game!
https://github.blog/2022-10-21-build-a-game-this-november-with-game-off-2022/
Forks are confusing. What is a fork? How do fork permissions work? What are the security and permission implications? Based on feedback from developers, we've improved how forks work and added more details to our documentation. Check it out!
https://github.blog/2022-10-20-unboxing-fork-improvements-and-unwrapping-fork-docs/
#GitHubUniverse is coming this November and we’ve built a security track that addresses today’s most pressing issues. 🔒 Register now:
https://githubuniverse.com/?utm_medium=org_social&utm_source=twitter&utm_campaign=2022universe_ebt&scid=
Actions changed how developers automate workflows with GitHub. We’re introducing a 🆕 navigation to manage your Actions experience, improving discoverability and accessibility, as well as opening up future feature opportunities.
https://github.blog/2022-10-20-improving-navigation-for-github-actions/
Re Hear from guests @RunChristinaRun @xcorail, and GitHub CEO @ashtom plus @mikethemelanson, Senior Editor for The ReadME Project on topics from OSS project security, developer happiness, building with LEGOs, and more.
What’s the secret to developer happiness? Is Java dead or just hitting its stride? All this and more, now on The ReadME Podcast.
https://github.com/readme/podcast/java-programming-language
RT Thomas Dohmke
Every project has a first commit and 15 years ago on this day, GitHub started that same way. From hosting git repos to the pull request, the contribution graph, Actions, Codespaces, and now Copilot, here’s to celebrating all the initial commits and iterating on them. 🚀
Re @Sas8dp Thanks! Want a fork?
Re @x0rg @martinwoodward We've got the forks covered
How can we write better developer documentation? 📝
Dan Jutan, a product manager at Astro, shared great advice about understanding your readers and their goals.
Watch the full video for more:
https://youtu.be/B1ejSMzr0n4
Game jams drive much of the creation of open source games, but, surprisingly, many games themselves are not actually on open source. What does the future hold for open source game development?
https://github.com/readme/featured/open-source-democratizing-video-games
Re Those were the values we established that helped make Scalar the powerful tool it is today. Read the full story of the path this open source project took to reach its users:
https://github.blog/2022-10-13-the-story-of-scalar/
Re 4️⃣ No surprises here--we value working in the open. Scalar was an open source project from day one, and was never intended to be a project only for internal use. So now we have a history of public code changes to talk about! 5/6
Re 3️⃣ Making any kind of software change adds risk to a project. That risk is mitigated when we have a large set of battle-hardened tests. With a robust test suite available, we were able to make significant changes to our architecture with confidence.
Re 2️⃣ Incremental changes > wholesale rewrites. We focused on small changes that solved an immediate need and optimized for reducing our technical debt and creating a better architecture. 3/6
- 📍
- San Francisco, CA
Bot
How people build software.
Need help? Send us a message at https://git.io/c for support.
Joined Jun 2020
