What does it mean that software license is not royalty free? [closed] - asp.net

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I use 3rd party library in my asp.net application. Then application will be deployed on client server. Owner says: a Developer License licenses only ONE developer to create ONE .NET application using their library and Developer License is not royalty free. What does it mean that it's not royalty free?

None of the other answers so far is exactly correct. From a practice standpoint, it can mean all or none of those things, depending on what the producer of the library wants as part of a license.
By saying it's "not royalty free", he's emphasizing in no uncertain terms that it's a rights-managed license, which is essentially the converse of a royalty free license.
Generally, the fees due through a rights managed license scale with the utility gained from the use of it. This contrasts with a royalty free license, which generally grants rights in perpetuity without need for further compensation.
Whether or not you have to pay per deployment will depend on the specific rights that the licensor grants you. All that statement means is that there may be such additional charges. A scaling per-deployment royalty is one of the more common fee schedules used with software rights-managed licenses, but it is by no means the only one.

"Royalty free" means that you don't need to do additional payments to the library maker when you distribute an application that make use of the library. If it is not, it means that you need to pay a fee to the library maker for each copy of your application that you distribute.

It means you cannot distribute the libraries without paying the vendor a license fee for each deployment/ client distribution.
Sometimes this is because the vendor is an OEM partner with another company that licenses software/IP/libraries to them, where they in turn pay a royalty. I found this to be the case with some PDF libraries.

It means that you need to pay for every installation/deployment. A royalty free license means that you pay once for the license and then you are allowed to install the software as many times as you wish.

Related

How Qt Standard Support works?

I beginner question...
I was wondering, how I could get in contact with Qt devs to get support in case I could not find any answer here or on any other site, forum, etc.
While reading here: https://www.qt.io/qt-support/
Standard Support Granted to all Qt license holders*
Looks like support is available only to people who bought their license, and reading here:
https://www.qt.io/pricing
Looks like their 'cheapest' plan is $302/mo.
This price is for companies or there is a different plan for individual developers?
Suppose I buy this plan, I'll be able to mail the support only for a month, or as now I'm a 'license holder' I'll be able to get support even when the plan finishes?
I believe you cannot buy it for a month, it's prepaid for 1 year in advance. I also think you won't be able to get perpetual support as the license itself is not perpetual, it's a subscription.
Moreover, the cheapest "Qt for Application Development"/"Professional" license only lists "Install support" in its features, not "Standard Support".
The minimal "Qt for Application Development" plan which includes "Standard Support" is $341/mo with 1-year prepayment, which results in $4090 at the very least. I'm not sure what extra charges and taxes apply and whether there are any other limits that come with the license due to export restrictions, sanctions, license agreements or whatnot.

How to deal with Wordpress updates and client sites? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
We're making a lot of websites for multiple clients and we always had some problems figuring out what to do with "Updates". We're starting building Wordpress sites and there's almost a plugin update every week. Since our sites use WPML and Woocommerce, there's a lot of conflicts happening with unreliable WPML updates and other plugin with security flaws (revolution slider in my case).
I've just received an email from my client's hosting and he wants us to make updates from WP 3.8.1 to 4.0 but I know there's an intensive conflict job coming up. I usually use the 'Disable all wordpress updates' plugin to hide 'em all from the wp-admin.
I wish my project had enough budget to build custom sites, but that's not the case here.
I just want to know how Wordpress agency are with that. It doesn't look that professional to tell a client that updates aren't necessary.
First of all, you of course bill them for the time you spend on your clients websites. Better yet, sign some kind of support support agreement where they pay you a monthly fee for having their websites kept up to date and maybe uptime monitoring. You can also include a few hours per customer for support and small development tasks per every month(it's usually nice for the clients to have even if they don't use it every month). This is a nice way to get some steady income and fill the time gaps when you have less to do.
You should also state in the agreement when you build the website that future updates and fixes is NOT included in price. You can give the clients a short period the report errors and bugs in the website and after that you will bill them for any extra time.
Secondly, get the right tools to optimize your time. I recommend ManageWP or InfiniteWP. ManageWP is slight better in my opinion and it is a hosted solution, but has a higher price if you have many clients(per client pricing model). InfiniteWP is a free self hosted solution(you set it up on your own server), where you only have to pay for the modules you use. You will need a few modules to get the functionality you need, but it's still much cheaper than ManageWP if you have many clients.
For uptime monitoring I recommend Uptime robot(simple and free for up to 30 websites) or Pingdom a better service with a lot of nice tools, for example performance monitoring, but also a much steeper price.

