[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#147303: ITP: winex -- A DESCRIPTION

* Ove Kaaven <ovek@arcticnet.no> [020603 11:51]:
> There was a change in the license preamble in the WineX CVS about a week
> ago. Does it suffice?

ooo. spirit vs actual sledgehammers.  Of course, it isn't on the HEAD
for some reason on viewcvs.



Note that while this license does permit certain kinds of non-commercial 
distribution of pre-compiled binary packages of WineX, doing so on a
scale is discouraged, as it affects TransGaming's ability to continue
to improve and develop the code.  TransGaming reserves the right to 
change the license under which future code is made available, and will 
not hesitate to do so if non-commercial distribution of pre-compiled 
binary packages adversely affects the financing of continued


I read this as a plea from transgaiming because they feel they can't
properly educate their userbase from not paying them to recieve a binary
package.  Of course, who knows how many people 'warez' their packages.

Perhaps a license key is next?  I would definately track their CVS and
keep watching until they totally eliminate the rights from their
license.  Personally, If I benefited greately from the product I could
see people putting money into a tipjar for more say on what happens to
the development.

If some people just dont care about future features because it
Works For Them(tm) perhaps the economics wont work out for this specific

Of course, if the future features are coming out at a good rate and
stuff just works, then theres a definate issue in this model based on
how many 'supporters' you can retain.  I bet there is some sort of
equliribium and if it goes low, just freak out about money like other
opensource companies have and get a boatload more subscribers.

Scott Dier <dieman@ringworld.org> http://www.ringworld.org/

To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: