Skip to main content

Visual Studio Online licensing changes

Great news! Brian Harry announced some licensing changes regarding Visual Studio Online:

…As a result of all this feedback we proposed a new “Stakeholder” license for VS Online.  Based on the scenarios we wanted to address, we designed a set of features that matched the needs most customers have.  These include:

    • Full read/write/create on all work items
    • Create, run and save (to “My Queries”) work item queries
    • View project and team home pages
    • Access to the backlog, including add and update (but no ability to reprioritize the work)
    • Ability to receive work item alerts

We then surveyed our “Top Customers” and tuned the list of features (to arrive at what I listed above).  One of the conversations we had with them was about the price/value of this feature set.  We tested 3 different price points - $5/user/month, $2/user/month and free.  Many thought it was worth $5.  Every single one thought it was worth $2.  However, one of the questions we asked was “How many stakeholders would you add to your account at each of these price points?”  The result was 3X more stakeholders if it’s free than if it’s $2.  That told us that any amount of money, even if it is perceived as “worth it”, is too much friction.  Our goal is to enable everyone who has a stake to participate in the development process (and, of course, to run a business in the process).  Ultimately, in balancing the goals of enabling everyone to participate and running a business, we concluded that “free” is the right answer.

As a result, any VS Online  account will be able to have an unlimited number of “Stakeholder” users with access to the functionality listed above, at no charge…

This means that a lot of functionality inside VS Online is available for free without the need for any kind of license!

To make this news even greater, the same licensing changes will also apply to future versions of Team Foundation Server(and maybe even for TFS 2013 Update 4).

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...