I found the previous releases (tags) on github say "Z3 is licensed under MSR-LA (Microsoft Research License Agreement)".
My question is whether they are also on MIT license now. Could you kindly please clarify? Thanks!
I don't understand the legal world of licenses, but to be on the safe side I would assume that previous releases carry the old license since that's what's included in distribution packages.
Related
Fiware Cepheus home page says that its branch is archived and 'read only' now.
https://github.com/Orange-OpenSource/fiware-cepheus
So does it mean:
1. There would be no future support and development in this community?
2. As alternative we should use 'Perseo' as its similar in functionality
https://perseo.readthedocs.io/en/latest/
In general, archiving a GitHub project means that "the project is no longer actively maintained.https://help.github.com/en/articles/about-archiving-repositories
The Fiware Cepheus page also states that "no new features will be added, nor issues fixed by the original team." So this means option 1 is the answer to your question.
There exists 21 forks of this project, so perhaps the community is moving over to one of those?
I am not familiar with 'Perseo', so I cannot tell you if option 2 is a good solution or not.
Yes, further information can be found in the FIWARE 7.4 Release Note
As announced at the Porto Global Summit 2018, five generic enablers
were placed under analysis and have subsequently been removed:
Proton, 3D-UI, FiVES, Cepheus, Aeron IoT Broker
Perseo is the now the
preferred generic enabler for complex event processing, replacing
Proton and Cepheus. 3D-UI. FiVES and Aeron are no longer seen to be a
good fit with the FIWARE project.
If you want to use Complex Event Processing you are left with two choices:
Convert your project to use Perseo and continue to enjoy community support and development.
Continue to use an archived CEP processor, fork it and make further bug fixes on your own.
I am looking for documentation for Ace to do "Floating UI" , i want to to like facebook "Chat Heads". So far there is no documentation only mentioning coming soon , which means avaliable but undocumented right?. Is it already available in github latest master?
They decided to close the support for this project:
As of December 2016, this project is no longer maintained by Microsoft. We built ACE to provide developers with an “escape hatch” to access native code from within JavaScript. After nearly a year in production, we learned that most developers are satisfied with the access granted by Cordova’s Plugin Model. Thus, we’ve discontinued active development. We appreciate your interest in the project and hope you found it exemplary of Microsoft’s commitment to experimentation and open source software. if you're interested in continuing this project, please feel free to fork it. As of December 2016, we will no longer monitor or respond to open issues. You can keep up with other projects from Microsoft’s Cordova team by visiting http://taco.visualstudio.com. Thanks for your support!
I was also looking some plugin to implement "chat heads" in Cordova, without any luck :(
I could not find the license on their website.
In what way are we allowed to use the library in our apps?
The license is MIT and it's detailed in the DBAccess.h file. We will add a page to the website as well, it is mentioned on the CocoaPod page as well in case that helps.
Thanks
Adrian
Just a note to say that now the project is Open Source and available at http://sharkorm.com, still under the MIT license. Shark is the open source equivalent of DBAccess.
We are planning to use openWRT "Attitude Adjustment" for out development. We have some software which we need to commercially license ; Is it possible to use opkg to license them commercially ? Is there any document which tells me licensing policies of opkg with respect to commercial code ? Thanks.
yes you can use the Attitude Adjustment buildroot and combine it with OpenWRT packages that have a different licence than the GPL.
The important part is that you have to release a GPL tarball to all the GPL stuff that you are using and evertually you have modified. The proprietary part can be released in binary form, if it is a package that is totally independent from previous sources.
I will make an example. Ubiquiti releases a firmware for its devices that is OpenWRT based. Ubiquiti releases a GPL tarball that contains the source code of everything that was GPL and inherited from OpenWRT. The binary blobs of software developed from scratch by ubiquiti are not released as source code.
it's GPL
so i guess it's a bad news for you.
You can always contact the author/s to see if they want to change their license.
Does the old Toolbar 2000 package (preferably with the TBX extension) compile and work under Delphi XE?
Are anyone using "Tb2k" and TBX these days?
Do TB2K and TBX compile?
Toolbar2000 does. It is used as part of SpTBX (see below.) TBX I'm afraid I don't know - development ceased a few years ago and I upgraded to SpTBX. I would recommend you do the same - it's actively developed / maintained and you probably won't end up asking questions like this about it in a couple of years (hopefully!)
(I know 'upgrade' wasn't what you asked, sorry. It's what I would recommend. I don't like the situation where I'm using third-party code which is no longer maintained, and I have to take that task upon myself and upgrade it each version.)
Is anyone using TBX?
Most people these days do not use TBX - development on it has ceased. Instead, they use SpTBX, developed by Silverpoint Development. It used to be a patch to TBX (so you'd have three layers: TB2K followed by TBX followed by SpTBX) but these days is directly based on TB2K, so it's only two layers.
The installation instructions are easy to follow, and its installer installs TB2K as well.
SpTBX provides extra controls on top of those provided by TB2K, and also provides skin support. It comes with a skin editor if you want to create your own skins. Many of the ones its shipped with I would never use in commercial software, but the Office 2003- and Office 2007-style skins are excellent.
One of the demo SpTBX applications with the Office 2007 Blue skin
Upgrading from TBX: Most TBX components have direct analogues in the SpTBX library, and renaming them in the DFM and form file and opening the form will be a good start. (Or use GExperts.) Some properties and events have changed or gone, which is annoying. I found I could generally figure out how to achieve the same thing pretty easily - it took a day or so to upgrade a large application for me - but you will find it's not a direct smooth transition.
You can download the 2.2.2 sources and modify them by opening the Delphi 2009 package (tb2k_d11.dpk and tb2kdsgn_d11.dpk) files and saving them as a new name, which creates a new copy. Change the NAME SUFFIX from _d11 to _d15, to follow the existing convention, which is useful although a dated technique. For our purposes d15 in this case means a delphi XE package (delphi version 15.0).
Or you can download my copy, which I did this to already (tb2k22_xe.zip). Just open up the project groups, and install the packages. Note that it seems this code is dual licensed, and to "redistribute" such a trivially modified copy of this code, my changes must be licensed under the GPL, and so, to avoid GPL contamination you should email Jordan Russell and ask for permission to relicense these changes/updates under his Toolbar2000 commercial license, if you wish to use them in a closed source commercial license. Or you can repeat the steps I followed, and avoid GPL contamination. Better still, give Jordan Russell $30 and become a paying customer, and prove that the good-old days are not completely gone, when a guy who wrote a nice component for delphi, got people handing him money, left right and center.
I realize this is an old question.
I am still using TB2K in delphi 5 apps. I've also used TBX in combination.
Some people refuse to use newer delphi versions simply because the old delphi products were almost just as good (not quite but still) since they have an infinitely expandable component system.
Doesn't SpTBXLib and TBX violate the Toolbar 2000 licenses considering that it modifies the TB2K without the permission of Jordan Russell? Or did these products get permision from Jordan Russell to release modifications and patches? This all seems to be jumping through a bunch of annoying hoops that a BSD/MIT style license would solve. Even if SpTBXLib and TBX are violating Russell's terms, he's probably okay with it if someone emails him, but I'm not 100 percent certain - it's a bad assumption to make. These projects should clearly say in their README or on their Github site that they have gotten the permission.
Also, I was one of those people who paid Jordan Russell ... to bring back the good old days of delphi developers paying other developers for their work (instead of GPL cult nonsense where programmers go home starving). The trick would be somehow for Russell to offer it BSD while getting paid still, which might prove difficult. It seems the GPL is actually a way for developers to restrict their software, not to free it up.. what a joke.
Free software foundation = Restrictive Software Foundation
One option would be to make it BSD/MIT and ask for donations, but I doubt Jordan Russell would go for it. Might be worth a try. Or if he is only making a few bucks from this every year, then it would be no big deal to just release it BSD. I'm not sure how many copies he sells per year. It's none of our business - but it sort of is in the sense that we are willing to make improvements to his code and not charge money, so we are part of the source too! May the source be with you.
You can check this
I think XE is very similar to D2010
You should check spTBX at http://www.silverpointdevelopment.com
It builds on tb2k without dependancies, installer is there and it works on unicode delphi.