Category Direction - Editor Extension

1. 表示中のページ:
2. GitLab Direction
3. Product Vision - Create
4. Category Direction - Editor Extension

• Editor Extension
  • Introduction and how you can help
  • 概要
  • Target Audience and Experience
    • Challenges to address
  • Where we are headed
  • Maturity
  • Problems to Solve
  • What's Next & Why
  • What is Not Planned Right Now
  • Competitive Landscape
    • Local Editors
    • Local Runtime
    • Remote Runtime

Editor Extension

Introduction and how you can help

Thanks for visiting this direction page on Editor Extension. This page belongs to the Editor group of the Create stage and is maintained by Kai Armstrong (E-Mail).

This direction is constantly evolving and everyone can contribute:

• Please comment and contribute in the linked issues and epics on this page. Sharing your feedback directly on GitLab.com or submitting a Merge Request to this page are the best ways to contribute to our strategy.
• Please share feedback directly via email, Twitter, or on a video call. If you're a GitLab user and have direct knowledge of your need for Local Development Tools, we'd especially love to hear from you.

概要

GitLab supports teams collaborating and building software together, however that collaboration is only available inside GitLab application.

Developers, on the other hand, spend the majority of their time working in local editors implementing work outlined in issues, responding to merge request feedback and testing/debugging their applications. These tasks are the core of the developer experience, but GitLab is missing from this experience in any integrated way.

Target Audience and Experience

Challenges to address

Where we are headed

GitLab should support developers closer to where they're doing their meaningful work and enable them to be more efficient in the delivery of that work.

Maturity

Problems to Solve

There are many specific problems that can be solved by focusing on local developer tooling:

1. Developers working in local editors
2. Developers working locally with local runtime
3. Developers working locally with remote runtime

What's Next & Why

Next: Remote Development Environments &3230

Developing a strategy and MVC for enabling developers to test and debug their applications utilizing remote compute will be key in expanding in this path.

What is Not Planned Right Now

We're not currently focused on extensions for any other local editors or IDEs. We recognize there are a variety of these environments and we'll continue to monitor demand and market trends to look for other opportunities to support developers.

The editor group is also not looking to connect our existing Web IDE to any runtime environments or local tools for further development. We may continue to explore a more advanced Web IDE that could support these itmes in the future.

Competitive Landscape

Local Editors

• GitHub Pull Requests and Issues

Local Runtime

• Skaffold

Remote Runtime

• Okteto
• Tilt
• Dev Pods