Contributing to the Keep Dreaming Project

Thanks for helping out! This will be a general guide on how to contribute to the project, enjoy!

Checkout the overview for more information about the project and the how to join section below, to well join.

How Can I Help?

The project has a pretty big scope so I'm sure you'll find something you can help with! I'll outline what some of those areas are below.

Checkout the roadmap and tasks on Phabricator for more specific ideas.

Planning and collaboration for the project occurs on Discord and Phabricator, that's the best way to contact us. Feel free to bring up any ideas you have for the project!

GitHub is used solely as a repository mirror, issues and contributions should be done using Phabricator. Exceptions will be noted.



I plan on doing all the hardware design work myself, but I'm open to any input or ideas. There are some areas I might need help in:

Dreamcast Variants

Right now I only have a handful of NA and JP VA1 Dreamcasts to examine and test with, I'd like to get my hands on more variants. Randomly buying Dreamcasts on eBay trying to find specific versions doesn't work very well.


There are quite a number of different software projects however many of them are in the planning stages.

When the development boards are done we'll need help in essentially all facets of developing software for them.

Relevant Knowledge

GD-ROM ODE, Network Adapter, Wireless Controller, Logic Analyzer
Sigrok Protocol Decoders

Contributing to any of the opensource projects that the Keep Dreaming Project relies upon is great too, which you can checkout below in the tools section!


Dreamcast Information


Writing up documentation on the various facets of the Keep Dreaming Project itself.


How to actually contribute and use the services or any of the other stuff under the Keep Dreaming Project umbrella.


Creating templates for BookStack and tasks on Phabricator.


Thankfully most of the major stuff is taken care of but there's still a lot to improve.


I've been working on adding permission, registration, and authentication systems to InvenTree to make it usable for our use case. Right now it's pretty hacked together and needs a lot of work.

Relevant Knowledge


Currently adding features and cleaning things up, but it works as intended for the most part

Relevant Knowledge

Webhook Bot

This works but is really poorly implemented, it either needs to be cleaned up or redone.

Relevant Knowledge


I need to migrate QMSV from being a Sublime-Text plugin to a VSCode extension. There is also a relatively new Phabricator extension that I plan on contributing to in order to make using arcanist easier.

Relevant Knowledge


Anything helps!

Contributing to Patreon helps in a couple of ways

Currently the server costs are really low. But as the project grows the tiny VPS I'm paying for won't be enough.

Joining The Project

You can create an account for BookStack and Phabricator, alternatively you can login using a GitHub account.

By default you will only have viewing permissions, you'll have to contact me in order to start contributing. Even though I can restore things I'd still like to avoid griefers.

You can contact me at any of these places (e-mail or Discord work best):

In your message include:

It doesn't need to be lengthy or very good. Once I review it I can give you the appropriate permissions so you can start contributing!

Otherwise everyone is welcome on the Discord server and you can chat with us there.

InvenTree is still under construction and is currently closed to contributions.

Code of Conduct

You can e-mail me at or contact me on Discord if you have any concerns.



All of my hardware designs are licensed under the CERN OHL v1.2 or later.


Licenses will vary per project, typically either the MIT or a GPL variant.


Currently there isn't a good opensource license for HDL, many other projects use the MIT or GPL license although they aren't designed for it. I would like to use the CERN OHL v2 but it is still a draft.

Text, Images, Etc

Anything not covered by the previous licences will use the CC-BY-SA-4.0 license, exceptions will be noted.



Revision #10
Created 2 November 2019 09:27:58 by Zeigren
Updated 15 March 2020 16:45:41 by Zeigren