Do I have to pay for Qt license to develop a commercial application for Symbian OS? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I have the intention to develop a commercial, closed-source application for mobile phones.
I've choosen to start with Symbian OS, as I've got a Symbian phone as
well, and I really like it.
I would like to adopt Qt, because it's actually the way suggested by
Nokia, and because I know I could port my app quite easily to ios and
other platforms by using the Qt libraries.
So, having to make the choose between Qt and C/C++/Carbide
I have one compelling question:
do I have to pay to obtain a license for using the Qt to develop a
commercial closed-source program?
Truly, I won't to pay for using a development tool, as I'm not sure I
could return on my investment. Besides, I have also to pay to open an
account for hosting my app on the stores.
Please feel free to correct my English if it sounds bad. Thnx.
No, you don't have to pay for the Qt framework to build commercial or proprietary applications. GNU LGPL version 2.1 allows this, and Qt is licensed under this licence.
Read about the Qt licensing here.
Extract:
This version of Qt is appropriate for the development of Qt applications (proprietary or open source) provided you can comply with the terms and conditions contained in the GNU LGPL version 2.1.
Note that LGPL still has some requirements. For example, if you improve the Qt sources to provide your application a better performance or to fix a bug, you have to make the source code of your modifications available to anybody you give (sell; distribute) your application to. As this is not a bad idea per se, one may want to keep such changes private and use it as a competitive advantage.
See also FAQ on Qt licensing (thanks to Claudio for the comments).

Registration or Licensing for an Adobe Air software [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am making a Adobe Air software which needs to work on Windows, Mac and Linux. One of the issues that has confused me is the registration/licensing process.
Basically, I want users to try out the full version of software for a month and then buy if they find it useful. What I am not able to figure out is how the licensing would work on all these platforms.
There are no registries in Mac and Linux where I can store the trial information.
If I somehow maintain things locally in a db, post trial, if the user simply uninstalls and re-installs the software, the trial would start again for 30 days.
Don't want to store things in filesystem as that's not even close to actual authentication.
Doing an online activation of the software is a little resource consuming and has network dependency, so that option is also out of scope.
What way should I choose? what other options do I have? Does adobe provide any support for this... any 3rd party libraries that I can use for free?
I use LimeLM (https://wyday.com/limelm) to do licensing for my Adobe Air app (Windows and Mac, no linux). Like you I have a 30 day trial, LimeLM has a trial feature which is tied to the hardware, so uninstalling/reinstalling won't give users another free trial.
LimeLM requires network activation BUT you can allow for grace periods, so someone must connect to the network, say, once in 30 days of use to activate.
I agree with the above post that EncryptedLocalStore is a good idea as well.
Unfortunately the licensing options for Adobe AIR is limited. LimeLM is functional and cheap (they don't take a cut of purchase price). I looked at NitroLM, which is very expensive (I think they take 30% of purchase price) and very complicated - I could never make sense of it. Zaqon also is out there. I didn't like the way their licensing interface looked to our users. LimeLM was the most flexible.
Have you tried EncryptedLocalStore? Data stored in ELS remains even after app uninstallation.

Resourcing XQuery in the market place [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have a client whose requirement is best met with an XQuery/XML solution. The problem I am facing is overcoming the risk associated with a lack of market place skills for these technologies.
This is maybe a sales question, but how have others overcome this objection?
I'll let someone else answer from a sales perspective or suggest technologies. Here's my project management perspective. I think you should do two things:
1.) Cost of ownership assessment
Draw out two or three architectures and try to amortize in hours, $$$, or some other quasi-imaginary metric the immediate and ongoing impact to the client. For each solution, how hard will it be to build? How many different engineers will you need? How many different skilled people will you need to keep familiar with the project to maintain it, etc. Does the benefit of not having to have separate middle tier and dedicated relational database people outweigh the market availability of XQuery people? You have identified that the problem is best met by XQuery/XML. Can you quantify this somehow to your client?
2.) Risk mitigation brainstorming
The idea here is to come up with a plan to reduce the possible impact to the client for the technology that you choose:
Start with a Proof of Technology project to gauge the difficulty and efficiency benefits for your staff / client to implement an XQuery solution
Develop an in-house expert / team:
XQuery Training is available
Share cost of supporting XQuery expertise with other projects and similar problem spaces at your organization / client
Expose the XQuery/XML portion of the solution through other means that don't require special skills
XML and/or JSON over REST
Some sort of data access object layer that doesn't remove the agile benefits of the XQuery technology
SOAP services (yuck)
Build a relationship with a service provider who knows their XQuery well
From more of a sales perspective it is important to realize that there is actually lots of XML expertise in the market. XQuery expertise, while perhaps more widely available than you might think, is more limited.
I would look to find an XQuery/XML technology that meets a couple of important criteria:
Numerous successful customers who are willing to act as references. Pointing to successful implementations in production and, even better, allowing your customer to talk with some of these implementors, can be very powerful in reducing the perception of risk.
Provides development tools that allow for rapid development and reduce the amount of initial XQuery knowledge provided. For example, look at this open source framework where you can access nearly all of the underlying XQuery functionality via REST services or even via language specific APIs built on top of REST: https://github.com/marklogic/Corona
Have a robust training program that is accessible and reasonably priced. The cost of training is often low and the risk reduction is high.
Have an active community of developers and open source projects. This will allow you to leverage a lot of existing work done by the community as well as general development knowledge resident in the community, further reducing risk.

Resources