Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:I'll follow them here too. :D (Score 4, Informative) 293

Is this some kind of back-handed comment based on the general view at Microsoft about Open-source software, or the general view that MS would like to push out to userland? That people should use MS OSS because you need to be a developer to use it on other platforms?

No-no.. exactly the opposite

Have you tried to roll out some OSS apps on Windows?

On Linux it's two clicks, and BAM! Done.

On Windows, it's almost never that easy to setup OSS apps.

The problem I see is that it doesn't take a Developer on Linux to get Apache installed and configured. Why should it on Windows?

Comment Re:I'll follow them here too. :D (Score 5, Informative) 293

No.

My intent is to completely do away with the practice of everybody shipping every damn shared library. It's one of the things that piss me off the most. I've got a very workable solution that uses WinSxS to cleanly handle this.

It is extremely important that there is a unified method for sharing libraries between apps.

Comment Re:I'll follow them here too. :D (Score 5, Informative) 293

That is precisely the red tape that I had cut.

Microsoft has given me a signed contract that says that whatever I produce for the CoApp project isn't owned by them. They do get a license to everything I make (fair deal), but they don't own it in the end.

That, and I've also chosen the BSD license for it's do-what-the-f*-you-want spirit.

Comment Re:I'll follow them here too. :D (Score 4, Informative) 293

Well, considering that I spent several months hacking thru red tape to get VP approval, and the enthusiasm that I've been getting, I'm pretty damn confident that we're clear sailing.

And given the first three targets that on my radar are PHP, Apache and Python (and the 40 or so shared library dependencies), and that's what I took to the VP, I'm fairly confident that's not going to be an issue.

And, on top of that, MS doesn't own the project, I do. "Shutting it down" is not an option for them.

Microsoft

Submission + - MS's CoApp to help OSS devolpment, deployment (msdn.com) 1

badpazzword writes: "Microsoft employee Garrett Serack announces he has received the green light to work full time on CoApp, an .msi-based package management system aiming to bring a wholly native toolchain for OSS development and deployment. This will hopefully bring more open source software on Windows, which will conversely bring OSS more users, testers and developers. Serack is following the comments at Ars Technica, so he might also follow them here. The launchpad project is already up."
Microsoft

Submission + - Package Management System for Windows: CoApp (msdn.com)

An anonymous reader writes: Microsoft's Garrett Serack has started a new project called the Common Opensource Application Publishing Platform. It aims to bring a package management system for open source applications to the Windows platform. Garrett writes on his blog, 'Listen up folks, this stuff is big. Today, I’m announcing the beginning of a project that intends to bring a little joy into the hearts of Open Source aficionados on the Windows Platform. The biggest challenge to using/building/maintaining many Open Source applications on Windows, is that Windows does a lot of things differently than Linux and Unix . Different filesystems, command lines, APIs, user experiences well, pretty much everything. Regardless of personal opinions about it being the ‘right-way’ or ‘wrong-way’, it suffices to say that it is just simply different. In order to build an Open Source application like PHP for Windows from scratch, I need to have a collection of libraries created from a fair number of different projects. This creates a dependency between the code that I’m working on—PHP—and the project that supplies the library that I need. ' More information is available at CoApp's Launchpad page and the CoApp wiki.
Microsoft

Submission + - OSI approves two Microsoft shared-source licenses (linuxworld.com)

An anonymous reader writes: Linuxworld reports that The board of the Open Source Initiative (OSI) has approved two Microsoft Corp. licenses that allow proprietary source code to be shared, a move that is likely to inspire protest and spur controversy for die-hard open-source proponents.
There's the link to OSI's original announcement.

Microsoft

Submission + - OSI approves Microsoft's open source licenses

Stony Stevenson writes: The Open Source Initiative has approved the Microsoft Public Licence and Microsoft Reciprocal Licence, officially branding them as open source licences. The OSI approves licences by validating compliance to ten rules set in the Open Source Definition. The decision was reached with an "overwhelming majority " of the votes, but not unanimously, OSI president Michael Tiemann said in a posting on the group's website.

Microsoft welcomed the decision. "This is a significant milestone in the progression of Microsoft's open source strategy and the company's ongoing commitment to participation in the open source community to effectively meet the evolving needs of developers," the company said in an emailed statement. But I'm not so sure the open source community will be so happy about it. Critics have charged in the past that the addition of the licence is an attempt by Microsoft to undermine open source.

Slashdot Top Deals

Scientists will study your brain to learn more about your distant cousin, Man.

Working...