Archive for December, 2009

Tasktop and VersionOne team up on Eclipse Mylyn integration for Agile teams

Wednesday, December 16th, 2009

Today marks the start of a major extension of Eclipse and Mylyn’s reach into Agile project management. We’re very pleased to announce a partnership with VersionOne to develop an Eclipse Mylyn connector for VersionOne’s Agile planning and project management platform. The Tasktop Certified VersionOne Connector will be included in Tasktop Pro and available as a plugin for any Eclipse-based IDE or as a standalone desktop application for product owners.

VersionOne Connector

One of the features we will be leveraging in VersionOne is their open and extensible platform approach to project management. VersionOne’s Team and Enterprise products provide comprehensive core of agile project planning and management tools. These tools are extended with a REST web service API as well as open source SDKs for both Java and .NET to facilitate integration with the rest of an organization’s unique tool stack. This open approach has led to an impressive ecosystem of integrations with defect trackers, version control system, build systems and more.

With the upcoming Mylyn and Tasktop Pro integration, VersionOne’s interoperability will take another giant leap forward in two key ways. First, VersionOne is joining the ecosystem of 42 interoperable Mylyn connectors. This will allow development teams in complex environments to seamlessly access VersionOne alongside artifacts from other supported systems as well as move and link artifacts across systems, all from within the IDE. Second, integration with Tasktop Pro will enable VersionOne artifacts to be linked with web pages, local documents, and applications such as Microsoft Outlook.

Of course, the Connector will also allow VersionOne teams to take full advantage of Mylyn’s task-focused productivity technology to focus the interface on only the code, documents and web pages that are relevant for a given VersionOne story, defect or task.

Feature Highlights

  greenbullet_icon Access VersionOne from any Eclipse-based IDE
  greenbullet_icon Standalone desktop application with offline access to VersionOne artifacts
  greenbullet_icon Link VersionOne stories with artifacts in other Tasktop Certified repositories
  greenbullet_icon Automatic time tracking and reporting
  greenbullet_icon Task-focused interface productivity technology
  greenbullet_icon Easy installation from the Mylyn Connector Discovery listing in the Eclipse IDE

We’ve received fifty requests for VersionOne integration and look forward to releasing the connector in March, 2010. Sign up on the VersionOne Connector page to be notified of future announcements.

Be more productive. Guaranteed.

Mingle and Murmur with Tasktop Pro and ThoughtWorks Studios

Wednesday, December 9th, 2009

Today’s Tasktop Pro 1.6.1 release includes a new Mylyn connector for the Mingle 3.0 project management software from ThoughtWorks Studios, the products division of the global Agile consultancy, ThoughtWorks. The connector takes Mingle’s emphasis on team collaboration to a new level by making it effortless for team members to access and communicate around Mingle cards without leaving the IDE.

Murmurs

What makes our collaboration with ThoughtWorks so exciting is that it has yielded the first social network extension to the task-focused interface. Starting on a cool task? Just murmur it much as you would send a tweet. The integration with the task editor is seamless. Stuck on something? Attach your task context, murmur for help, and colleagues on the project will have instant access to the code you’re squinting at.

videos1
Watch the Mingle Connector Video
 

What’s a murmur?

Mingle’s Murmurs™ support casual conversations much like Twitter or IM chats. But instead of being lost in Twitter or IM, the communication is captured on artifacts in Mingle for easy reference. With the Mingle Connector, Murmurs can be sent directly from the IDE and it’s easy to view all murmurs relevant to a particular development task or card.

murmurs

 
Focus on your cards

The Mingle Mylyn Connector fully supports task-focused programming productivity. Mingle cards in the task list can be activated to automatically track and show only the most relevant source code, web pages and documents for a given card. For example, when working on a million line code base, the task-focused interface might show only the 2 files and 12 lines of code that are relevant for the bug fix in progress. When returning to the same bug after an interruption, or after lunch, a single click instantly restores the workspace to its previous state, including open editors. This means far less time is spent repeatedly searching and scrolling to find the relevant code and other information. For more on task-focused programming, watch the Tasktop for Carbide screencast which demonstrates the concepts using the Eclipse-based Carbide IDE.

 
Automate time tracking

