X0xb0x goes Github

[reinvantveer]

X0xb0x has gone Github, through http://x0xb0x.org! I thought it was high time to get a dedicated domain and an open repository in the general spirit of x0xb0x open development so I went ahead and did it. With some official-ish permission by Adafruit. Why? It's because I thought

• There's ample community that wants to contribute, but it needs a repository to contribute to
• The web site is in dire need of maintainance (dead links etc.)
• The documentation needs lots more expansion on debugging and troubleshooting
• The documentation needs centralising of scattered advice, best practices, etc.

So, at the moment, http://x0xb0x.org is no more than just a scrape of http://www.ladyada.net/make/x0xb0x, but with some dead links removed, and cleaned of some superfluous or non-working stuff. Basically, so far I added nothing, only pruned. But http://x0xb0x.org needs a lot of work. If you want to contribute, here's what you can do:
Contribute content or code

• Create a fork of the repository on https://github.com/x0xb0x/x0xb0x.github.io, add your picture, info or UX contribution
• Test your contribution! x0xb0x.org works through Github pages, which is based on Jekyll (see http://jekyllrb.com/). So do your stuff, install and fire up Jekyll using

  Code: Select all

  jekyll serve

  and test your changes.
• Commit and push your edit to your fork, preferably to the 'develop' branch
• Send a pull request!

There's already a tons of stuff you can contribute to, listed on https://github.com/x0xb0x/x0xb0x.github.io/issues, but it's not hard to come up with more stuff to improve. There's unfinished x0xb0x info, documentation and software all over the place that should be conveniently gathered together for x0xb0x enthousiasts to work with.
So you could:
Contribute Issues

• Go to the issues page for the repository on https://github.com/x0xb0x/x0xb0x.github.io/issues and describe the thing that should be added. There's already a couple of them.

By the way, I have a personal incentive in this endeavour, but it's not economic. I have an assembled, non-working x0xb0x sitting in my drawer, for which I have no idea how to fix it. I hope this project will gather the right troubleshooting info for me to start debugging. It's not the easiest route for getting my x0xb0x fixed, but I hope it's worth the effort for me and for countless other bass synth aficionados! So pitch in if you can! Above all else: http://x0xb0x.org will stay open source and open documentation as it has been from the start.