I am trying to get clear the meaning of Department/Division. The following sentence of your license states:

"A department or division is any separate unit of developers, either separated according to business model working on a single location or separated by actual location."

I work at MyDivision, a business division of Real Big Company. The development group I am on at MyDivision works on several products. We also have several offices making several of the product teams geographically seperated.

So, reading the sentence in your license, even though we are in the same logical business unit of Real Big Company would your license consider us seperate divisions because we had multiple offices within MyDivision? I think that is what it says, although I'm not sure I understand it?

Also if that is the case, what if I work for a company that has a virtual office, ie we all work out of our homes. Would we then need multiple licenses?

Thanks in advance for the answers. I know the lawyers would ask me these same questions. We don't need anyone suing us.

Thanks, BOb

pilotboba wrote:

I am trying to get clear the meaning of Department/Division. The following sentence of your license states:

"A department or division is any separate unit of developers, either separated according to business model working on a single location or separated by actual location."

I work at MyDivision, a business division of Real Big Company. The development group I am on at MyDivision works on several products. We also have several offices making several of the product teams geographically seperated.

So, reading the sentence in your license, even though we are in the same logical business unit of Real Big Company would your license consider us seperate divisions because we had multiple offices within MyDivision? I think that is what it says, although I'm not sure I understand it?

You're right. Although YourDivision is just one division, it being seperated locally means every location/office needs to have its own license.

pilotboba wrote:

Also if that is the case, what if I work for a company that has a virtual office, ie we all work out of our homes. Would we then need multiple licenses?

Good question. As the license states now, all workers would indeed need individual licenses, although that isn't really the spirit of our licensing policy. The idea behind the department license was to make LLBLGen Pro payable for smaller companies as well, and virtual offices tend to be like that.
With version 2.0 things will change though. Then individual licenses will apply, which will eliminate these problems. Current customers will be enabled to upgrade at a very big discount by then, so this change won't be hard on them.

Aglaia wrote:

Good question. As the license states now, all workers would indeed need individual licenses, although that isn't really the spirit of our licensing policy. The idea behind the department license was to make LLBLGen Pro payable for smaller companies as well, and virtual offices tend to be like that.

I'd like to know your take on this, since I may soon be in this situation (virtual office) with some consulting work I will be doing.

Also, I think your current licensing actually favors the BIG shops, since they would pay the same for 20 or 30 developers as a small or even 1 man shop. Although even for a single developer the price for you tool seems a very good value.

Aglaia wrote:

With version 2.0 things will change though. Then individual licenses will apply, which will eliminate these problems. Current customers will be enabled to upgrade at a very big discount by then, so this change won't be hard on them.

So, if I read between the lines it sounds like you are changing to a "per developer" license fee? Any specifics you can share at this time? Some times per license fees actually market the larger shops out unless there is some type of scaling discount, the more you buy the less it is per developer.

It sounds like my best bet is to get a license of 1.x for my location so I can partake of that "big discount".

Also, will 1.x customer have access to the 2.0 beta?

Thanks for the info, BOb

pilotboba wrote:

Aglaia wrote:

As the license states now, all workers would indeed need individual licenses, although that isn't really the spirit of our licensing policy. The idea behind the department license was to make LLBLGen Pro payable for smaller companies as well, and virtual offices tend to be like that.

I'd like to know your take on this, since I may soon be in this situation (virtual office) with some consulting work I will be doing.

If you bought a license for a company you work(ed) for and are going to do consulting work on your own, you'd need to have your own license. If the current team or department you work in is going virtual, I'd say the same license you already have would do. Do note though that licenses are only needed for working with the designer, not the generated code.

pilotboba wrote:

Aglaia wrote:

With version 2.0 things will change though. Then individual licenses will apply, which will eliminate these problems. Current customers will be enabled to upgrade at a very big discount by then, so this change won't be hard on them.

So, if I read between the lines it sounds like you are changing to a "per developer" license fee? Any specifics you can share at this time? Some times per license fees actually market the larger shops out unless there is some type of scaling discount, the more you buy the less it is per developer.

Exactly. For version 2.0 you'll have to buy a license for every individual who's going to use LLBLGen Pro (again: the designer, not the generated code). We will offer those scaling discounts you mentioned. Current customers will be enabled to upgrade at about EUR 50,- p.p., which effectively means most people will be better off buying now and upgrading at the discount than buying individual licenses at full cost after the release of version 2.0.

pilotboba wrote:

It sounds like my best bet is to get a license of 1.x for my location so I can partake of that "big discount".

It is

pilotboba wrote:

Also, will 1.x customer have access to the 2.0 beta?

I'm afraid not.