Because Tasktop users activate their tasks or cards to benefit from the task-focused interface, the time spent on each card is already available. Each Mingle card includes a time tracking section that provides a summary of how much time was spent during a given period. Time spent can be adjusted as needed to account for meetings, design time at the whiteboard etc. before uploading the data directly to Mingle.

time-tracking1

 
What about Twist and Cruise?

Mingle is a part of ThoughtWorks Studios’ Adaptive ALM product suite that includes Twist test automation and Cruise release management products. Further Tasktop Pro integration with Twist and Cruise will be available in March 2010. Sign up to be notified about further integration on the ThoughtWorks Studios Connector page.

 
Try it

The Mingle Mylyn Connector is now included in Tasktop Pro. Download a free trial

If using an IDE based on Eclipse 3.5 or later with Mylyn installed, Tasktop Pro can also be installed via the Connector Discovery wizard by clicking “New Task” in the Task List toolbar and then clicking the “More Connectors…” button.

Need Mingle? Download a free Mingle trial

Be more productive. Guaranteed.

Eclipse ecosystem: Open discourse at the risk of open conflict

Thursday, December 3rd, 2009

Open discourse brings conflicts out from behind closed doors. A while back I was involved with an open source conflict that degraded technical discussions to power struggles. I looked to Bjorn Freeman-Benson and Mike Milinkovich the help resolve that conflict. This week, countless eyes were peeled on Planet Eclipse as a very public conflict arose between the two of them.

Open source passions often transcend organizational and professional boundaries. That’s what makes someone bored with their day job contribute to Eclipse on evenings and weekends. It’s what makes someone like Bjorn continue to be invested in the success of Eclipse long after he has moved on from his job as the Director of the Committer Community.

mike-mik-bjorn
Mike, Mik and Bjorn at EclipseCon 2008

Open conflict helps avoid the slow death by a thousand cuts that can result when fundamental or structural problems are hidden from a community. This is one reason why open discourse is as important to a healthy ecosystem as an open development practices. It is up to us to process the information underlying the conflict, learn from it, and move on.

My perspective comes from joining the Eclipse community eight years ago, as one of the first non-IBM committers, and watching it grow. Mike’s great leadership as Executive Director has created the successful Eclipse ecosystem and membership that we have today. Mike has been instrumental in laying down both the technical roadmap and community design that makes Eclipse so successful. Bjorn’s five years of contributions have been remarkable as well. He drove the most fundamental changes to the Eclipse development process with a consistent theme of improving the mechanisms that support committer collaboration, release coordination and innovation. Bjorn has that very rare ability to understand the overlap between people and technology, and employ social engineering in order to define the rules of engagement that make a community successful. The technological implementation of social rules is just as important to open source ecosystems as it is to social networks like Facebook and LinkedIn.

Having collaborated with both Bjorn and Mike throughout most of this decade has given me an appreciation of how different their perspectives are. Bjorn’s academic stance will have him happily debate you to death, and can result in some provocative statements. Mike is a business leader, and if those statements cease being constructive, he will call “jerk” on you in order to protect the foundation and ecosystem.

Evolving open source ecosystems requires the voices of both Mikes and Bjorns. One creates business direction and drives change within the ecosystem as a whole, the other focuses on community structure and dynamics. While recent posts went into enough of a downward spiral as to stop being constructive, we should not discount that Bjorn’s critiques of the Eclipse ecosystem struck a nerve, and have stimulated some of the most significant discourse we have seen around Eclipse since the code went live eight years ago. Assuming that the discourse can return to its constructive form, it is in our interest to have it continue as part of Planet Eclipse.