Skip to content
This repository has been archived by the owner on Jun 27, 2018. It is now read-only.

NEWS: Moving to GitHub

hach-que edited this page Apr 16, 2012 · 3 revisions

Moving to GitHub

As you may have noticed, the DCPU-16 Toolchain project moved to GitHub. But why? In a word: centralization.

The existing way

The existing system that I had set up involved the use of RhodeCode and Redmine on my own personal server. Those systems are set up for my own personal use; the way that they're set up on my server means they aren't designed to accept contributions from third-parties and they aren't designed for public team development.

So I ended up with a code repository at one URL, a bug tracker at another URL, the wiki at yet another URL, the website at a fourth, main URL and no way to accept third-party contributions easily (basically, they had to be emailed to me).

The new way

The new way means we'll be using the source code, issue tracking and wiki systems on GitHub, as well as the pull requests system so that we can easily accept third-party contributions to the project. Get forking!

Does this mean we have to update links again?

I know just recently I renamed the project to DCPU-16 Toolchain and that everyone had to update bookmarks and links to the project. Unfortunately this does mean you need to do this again; although in this case most of the URLs are going to change to https://github.com/DCPUTeam/DCPUToolchain since the issue tracker and source repository are now on the same site.

The main site will remain as it is currently; that will continue to be the front-facing page of the project. The menu links on that site will be consolidated to link to the GitHub project page.

Clone this wiki locally