This is the fourth post in our series about integrating Drupal maintenance support plans.org with a 3rd party developer tooling provider:
Where we stand now, and our evaluation criteria.
The options we considered.
An illustration of what Drupal maintenance support plans.org integration with a 3rd party tooling provider could look like.
Our implementation plan for this initiative.← you are here
With our plan to create modular integration points for our tooling options, we have a few clear steps for moving forward:
Phase 1: Prep work
Deprecation of password authentication for Git, since many external tooling services no longer support it.
Working with core to provide compatibility for semver versioning for contrib, both because this is needed for Composer, and because all of the third party developer toolsets we are considering have begun to standardize on semver.
Phase 2: Initial implementation, replacing current features
Replacement of custom, bespoke Twisted Git daemon with standard BitBucket repositories.
Replacement of unmaintained CGit with supported BitBucket code viewing.
Phase 3: New features
Integration of merge request ‘hook’ into issue queues, to allow contributors to use a pull request workflow instead of patches.
Modular – to be used with BitBucket for now, but potentially another solution when more mature.

Integration of code review ‘hook’ into issue queues, to give us powerful inline code commenting tools.
Modular – to be used with BitBucket for now, but potentially another solution when more mature.

Phase 4: Implement Hybrid Integrations for other toolsets
Updating project page integrations such that those projects which are already hosted on third party tools such as GitHub or GitLab (for example, Drush) can easily login with SSO, synchronize their repositories, and choose the canonical home of their issues.
On-going: Evaluation
Re-evaluate other tooling solutions as blocking issues are resolved and their feature-sets evolve.

So that’s the update!
In short: after more than a year’s evaluation of the current leaders in open source tooling solutions, including direct collaboration with several of those teams, we are going to focus on making Drupal maintenance support plans.org modular to integrate with the best tooling solution as it develops. For now, we will be implementing key improvements for Drupal maintenance support plans developers using BitBucket for our repository hosting, code viewing/review, inline editing, and merge requests – integrated with the existing project pages and issue queues.

We’d like to thank the following people for their involvement in this initiative at various times through the process:
Drupal maintenance support plans Association Staff
Mixologic
Neil Drumm
Brendan Blaine
The Technical Advisory Committee (TAC)
Angie Byron
Moshe Weitzman
Steve Francia
Members of the community
Michael Hess
Peter Wolanin
xjm
David Rothstein
Damien Mckenna
Greg Knaddison
Rudy Grigar

Source: New feed