chore: add moving to Coder OSS docs #1078
Conversation
|
✨ Coder.com for PR #1078 deployed! It will be updated on every commit.
|
|
@bpmct should we refer to v2 as Coder OSS? |
|
@ericpaulsen not sure yet |
|
@bpmct I have received feedback that the term v2 is confusing. Until we call it something else and we do not have a licensed product, I strongly suggest stop using v2 and use Coder OSS. |
guides/moving-to-oss.md
Outdated
| description: What you need to know about Coder OSS | ||
| --- | ||
|
|
||
| Coder OSS (also referred to as [Coder OSS](https://github.com/coder/coder)) is |
|
Co-authored-by: Ammar Bandukwala <ammar@ammar.io>
|
I won't stand in the way of merging, but I still think this document contains too much low level detail for us to hope to keep it up to date. People don't need a feature-by-feature accounting, especially for places where we have feature parity or the feature is new in OSS. What are the key features that someone moving from v1 might need to know about to be able to tell whether OSS is worth their time to try out? For all the minor stuff, they can discover the differences in the process of trying things out. |
|
Spike Mark and I discussed this on Discord and would like to start with as much detail as possible |
Resolves #1075. This document intends to be "the state of things today" as opposed to the desired state. As we add functionality, we can change this.