This is very encouraging news! While I don't want to rush the discussion by any means, it would be really neat to have this announcement at the upcoming AtlasCamp since it's heavily attended by developers, and I'm sure it would be welcomed with thunderous applause. :-)
As you can imagine, getting pricing right can be a complicated process. We will have to determine whether we can change the price in a way without sacrificing revenue on our server license sales. One thing I know for sure is that we won't be able to get a new pricing out before Atlascamp. But we will be looking into it.
Thanks again for the suggestion.
Could you tell how do you see this "starter license" might look like (price / number of users / scope of functionality)? Please note that we already have the "Developer License" which costs 1/4 of Server license and has nearly all features (except exporting reports in HTML/XML/PDF).
Thanks so much for being willing to open up the discussion -- I really appreciate it. I have just downloaded the Clover desktop product trial version and have experimented with it a bit to see what kind of functionality is available (I'm really impressed, btw!).
Price: It would be good to see a price that is easily affordable when his/her boss says "No, we won't get that for you", but they'd be willing to pull out their own wallet to purchase it because as a developer, they see value in test coverage metrics. An annual cost of somewhere between $10 and $25 would probably be seen as reasonable for a personal purchase as a starter license cost. $300 initially and then $150 annually is a bit of a stretch for someone to spend money out of their own paycheck, however. I'd add the stipulation that this would have to be a personal, 1 user license, not a license that is owned / managed by a corporation.
Number of users: 1 user per license
Features: I would remove the ability to generate/export HTML/XML/PDF reports and run it with Ant/Maven builds since this would be targeted for users who are only working within an IDE. If their boss wants reports, the boss should have to pay for the full Desktop license. It may be worth considering removing the ability to run coverage on Groovy code since only some developers do Groovy coding. If the Coverage Database keeps track of coverage over time, it could also be excluded since developers will likely be most interested in what the coverage of their codebase is at present. Sure, it would be nice to see how things are getting better, but it's hard to say it would deliver a significant value for a single desktop user (if this is indeed what the Coverage Database does).
Not sure if you'd want to offer source code with this license -- I know that the source code is available for the other Atlassian starter licensed products.
Again, thank you so much for being willing to open up the discussion.
To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?” That question applies to both implementation and improvements on the Scrum framew...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs