
	Where results make sense

Topic: Shared source

Related Topics

file sharing

time sharing

market share

shared libraries

distributed shared memory

mind share

secret sharing

share alike

shared source

code sharing

share finance

Needle Sharing

In the News (Tue 21 May 13)

EXECUTIVE POWER

Iran

ANALYSIS

Pakistan

Family compact

	Who Is Behind "Shared Source" Misinformation Campaign? \| Open Source Initiative
		But identifying them as 'shared source' licenses, which has nothing whatsoever to do with why they were submitted nor why they were approved is a way to jam a contrary concept—shared source—into an open source conversation.
		Shared source is an insurgent term that distracts and dilutes the Open Source message by using similar-sounding terms and offering similar-sounding promises.
		Let us see who is accountable for injecting 'shared source' into the business of the OSI, and let us see whether Microsoft will clarify that indeed 'shared source' has nothing whatsoever to do with open source, so that their newly minted open source licenses do not fall under a cloud of suspicion.
	opensource.org /node/225 (923 words)

	Shared source - Wikipedia, the free encyclopedia
		Though shared source licensing allows for source code access, it is not open source according to the Open Source Definition, because none of the license programs allows for commercial use of modified code.
		Shared source licenses provide a number of benefits to end users that are not present in typical proprietary software licenses.
		Shared source benefits the copyright holder in that much tighter control is kept over the use of their product than open source licenses, which generally include the voluntary abdication of many of the author's rights.
	en.wikipedia.org /wiki/Shared_source (733 words)

	Closed source - Wikipedia, the free encyclopedia
		Closed source is a term invented as an antonym for open source and refers to any program whose licensing terms do not qualify as open source.
		The source code of such programs is usually regarded as a trade secret of the company.
		Microsoft's "shared source" initiative is a prominent example of this.
	en.wikipedia.org /wiki/Closed_source (159 words)

	ONLamp.com -- Perspectives on the Shared Source Initiative
		Microsoft began pushing the idea of "shared source" a few years ago as a way to talk about source code sharing exercises they continue to develop in the face of open source software practices.
		Most people imagine Shared Source as an avenue to open sourcing Microsoft's key product assets and are disappointed when they see restrictive licenses and difficult eligibility requirements.
		Enterprise Source License Program, etc.) There is tightly controlled access to the code, with restrictions on what people can do with it (often read or debug or limited modification without redistribution rights).
	www.onlamp.com /pub/a/onlamp/2005/03/24/shared_source.html (2515 words)

	IT Conversations: Jason Matusow - Microsoft and Shared Source
		Jason Matusow, Microsoft's Shared Source Manager, discusses the effects of the open source software model and how the benefits of this model may be applied to commercial software.
		Matusow also provides details on the Shared Source offerings from Microsoft and how organizations are improving their information technology solutions through interaction with source code.
		As manager of the Shared Source Initiative at Microsoft Corp., Jason Matusow is responsible for working with internal and external constituencies to establish the company-wide framework for Microsoft’s global source licensing strategy.
	www.itconversations.com /shows/detail138.html (358 words)

	NewsForge \| Why Shared Source is not Open Source
		The Shared Source initiative is a balanced approach that allows Microsoft to share source code with various communities while maintaining the intellectual property rights needed to support a strong software business.
		Indeed, Shared Source is not even related to Open Source in any substantive way, because it gives its users none of the advantages they get from using real Open Source.
		Shared source turned to be a result of the pressure of the open source movement.
	www.newsforge.com /newsforge/03/03/12/1330253.shtml?tid=9 (2732 words)

	IT Manager's Journal \| Microsoft defines position on shared-source code (Site not responding. Last check: )
		Shared source, which is the way the company shares code with its worldwide partners, isn't exactly open source.
		Jason Matusow, manager of Microsoft's Shared Source Initiative, offered an explanation and answered some questions on the topic on the second day of the Open Source Business Conference on a summerlike Northern California day.
		Asked if he thought open source applications were generally more secure because more eyes had vetted the code, Matusow said: "I challenge the idea that just because a project is open source that it's inherently more secure.
	software.itmanagersjournal.com /software/04/03/18/1538206.shtml (1125 words)

	What is shared source? - a definition from Whatis.com
		Under a shared source program license, authorized parties are granted full or partial access to source code.
		Critics have described shared source as a marketing ploy and suggested that the approach could pose a threat to the purity of the open source model.
		In a paper called "Shared Source: A Dangerous Virus," the Open Source Initiative called Microsoft's shared source program "a trap for the unwary" and warned that developers who'd been exposed to it should be considered "contaminated" and not assigned to projects that were competitive with Microsoft products.
	searchenterpriselinux.techtarget.com /sDefinition/0,,sid39_gci1149804,00.html (334 words)

	Slashdot \| Microsoft 'Shared Source' Attempts to Hijack FOSS
		This is very roughly the sense of closed that applies to the some of the shared source licenses, in that the code is open to the public only in the sense that anyone willing to follow all of the "membership requirements" is allowed to use it.
		The shared source license is somewhat different in that the specific use case it is designed to solve is a marketing one, rather than a functional one.
		My personal thought about this is that the Shared Source license is a way for Microsoft to make use of open source in some applicable categories without having their code licensed under something that is controlled by an organization of wingnuts, like the FSF.
	linux.slashdot.org /linux/08/05/12/1325203.shtml (4180 words)

	tecosystems: What is Shared Source?
		My answer to this question is actually quite simple: the term Shared Source, as people have come to understand the definition around Windows, is having a drag effect on projects released under more permissive terms.
		At their core, open source projects to me are about having access to the source code itself.
		Unless you're imbuing the term open source with some intangible philosophical requirements, in which case one should be upfront about those biases because not everyone shares them.
	www.redmonk.com /sogrady/archives/000550.html (708 words)

	ONDotnet.com -- Microsoft's Shared Source Record
		The ECMA CLI is just the latest in a series of shared source releases that represent a big shift in a company that’s used to having complete control over their products (and the code within them).
		But shared source is more in line with how Microsoft wants to release code outside its organization, and it has released several shared source products, in addition to the CLI it plans to release.
		Under the terms of shared source, modified code cannot be released commercially without a license from Microsoft, and even then, those modifications have to go back to Microsoft.
	www.ondotnet.com /pub/a/dotnet/2002/03/25/shared.html (1388 words)

	Proposal for an Open Source Shared Runtime Layer (Site not responding. Last check: )
		Historically, open source developers have been good at creating widely-adopted solutions that promote interoperability and code reuse, while proprietary vendors have found it difficult to solve interoperability problems because of their attachment to their own proprietary technology.
		Open source developers tend to be focused on evolving the particular development environment they're working on, rather than stepping back to consider the state of free software as a whole.
		A shared in-process component system and runtime is an enabling technology; it allows entire open source projects to work together, much as the Internet allowed individual open source developers to work together.
	people.redhat.com /~hp/proposal/proposal.html (3806 words)

	Slashdot \| Shared Source?
		The funny thing is that Shared Source, if shared-source.com is to be believed, is worse than source code licenses that MS has used in the past.
		All their games they port are proprietary closed source programs, but they can sell the games with the SDL library packaged with it as long as they allow people free access to the source code of the library.
		If MS spreads its source code wider via this "shared source" concept, they'll still have all the copyright protection they could ask for and now it will be much harder to find virgins who can work on competing/compatible products.
	slashdot.org /articles/01/05/18/1659252.shtml (6329 words)

	Integration Developers News (Site not responding. Last check: )
		Matusow also told OET that the concepts of Shared Source reflect a "movement to the middle" between totally proprietary and totally "open and free" software, and that the flavor of Microsoft's Shared Source program in some ways was based on lessons learned from watching the Open Source community.
		While I can't give the name of the firm, there is also a large financial institution that had created a custom built trading application, and their developers were concerned about how it interacted with the encrypted file system and the device drivers that were needed on laptops to pre-deploy them.
		When the dot com boom was really flying, many had this attitude: "I am 100 percent Open Source, and I am going completely on a 'loss leader' model." Their idea was to generate a lot of interest and a big community and then monitize that later.
	www.idevnews.com /IntegrationNews.asp?ID=28 (1540 words)

	Microsoft to Submit Shared Source Licenses to OSI - O'Reilly Radar
		This open source initiative might be a hint of the very long road for Microsoft towards true free software with a GPL license, and not because they want to but because market forces dictate it for their corporate survival.
		Unless the Shared Source licenses have changed significantly since I last looked at them (or Microsoft is willing to change them significantly in response to feedback) I don't see how they could pass OSD muster, especially with the gratuitous "thou shalt not use the GPL" conditions.
		Microsoft applies the phrase 'shared source' to multiple licenses, some of which would be considered 'open source' by the OSI and (it appears to me from a cursory glance) free software by the FSF, and other licenses which are plainly proprietary licenses.
	radar.oreilly.com /2007/07/microsoft-to-submit-shared-sou.html (9833 words)

	Plays Well with Others: Microsoft Moves to "Shared Source"
		The documents surrounding the announcement challenge the corporate backers of the Open Source movement (as in Linux), saying, in essence: “Your underlying philosophy is mistaken and your business model is wrong.” Images of swords at dawn flash to mind.
		Open Source is backed by deep corporate pockets, and their programmers are quite comfortable.
		All work on Linux is conducted under the General Public License, which says that any code written for the system and distributed beyond the developer must be made available to all at no cost.
	www.cei.org /gencon/016,02029.cfm (612 words)

	LinuxDevCenter.com -- Shared Source vs. Open Source: Craig Mundie and Michael Tiemann
		Now, of all the choices, open source makes it easier to be rather than to seem.
		For example, from this perspective, there is no reality to Microsoft's shared source license in the sense that, as [with] many well-spun phrases, it's not unlike the alternative minimum tax: it is neither alternative nor minimum.
		This shared source thing may be "It's only 1.0." — [but it] has nothing to do with community outside of Microsoft.
	www.linuxdevcenter.com /pub/a/linux/2001/08/09/oscon_debate.html?page=4 (1191 words)

	Microsofts Linux lab head takes on shared source initiative - Computer Business Review
		The head of Microsoft Corp's Linux and Open Source Software Lab is taking on responsibility for the company's shared source initiative after its former manager, Jason Matusow, stepped up to the role of director in the corporate standards strategy team.
		Microsoft's shared source initiative was launched in May 2001 as a way to offer customers access to its code in response to the growth of the open source software model.
		It remains to be seen how Hilf will manage the ongoing evolution of the shared source initiative, but with more than 10-years experience with open source software, the former senior director of engineering for eToys and member of IBM's Linux technical strategic team has a good understanding of the open source development model.
	www.cbronline.com /article_news.asp?guid=953EEAC1-4410-4B76-8BCE-672182542EF4 (774 words)

	FileForum \| Microsoft Shared Source CLI
		The Shared Source CLI is a compressed archive of the source code to a working implementation of the ECMA CLI and the ECMA C# language specification.
		It is released under a shared source initiative.
		The Shared Source CLI goes beyond the printed specification of the ECMA standards, providing a working implementation for CLI developers to explore and understand.
	fileforum.betanews.com /detail/1017294124/1 (130 words)

	[No title]
		The Shared Source initiative framework supports a spectrum of programs and licenses offered by Microsoft to various communities of customers, partners, developers and other interested individuals.
		However, projects can be based on any source of quality software that can be improved and expanded to meet the needs of the academic community.
		One of the first toolkits available for the academic community and the ASSC is Shared Source for Assignment Manager.
	www.msdnaa.net /assc (252 words)

	Microsoft simplifies Shared Source programme - ZDNet UK News
		Microsoft has simplified its programme for sharing source code in an effort to work better with third parties.
		Microsoft's Shared Source Initiative is a programme to allow third parties, such as other software companies and large customers, to see portions of Microsoft source code.
		"As with other individuals and organisations, we too have seen the proliferation of source code licenses become problematic," Jason Matusow, the director of Microsoft's Shared Source programme, wrote in a blog on Wednesday.
	news.zdnet.co.uk /software/applications/0,39020384,39232060,00.htm (616 words)


		Mundie set off a far-reaching discussion recently when he introduced Microsoft's Shared Source program, which blends access to source code with the preservation of strong intellectual property rights by software developers, and contrasted Shared Source to Open Source and the GNU General Public License.
		There's been a strong response from the open source and free software communities, accusing Microsoft of trying to co-opt the momentum of open source with a program that offers superficial similarities, but few of the real benefits.
		Mundie will discuss ways in which Shared Source differs from Open Source, and why Microsoft believes that the Shared Source Philosophy supports a strong software business case for commercial software developers and their customers.
	conferences.oreillynet.com /cs/os2001/view/e_sess/1834 (267 words)

	RISC OS Open: Shared Source FAQ
		The primary objectives of sharing the sources to RISC OS are to bring RISC OS software to a wider community and to encourage growth in both the RISC OS user and developer communities.
		The shared source RISC OS project is maintained by RISC OS Open Limited on a not-for-profit basis with Castle Technology Limited.
		From that definition, it is clear that the shared source RISC OS project is not open source for the simple reason that it makes a distinction between people who want to use or access the RISC OS sources for non-commercial purposes and those who want to use them for commercial purposes.
	www.riscosopen.org /content/documents/ssfaq (2045 words)

	Castle reveal shared source licence - RISC OS News, Software and Information
		ROOL are said to be running the project on a not-for-profit basis after announcing their intention to manage the 'shared source code' around a year ago.
		Shared source is a con, really: commercial companies (such as Micros~1) are asking for you to donate your time, your effort, your help, to their profit-making enterprises, and in return, you get nothing except the right to play with their product.
		Shared Source is as it always has been, a timorous toe in the water for companies too scared to take the plunge and go Free.
	www.drobe.co.uk /riscos/artifact1958.html (4244 words)

	Is Community Server Open Source?
		Open source isn’t just about whether the source code is available, it is all about the license to the source code.
		At the same time, I am passionate about Open Source software and it is important to me to help keep the distinctions clear and educate others on what open source software is and the value it provides.
		Their approach makes the source transparent and adaptable, contributes to a rapidly growing development and user community exploring this accessbility, and provides some measure of predictable direction and quality to the core product.
	haacked.com /archive/2006/07/25/IsCommunityServerOpenSource.aspx (2668 words)

Try your search on: Qwika (all wikis)