Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: SISSL

In the News (Fri 25 Apr 14)

  Sun Industry Standards Source License - Encyclopedia, History, Geography and Biography
The Sun Industry Standards Source License (SISSL) is a now-retired free and open source license, recognized as such by the Free Software Foundation and the Open Source Initiative.
Later versions of Openoffice.org were dual-licensed under the SISSL and LGPL until the retirement of the SISSL, at which time Openoffice.org was relicensed only under the LGPL.
SISSL is actually compatible with LGPL (Lesser General Public License).
www.arikah.com /encyclopedia/Sun_Industry_Standards_Source_License   (980 words)

 OpenOffice revamps licensing structure - Infomatics   (Site not responding. Last check: 2007-10-13)
The move follows a decision by Sun Microsystems to retire the SISSL in an effort to reduce the proliferation of open source licences.
The SISSL licence was "not used much", said Simon Phipps, director of Sun's Open Source Office, on his blog.
Under the SISSL, developers were not required to publish the code of modifications made to the application.
www.infomaticsonline.co.uk /vnunet/news/2141948/open-office-switches-license   (544 words)

 Re: Differences between LGPL and SISSL ?
SISSL and LGPL are both Free and Open Source licenses, meaning that they satisfy the requirements of both the Free Software Foundation and the Open Source Initiative.
The SISSL acts essentially like a BSD license, allowing code reuse as long as that reuse does not deviate from the referenced standard(s) (in the case of OpenOffice.org, the standards referenced are the OpenOffice.org APIs and the OpenOffice.org file formats).
The reason for the "either/or" option is to encourage proprietary companies to use SISSL code without fear that they will be forced to reveal their "secret sauce" code as actually implemented, since a specification and reference implementation are enough to allow other SISSL community members to make use of new APIs or formats.
www.mail-archive.com /license-discuss@opensource.org/msg05261.html   (364 words)

 Webwereld | Licentie OpenOffice.org wijzigt door toedoen Sun
De sissl is een van vele door de Open Source Initiative (osi) goedgekeurde software licenties en een van de twee licenties waarmee OpenOffice.org werkt.
Alle OpenOffice.org-code valt ofwel onder de sissl ofwel onder de GNU Lesser General Public License (lgpl) licentie, de keuze is aan de individuele ontwikkelaar.
Een kenmerk van de sissl was nu juist dat anders dan bij de lgpl de eigen code niet per definitie gepubliceerd hoefde te worden.
www.webwereld.nl /ref/newsletter/37102   (557 words)

 Sun gives NFS component to open source world – sort of | The Register
SISSL makes source code available to developers, and they are allowed to "modify and distribute source code and derived binaries freely." But they are also allowed to choose whether to keep their mods confidential or to make them public.
The other plus point is the secrecy aspect - under SISSL commercial vendors can keep their development to themselves, if they so choose, whereas under GPL they'd have to release it.
The company also says SISSL "is designed to meet the requirements of the Open Source Definition as articulated by the Open Source Initiative," and that it has submitted the license to the Open Source Initiative for consideration.
www.theregister.co.uk /2000/02/02/sun_gives_nfs_component   (593 words)

 Post-Dated Musings
SISSL works like the BSD and is thus friendly to proprietary companies wishing to modify code without publishing those modifications.
In itself that may not be bad, as the license in effect promotes the fast growth of a market, so arguably open-source projects using the SISSL also benefit from the increased market.
This at least was probably behind the reasoning for using the SISSL to begin with: create a large market for OOo and StarOffice.
homepage.mac.com /luispo/blog/C564357417/E20060327175107   (2076 words)

 OpenOffice.org Goes LGPL - OSNews.com
On 2nd September 2005 Sun announced the retirement of the Sun Industry Standard Source License.
Projects currently using the SISSL under a dual-license scheme, such as OpenOffice.org, are dropping the SISSL and thus simplifying their license scheme as soon as the development cycle allows.
Effectie with the announcement that Sun is retiring the SISSL, OpenOffice.org will in the future only be licensed under the LGPL (.pdf).
www.osnews.com /story.php?news_id=11770   (155 words)

 The Java Community Process(SM) Program - Press & Success - News Stories
The SISSL is approved by the Open Source Initiative (OSI) as a license for “OSI Certified Open Source Software” and is a choice that is within the JCP requirements for JSRs in development through the JCP program.
SISSL allows developers to use Java source code to develop compatible implementations that can be privatized and shipped without divulging the source code.
For developers who want to build incompatible implementations, SISSL requires them to make their source code or a reference implementation available to other developers, who can also use that implementation.
www.jcp.org /en/press/news/licensing_update?showPrint   (2482 words)

 Sun Industry Standards Source License - Wikipedia Mirror US   (Site not responding. Last check: 2007-10-13)
