search

upbound / vscode-up

Visual Studio Code extension for @upbound
Apache License 2.0
14 stars 4 forks source link

How do we want end users to consume this extension? #2

Closed tnthornton closed 2 years ago

tnthornton commented 2 years ago

What problem are you facing?

VSCode extensions typically end up in the VSCode marketplace. Is that where we want this to go?

It seems like there are multiple facets to this:

  1. How do we want customers to consume this?
  2. Is this something that we want behind some sort of paywall?
  3. (more of meta question) Is the extension the thing a customer pays for OR do they pay for services that easily integrate with the extension and extend its functionality?

How could Upbound help solve your problem?

Opening this issue to kick off the discussion for how we'd like to approach this and capture the initial decisions.

tnthornton commented 2 years ago

@grantgumina @hasheddan this doesn't seem like it needs an immediate answer; but I wanted to open up the discussion so that we can start hashing out what we feel like is the approach we'd like to take for now and why.

grantgumina commented 2 years ago

Thanks @tnthornton. I'm planning on creating an issue for the work to launch this plugin, similar to what we're doing with Terrajet (see: https://github.com/upbound/marketing/issues/21).

grantgumina commented 2 years ago

Updated: https://github.com/upbound/marketing/issues/41

tnthornton commented 2 years ago

Thanks @grantgumina. It looks like you've answered the questions posed at the top of the thread. Closing this out.