Second article in the Best = Free Drupal IDE series

This article follows last week's article Best = Free: Drupal IDE based on latest Eclipse release (Kepler), in which we established Eclipse as a premier Drupal IDE. This article demonstrates Eclipse (Kepler) as a Drupal Team Project Management tool also.

Our projects consist of deliverables, and our project deliverables live in repositories. Git repositories. For AWebFactory and a good number of developers and organizations, that means GitHub.

If you followed the first article in this series, you already have a powerful Drupal IDE to work on your Drupal based projects, both locally on your laptop or at your workstation, and remotely, directly on your server. In either case, assuming the code is cloned from a repository and incremental improvements and deliverables are pushed there, the version control cammands are often carried out in a terminal (inside of Eclipse, hopefully!) or else with a GUI of some kind, again, working with either local or remote cloned codebases.

Wouldn't it be great if these tasks could be carried out in the same IDE environment where the actual editing of the code takes place. And if that repo is on GitHub, and the IDE could integrate with GitHub issues (and even gists), our IDE would not only be capable of managing the codebase, it would be capable of managing the entire project and team also, via GitHub Issues 2 (https://github.com/blog/831-issues-2-0-the-next-generation).

That's exactly what EGit and the GitHub Mylyn Connector can do. So we need to:

1. Install EGit

2. Install the GitHub Mylyn Connector

3. Start managing Drupal Team Projects and issue tracking right from your Kepler based Drupal IDE

read more