Later versions were dual-licensed under the SISSL and LGPL until the retirement of the SISSL.
Derivative Works: The SISSL requires the license to be duplicated in each source code file.
Distribution under the license: SISSL explicitly states that the holder is granted “world-wide, royalty-free, non-exclusive license.” ([2])
www.wiki-mirror.us /index.php/Sun_Industry_Standards_Source_License   (1001 words)

 The Licenses
The Sun Industry Standards Source License (SISSL) is an open-source license for providing the source code to implement a specified standard, along with the right to use any IP associated with that source code.
The SISSL is a true open-source license and has been certified as such by the Open Source Initiative.
In September 2005 Sun announced that it was retiring the SISSL in support of the Open Source Initiative (OSI) attempts to minimize the number of open source licenses, so as to make the process of choosing a license easier for developers and companies.
www.dreamsongs.com /IHE/IHE-47.html   (5082 words)

 OpenOffice - Reno Linux Users Group Wiki   (Site not responding. Last check: 2007-10-13)
The source code of the suite was released as an open source project in July 2000, with the aim of breaking the market dominance of Microsoft Office by providing a lower-cost, high-quality and open alternative.
The project and software are informally referred to as "OpenOffice," but project organizers report that this term is a trademark held by another party, requiring them to adopt "OpenOffice.org" as its formal name, and abbreviated as OOo.
A final release candidate was expected in April 2005, with the official release in May/June, but due to amount of work needed to be done, the release was delayed.
www.rlug.org /wiki/OpenOffice   (1280 words)

 OpenOffice.org Forum at OOoForum.org :: View topic - OpenOffice license question
My understanding of SISSL is this: you don't have to distribute source, but your binary must be fully read/write compatible with standard OOo documents.
The SISSL allows redistribution, even modified versions, without source, but only in such a way that you can not incompatible proprietary features.
The GPL and SISSL licenses allow different ranges of flexibility in this regard, but in the end, regardless of the license used, any and all incompatible changes must be published openly.
www.oooforum.org /forum/viewtopic.phtml?t=9046   (883 words)

 LinuxElectrons: Sun Moves OpenOffice to LGPL License   (Site not responding. Last check: 2007-10-13)
As most know, OpenOffice.org code was launched under the dual banner of the SISSL and LGPL; licensees could choose which one they wanted to use, and nearly all have chosen the LGPL.
Effective with the announcement that Sun is retiring the SISSL, however, OpenOffice.org will in the future only be licensed under the LGPL.
(The SISSL did not require all changes to the source to be published.) As most OpenOffice.org contributors are already openly contributing to the community, Sun anticipates no problems.
www.linuxelectrons.com /article.php?story=20050906135931593&mode=print   (239 words)

 Application Development Trends - SPL No Longer Required
The company created the Sun Industry Standards Source License, or SISSL, under which the OpenOffice Suite was originally licensed.
SISSL page of the OSI website you'll find a bright red ''Sun has ceased to use or recommend this license,'' just above the definitions.
Apparently, if you're the copyright holder of a license, all you have to do is call up the OSI and declare that the license is retired.
www.adtmag.com /blogs/blog.aspx?a=19736   (810 words)

 Science Fair Projects - Sun Industry Standards Source License
The Sun Industry Standards Source License (SISSL) is recognized as a free and open source license by the Free Software Foundation and the Open Source Initiative.
Under SISSL, developers may modify and distribute source code and derived binaries freely.
Furthermore, developers can choose to keep their modifications private or make them public.
www.all-science-fair-projects.com /science_fair_projects_encyclopedia/Sun_Industry_Standards_Source_License   (252 words)

 Sun Industry Standards Source License
September 2005 angekündigt, die SISSL in Zukunft weder selbst zu nutzen noch anderen zur Nutzung zu empfehlen.
Der Verweis auf die SISSL soll in den nächsten Wochen aus allen Quelltextdateien von OpenOffice.org entfernt werden.
Der Verweis auf die SISSL soll in den nächsten Wochen aus allen Quelltextdateien von OpenOffice entfernt werden.
www.w-w-w.de /Sun_Microsystems/SISSL.html   (215 words)

 LWN: OpenOffice.org License Simplification
All, On 2 September 2005 Sun Microsystems announced that it was retiring the Sun Industry Standards Source License (SISSL), an Open Source Initiative (OSI)-approved software license.
(The SISSL did not require all changes to the source to be published.) As most OpenOffice.org contributors are already openly contributing to the community, we anticipate no problems.
And for those who have been using the SISSL exclusively, we invite you to join us.
lwn.net /Articles/150503   (266 words)

 Houston, Do We Have A Problem? -- garyedwards@...'s comment on "For non-proliferation's sake, Sun asks OSI to retire ...
