On the other hand, let's take a team of 50 people working in a large company, and creating a free open source project. At this point this is an individual developer, but who knows what may happen in the future. This is a sort of promotional step that could get compensated later. Nevertheless, we would be glad to help him get acquainted with the methodology of static code analysis, and provide a free license for him. His code is closed, and used for commercial purposes. Let's imagine an individual developer, who writes and sells some game, for example. If you are still interested in knowing the details, then I suggest you continue reading. However, you can skip this section and just move to the "Free PVS-Studio license" section. Unfortunately, this solution does not seem to be the way to go. At first glance, it seemed that the simplest way is to start giving away licenses to those who develop free software. We were thinking for quite a long time about how to help small-size development teams, and how to start issuing academic licenses. However, this does not mean that we should exclude other options of interacting with the world. The world imposes its own laws and for example, the well-known Coverity tool is also aimed at corporate licenses. I think, our failure with CppCat was predetermined. This is why we still see PVS-Studio as a B2B solution. We don't know how we can build a successful business in the sphere of static analysis by selling individual licenses. Unfortunately, our experimental product CppCat had no success. At the same time, we would also like to see individual developers as our clients. The main customers of the PVS-Studio tool are the development departments of various companies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |