open source

Rationale You want to keep your project healthy, approachable, and maintain readable CI/CD pipelines. You want to avoid strong dependencies on specific vendors, technologies, or CI runners, ensuring the flexibility to switch providers if needed. Vendor lock-in is problematic, among other reasons, because: Cost model can change Feature sets, and the api surface to access it may change and go in a direction you don’t like Changes in ToS Competitors may get better and should be re-considered, or new options can be evaluated How With a few simple precautions and sustained attention, you can achieve this:...

Monitor links It may seem obvious, but maintaining links working across every kind of web page of your project is crucial for ensuring your visitors and potential users have a good experience when learning. Broken links can lead to frustration and may discourage users, making them leave sooner than expected. Implement scripts to regularly check the status of links helps to promptly identify any that are breaking. Put those scripts in CIs....

About gbdev “gbdev” is the home of the Game Boy development scene. A community of retro-hardware enthusiasts. Maintaning and developing many projects, including RGBDS, the de-facto standard development toolkit, curated collections of resources, documentation efforts, digital preservation and an open archive of homebrews. Follow the Game Boy Development (gbdev) initiative on Twitter, join us on Discord or check our website at gbdev.io. I serve as community leader and directly mantain some of the projects under the gbdev umbrella....