The exodus: leading Drupal out of CVS

In those times, the children of Drupal served with rigour under the law of CVS. One week the test bot was down, and a poor, bored, core committer decided to show the way out of this oppression. And there we are. Drupal.org is moving out of CVS, and you can help make this real.

The answer is toward a distributed version control system, GIT. In this panel discussion, led by members of Drupal.org infrastructure team, we will discuss how to make the most of that tool and how we plan to improve the daily life of everyone coding, reviewing and committing on Drupal.org.

Meet GIT, don't be afraid

We will show you that there is nothing to be afraid of. GIT is your friend.

Core development on steroids

Some of the core development workflow will be significantly improved by the adoption of GIT. We will show you how we can all cooperate more easily.

Enhanced cooperation in contrib

Drupal is a friendly and caring community, promoting cooperation and mentoring. We will show you how the move to a distributed version control system will help us do that, while significantly lowering the barrier to entry for new-comers.

Deployment scenario: Project* isn't going away

Although we're leaving CVS behind, all of our project, release management and issue tracking tools on drupal.org are going to continue to be how we get things done. We'll still have our automated test bot, our automated release packaging scripts, and more.