This is contrary to the SISSL, which did not require all changes to the source to be published and returned to the community.
Which is fine since the SiSSL license they chose to work under was intended to allow for undisclosed modifications.
This is in sharp contrast to the SISSL, which did not require all changes to the source to be published and disclosed.
talkback.zdnet.com /5208-10532-0.html?forumID=1&threadID=13121&messageID=261290&start=-1   (2058 words)

 » 2005 » September | Open Source | ZDNet.com
The Sun set on SISSL, the Sun Industry Standards Source License.
Sun chose to support its newer CDDL license instead of the older SISSL.
OpenOffice, to which Sun has made many contributions, will now be governed by the LPGL, now that SISSL is no more.
blogs.zdnet.com /open-source/?m=20050906   (438 words)

 de: Mail reader
Previous in thread: [de-dev] SISSL auf unseren Webseiten (Michael Kirchner)
M.E. ist das dann beides zu ändern auf den einen Eintrag LGPL.
CollabNet is a trademark of CollabNet, Inc., Sun, Sun Microsystems, the Sun logo, Java, Solaris, StarOffice are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
de.openoffice.org /servlets/ReadMsg?list=dev&msgNo=21603   (212 words)

 gridengine: Mail reader
Previous in thread: [GE dev] SISSL License questiom (Rayson Ho)
I was advised by my mentor to use > the SISSL for the binary > > RPM of SGE that we built.
By any use of this Website, you agree to be bound by these Policies and Terms of Use.
gridengine.sunsource.net /servlets/ReadMsg?list=dev&msgNo=2368   (251 words)

 license-discuss@opensource.org: 7284: Re: Framework Licensing for Developer Flexibility
If you are not confortable with the LGPL, you might want to consider the SISSL (Sun Industry Standard License).
OpenOffice.org is distributed under a dual LGPL/SISSL system: http://www.openoffice.org/license.html The SISSL allows the creation of propietary software, much like the BSD, but it has a clause that you have to either maintain API compatibility or if you break compatibility, publish the new API.
I would feel more confortable with an SISSL license than with a BSD because it better prevents the "hijacking" of your work.
www.crynwr.com /cgi-bin/ezmlm-cgi/3/7284   (498 words)

IBM has, under the SISSL license which allows binary only distribution of derivative works, forked OO to produce the IBM Editors for Workplace (the intended successor to Lotus Notes).
This is a plugin for the Java based Workplace Rich Client Platform (RCP) which is basically the same as the open source Eclipse RCP released under the IBM Common Public License (CPL).
It has not opened any of the code for the Workplace Editors (which are derived from OO) as under the SISSL it is not obliged to.
www.osnews.com /permalink.php?news_id=11770&comment_id=27620   (435 words)

 ITworld.com - Go for broke on open source Java
I'm not sure anyone fully understands the ramifications of the SISSL yet, but most people speculate that it will allow Sun to have final say over what constitutes the official version of Java.
But that conclusion is premature, no matter what SISSL amounts to.
There are still a number of reasons people might want to choose C# over Java but, as Microsoft demonstrated with Internet Explorer, very few things can stand up for long against free competition -- especially when the free product shows up on every copy of the operating system whether you want it or not.
www.itworld.com /AppDev/716/lw-11-penguin_1/pfindex.html   (1373 words)

 New DivaBlog: Copyright Assignment
It gets a few things wrong...for instance the assertion that the SISSL grants copyright to Sun.
In fact the thing that does that is the Joint Copyright Assignment, a separate document which must be signed and on file at Sun before a contribution can be accepted into the main OpenOffice.org source tree from outside of Sun.
Licensing stuff is complex and hard to explain in sound-byte format, unfortunately...so its not surprising that David didn't get it exactly right.
danesecooper.blogs.com /divablog/2005/04/copyright_assig.html   (731 words)

 Choose a License
A variety of licenses have been created to meet the different needs of open source projects---the original Berkeley Unix was released under the Berkeley Software Distribution (BSD) license, Linux and Emacs use the GNU General Public License (GPL), while Netscape created the Mozilla[TM] Public License (MPL) for its browser.
Over 40 different licenses have been certified as meeting the criteria for open source by the Open Source Initiative, a nonprofit corporation dedicated to managing and promoting the Open Source definition (http://www.opensource.org), and it is unknown how many additional licenses have been created for use by other open source projects.
It is possible to make your source code freely available using open source, but require people to license your patents before they can distribute any software based on the source code.
www.java.net /choose_license.csp   (2218 words)

Try your search on: Qwika (all wikis)

  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.