We are using Mosek Floating License offering across our organization.
Sometimes situations occur wherein a team member is unavailable, but has occupied the Mosek licenses, making it unavailable for others (even if urgently required).
To help in those situations, does Mosek's have any utility to forcefully release that occupied license?
e.g.
If utility for License view: lmutil lmstat -c 27007#127.0.0.1 -a., then what will be the utility for License release?
You can consult
https://docs.mosek.com/generic/fnp_LicAdmin.pdf
for question about the license system.
You should do
lmutil lmremove something
(It is in Chapter 12.)
Related
We have an open source tool that we want to deliver to users with a specific JRE version. As Oracle is so unclear and closed with licensing (even with newest jlink possibilities), and unofficial openjdk builds are so hard to "follow", we think that Zulu can be the right alternative here. Thus the only worry I have:
Can I freely redistribute this JVM in my distributions? It's nothing more than having a /jre directory in my distribution and making start-up scrips going for provided JVM instead of the system default.
The Zulu Terms of Use are not 100% clear here:
You also represent and warrant that you do not intend to distribute the software in a manner that is not compliant with relevant export control laws or regulations administered by the U.S. Commerce Department, OFAC, or any other government agency.
This question comes up regularly with software developers wanting to redistribute Zulu with their applications. The specific item in the Terms of Use you highlighted calls out specific export controls to remind you of the implications that every Java SE distribution from any vendor including Azul has some cryptography features inside in. Because of that fact, you should be aware of US export laws, and that many countries have import restrictions, too. Zulu does not have any field of use restrictions, though we needed to assert the statement about export in the ToU.
We typically share the details of what it means to redistribute Zulu through our Zulu Embedded offering. I make several points why it is at least worth a call to Azul to discuss alternatives in my forum post here:
http://zulu.org/forum/thread/bundle-zulu-community-jre-with-our-product/
If you are doing anything other than open source software, there are potential pitfalls redistributing community binaries. Azul can help clarify your risks.
Matt
Disclaimer: I am the Zulu product manager at Azul, though this response reflects my personal opinions.
The answer is probably. This is one of those areas where nothing and no one can substitute for actual legal advice. At a guess, you may need no more than an hour or two from a lawyer specializing in software copyright issues. The lawyer's office itself can (will) provide an estimate.
Please take note that I'm not a lawyer.
Hotspot and most of the JVM code (mostly C/C++ native code) in the OpenJDK is released under the GPL 2.0 with Assembly Exception and not a "bare" GPL. This is in addition to the Classpath exception to the GPL that applies mostly to the runtime library code.
I would assume any OpenJDK is safe to redistribute with your application. Please do correct me if I'm wrong.
What are the differences between the different Rebol 3 branches, especially with the new REN branch?
Is it the platforms they'll run on, the feature set, code organization, the C standard compliance?
This is an answer destined to become outdated, hence set to Community Wiki. This information is as of Sep-2015. So if updating this answer after some time has passed, please modify the date as well.
Binary download of Rebol3 from rebol.com
Last build was 5-Mar-2011 and pre-dates the open source release.
No GUI support, no HTTPS support, no serial port support, no UDP support, no smart console...
No 64-bit builds. Binaries are for Windows x86, OS/X (PPC or x86), Linux (x86 or PPC), FreeBSD x86.
While Rebol2 binaries are archived for many "esoteric" systems (BeOS, AIX, Windows DEC Alpha, QNX, Solaris...) similar binaries were not provided for Rebol3. The only "weird" build is for Amiga, and only an OS4 PowerPC Amiga. No successful builds of Rebol3 for Amiga emulators have been reported.
Open source release of Rebol3 on Github rebol/rebol
Open-sourcing was on 12-Dec-2012.
The rebol.com binary downloads were not rebuilt as part of this release. However, a community member (#earl here on SO) created a build farm at rebolsource.net that follows this GitHub master whenever it updates. Given that GitHub's rebol/rebol master hasn't been updated since March 2014, this dynamism is currently underused.
Building the source at time of release got an executable not distinguishable (?) in functionality from the builds on 5-Mar-2011. This suggests few changes to the source were made besides some cleanup and Apache-licensing edits to prepare for publication.
Minor patches and bugfixes were integrated sporadically, with most PRs sitting idle. Last PR accepted at time of writing was Mar 3, 2014, which is over a year ago.
The most noticeable "breaking" PR that did get approved was to repurpose the FUNCTION name. It was considered to be worth breaking the old arity 3 form to let the word be taken for the much more useful implementation as locals-gathering FUNCT. (This also brought Rebol in alignment with Red, whose FUNCTION is arity 2 and acts similarly.) FUNCT was kept around as-is for legacy code.
The most major non-breaking PR that was taken is probably not requiring blocks around IF, UNLESS, or EITHER bodies. This has been received well among those who know it's there, as fitting the freeform and non-boilerplate philosophy of the language. It allows some code constructs to get "prettier" and gives programmers more choice, while it doesn't seem to cause any more problems than anything else. It's certainly less of a speedbump than if [condition] [...], in fact it seems almost no one knows this feature got added, so it must not be biting anyone. (If anyone can bend ears over at Red to make sure it gets IF and IF/ONLY then that would be ideal.)
RETURN/REDO was removed. Rationale was that it permitted functions to effectively behave with variable arity, and that this was unnecessary and took terra firma away by no longer being able to predict a function's arity from its spec. Perhaps this stance warrants a second look...as Lisp users who are pressuring for the addition of Lisp-style macros seeming aren't worried about that very much. (Here in the StackExchange universe, this provoked a Programmers.SE question Would Rebol (or Red) benefit from Lisp-style Macros?, which hasn't gotten much in the way of answers yet.)
The fork by Saphirion: "Saphir"
Prior to the open-sourcing of Rebol, Saphirion AG had a special relationship with Rebol technologies. They had access to the source and were taking responsibility for most of the development work for Rebol3 GUI features. They also added several other things like HTTPS.
Saphir is available as a binary download from their website, but only provided for 32-bit Windows. There was at one time an experimental .APK for Android from Saphirion.
Some (but not all) of Saphir's source was released after the open-sourcing. Notable omissions were the android build and some Rebol3 code for encapping...a way of injecting compressed scripts and resources into binaries of the interpreter without needing to recompile it.
(Note: Under Apache2 license there is no requirement to release source code for one's derived work.)
"Community" Integration at Rebolsource on GitHub
With the GitHub rebol/rebol being held up on integrations, a fork at rebolsource/r3 was established to be a "community build" where work could be staged.
Rebolsource changes were conservative, seemingly aimed toward showing process for how GitHub's rebol/rebol might adopt changes "in the spirit in which Rebol was conceived" should that repository be delegated to the community. (For that spirit, see this.) Hence it integrated non-controversial bugfixes and tweaks, instead of large third-party cryptography libraries for implementing HTTPS. Also: no allowance for adding build dependencies besides a C compiler (no GNU autotools, for instance).
Binaries for the community build were produced on an as-needed basis for those requesting them who could not build it themselves.
Atronix Engineering's Rebol "3.0" at Github zsx/r3
Atronix is an industrial automation solutions provider that uses Rebol. How they do so is described in a video here by David den Haring, director of Engineering, and their ZOE software is built on their version of Rebol.
After the open sourcing, Atronix partnered with Saphirion to port the GUI to Linux. Atronix publishes their source publicly as it is developed, and David den Haring notes in the video above that they have only one proprietary component they developed (an industrial control driver). Other than that they are happy to share the source for all Rebol development they do.
Atronix integrated the 64-bit patches from Rebolsource, created a Windows 64-bit target, and offer up-to-date binaries of their development branch for Windows and Linux x86/x64, as well as Linux ARMv7.
Besides having the features of Saphir, the Atronix build added support for CALL with /INPUT, /OUTPUT, /ERROR. It also added a Foreign Function Interface, implementing LIBRARY!, ROUTINE! and STRUCT! for communicating with non-Rebol dynamic libraries. It brings in encapping support as well on Windows and Linux.
Rebol's "religion" was at times at odds with expedience, so the Rebol-based build process was replaced when needed by hand-edited makefiles and Visual Studio projects. The FFI library introduced a dependency on GNU autotools to build.
All Atronix builds include the GUI, so there is no "Core" build. And again, only Linux and Windows.
Ren-C
(Bias Note: This fork is the initiative #HostileFork started, knows the most about, and will speak most enthusiastically about.)
Ren-C started as an an extraction of a Core build out of Atronix's codebase. That gave it features like HTTPS, the enhanced CALL, and Foreign Function Interface to essentially all the platforms that Rebolsource was able to build for. Updates Jul/Sep-2015 Ren/C supports line continuations in the console, user infix functions, several bugfixes...
Ren-C makes large-scale changes and fixes fundamental issues in R3-Alpha, which are tracked on a Trello that provides more information. There is a new FAQ as a GitHub wiki. Critical issues like definitionally-scoped returns have been solved, with continuous work on other outstanding problems.
Though Atronix's R3/View required some additional dependencies, Ren/C pushed back to being able to be built with nothing besides a C compiler, and eliminated all handmade makefiles/projects.
Beyond Windows, Linux and Mac in both 32-bit and 64-bit variants, Ren/C has also been built for smaller players like HaikuOS and yes, even Syllable. This is interesting more for the demonstration of how broadly turnkey builds of the C89 code work (simply as make -f makefile.boot) as opposed to there being a particularly large userbase of those particular OSes!
From the point of view of language rigor, Ren/C is pushing on modern techniques. Although it can still build as C89, it can be built as C99 and C11 as well. It has also been verified to build as C++98 through C++14, and with some strategic modifications under #ifdef __cplusplus it can take advantage of modern C++ as a kind of static analysis tool over the C code. Warnings are raised, type errors all fixed up, and it's "const correct". The necessary changes were carefully considered to make Rebol's baseline C code not just more correct but cleaner and clearer source across the board.
From a point of view of C developers, Ren/C should be stable, organized, and commented enough for anyone who knows C to "modify with confidence" and try new features. That means being able to implement definitionally scoped returns (actually written, but not pushed), or try developing features like NewPath.
From a point of view of architecture, Ren/C is intended to not have an executable at all...but to be a library for embedding a Rebol interpreter into other programs. It is now the basis for Ren/C++, which was designed to anticipate working with Red as well.
From a point of view of testing, Ren/C intends to whip everything into shape for engineering rigor and zero bug tolerance. This means avoiding practices like zero-filling memory to obscure uninitialized memory accesses, using Address Sanitizer, Valgrind, and a test suite that can pass the highest settings on both.
While enabling all the extra functionality has made Ren/C's executable nearly twice the size of Rebolsource's, there's not yet been any audit to see how this can be brought down. It has been confirmed that there are duplicate copies of Zlib and PNG encoding/decoding--for instance (Saphirion included LodePNG, likely to work around a bug in the existing PNG because it was easier than fixing it...yet did not mothball the previous code). Also, being able to do a build which selectively integrates only the codecs you want to use is on the agenda.
Ren/C currently has the stakeholders from Atronix and Rebolsource participating in its development and direction, which strengthens the likelihood that it may evolve into "the" Rebol Core. It is now being linked in as the code backing Ren Garden, and using a similar approach it may be set up as the library used by Atronix's R3/View...then Rebolsource...and perhaps ultimately rebol/rebol itself.
The fork by Oldes
(Bias Note: this edit is added 28-Feb-2019 by Oldes himself)
Forked from the community branch. Main focus on keeping the code close to the original Carl's release without blindly taking everything from Atronix/Saphirion but still trying to pick-up the good things from these branches slowly.
Not like Ren-C, this version is not trying to introduce new syntax, but rather be closer to the original Rebol2 and new Red language
I'm a student and I can register Intellij Student Program for registry student license from Intellij. As in license comparison here. I see that:
Student license just for Non-commercial only, including education and
academic research
So if I use Intellij IDEA and write android app and publish to playstore and get earning by advertisement or by in-app billing, Do I violate license ? Or I use Intellij IDEA app and write a web application and get earning by advertisement, Do I violate license ?
I also registered Microsoft Dreak Pack program. I don't have any source about this program license, so can I use those application for commercial purpose ?
Thanks :)
IntelliJ
Academic licenses are only available to students and teaching staff of educational institutions. Use of a fully-functional version of IntelliJ IDEA under an academic license is restricted to educational purposes. For more information, see the Academic License Agreement.
DreamSpark
No commercial use. Except as provided below, you may not use the DreamSpark Direct Subscription software for commercial purposes or commercial software application development, publication or distribution unless you first purchase the appropriate commercial license(s) for the software.
Commercial Definition
According to 18 USCS ยง 31, term "used for commercial purposes" means the carriage of persons or property for any fare, fee, rate, charge or other consideration, or directly or indirectly in connection with any business, or other undertaking intended for profit.
IANAL, but you can't use IntelliJ Academic License and DreamSpark Licence (there are some exceptions in the link) to build apps, if you're planning to make money with it. Adverts = money.
I'd like to embed Mono into an .exe file but the problem is the license, because a LGPL library can only be linked with LGPL code. However, I'd like to build a commercial app, so I ask if is possible to use a stub that launches a DLL version of the Mono runtime and executes my app. Or do you know a better way to do this?
I need a cross-platform framework and Mono seems good, but there are some problem to pack it in one file, so you know a "free" way to do this?
I'm not sure where you have the idea that you must LGPL your app. From Wikipedia:
The main difference between the GPL
and the LGPL is that the latter can be
linked to (in the case of a library,
'used by') a non-(L)GPLed program,
regardless of whether it is free
software or proprietary software.1
This non-(L)GPLed program can then be
distributed under any chosen terms if
it is not a derivative work.
From the LGPL license:
You may copy and distribute the Library (or a portion or derivative of
it, under Section 2) in object code or
executable form under the terms of
Sections 1 and 2 above provided that
you accompany it with the complete
corresponding machine-readable source
code, which must be distributed under
the terms of Sections 1 and 2 above on
a medium customarily used for software
interchange.
If distribution of object code is made
by offering access to copy from a
designated place, then offering
equivalent access to copy the source
code from the same place satisfies the
requirement to distribute the source
code, even though third parties are
not compelled to copy the source along
with the object code.
That says that you merely need to provide access to the source code of the library if it's distributed in binary form. Just make sure you're not creating a derivative work and instead are merely linking to the lib.
If you're not content with LGPL, then you could always purchase a license from Novell.
From http://www.mono-project.com/License:
Mono is available to be licensed
commercially if the LGPL/GPL/X11
combination is not suitable for you.
Mono Tools for Visual Studio Ultimate
Edition includes a commercial
license to redistribute Mono under
non-LGPL terms on Windows, Linux, and
Mac OS X PCs for products with volumes
under 100,000 and revenues under $2M
annually. If your organization intends
to redistribute software which embeds
or bundles Mono, but is unable to
comply with the terms of GNU LGPL v2,
the Ultimate Edition may be right for
you.
For other licensing options, contact
us.
I'm working as a software engineer for a company. We are going to apply some software engineering standards in our development process. We need a tool which provides a repository for our peripheral products (functions, classes, libraries, ...) which is created during software development process for later use. The tool should provide some functionalities (e.g Name of the component, it's functionality, withing which projects it is used?, author, publication date, list of known bugs, user rating, comment, ...) and it's better to have a web-based interface. Does anybody know such a software?
You should check out FogBugz. Its a great project management tool which has recently released Kiln which is source control you can integrate with your projects.
A cheaper alternative is to look at something like XP-Dev.
In my experience, such a tool doesn't exist because the problem is solved differently. Companies typically use component frameworks, whether their own or 3rd party, and develop new components that conform to the component standard from their framework.
Each project then depends on the framework rather than on specific versions of specific components. This also resolves interdependencies and all related version compatibility issues.
Component framework is typically documented somewhere by its vendor and newly created components can be added to your company's wiki, such as mediaWiki.
Alternatively, the company may need some knowledge management. See the introductory videos from kbPublisher. kbPublisher is an OpenSource Knowledge Base which may be even more suitable than a groupware like mediaWiki. The free version of kbPublisher can be downloaded here.
Note each project should have a feature which displays the framework version number and configuration, as needed by staff. This way, when you are targeting a particular client, the system can be identified remotely.
Open source tools like GIT or SVN may provide source code management however they may lack in the functions you are asking particularly bugs or ratings. There are also many paid tools available in the market which not only provides source code management but also management and integrations over projects. You may explore:
TFS https://en.wikipedia.org/wiki/Team_Foundation_Server
Rational Clear Case http://www-03.ibm.com/software/products/en/clearcase