Follow Us on Twitter
by MichaelF on August 10, 2006 12:10pm
The second person we interviewed during the LANG.NET symposium is John Lam. John is the creator of RubyCLR and most recently he created an Avalon Ruby Editor (we capture a short demo near the end of this video. Let me acknowledge now that, yes, I need to work on my skills capturing demos on film.)
John has his own blog: http://www.iunknown.com and he has an entry about his time with us in the lab here.
Credit to John's Blog for the photo below, from his visit to the Open Source Software Lab
by anandeep on January 18, 2007 02:15pm
Prof Stephen R. (Steve) Schach is an Associate Professor of Computer Science and Computer Engineering at the Vanderbilt University.
Port 25 met up with him while he was visiting Seattle, Washington in picturesque Kirkland, Washington on the shores of Lake Washington.
Steve (he hates being called Prof Schach!) believes in gathering data to make predictions. While he accepts that there may be interpretations of data he thinks gathering the correct data is paramount.
He credits Open Source Software with kick starting the Empirical Software Engineering movement saying “We could count the number of lines of code in gcc and Linux – we couldn’t do that with Windows 95!”.
In this interview we discussed empirical software engineer/computer science and some of the work Steve has been doing. This includes his work on the proportion of time that code is in bug fixing mode and his work on global variables in Linux.
The latter work was found to be controversial by the Open Source Community. Steve thought that all he was doing was counting the number of global variable in Linux vs BSD and stating that Linux had far more than is considered wise! This was surprising to Steve, but isn’t that much of a surprise to the people who know how much passion Open Source can generate!
Steve’s website is here http://www.vuse.vanderbilt.edu/~srs/ and you can find his publications on his website.
Microsoft and The Open Group have announced the release of Open Management Infrastructure (OMI), an open source project to further the development of a production quality implementation of the DMTF CIM and WBEM standards. The Windows Management team has a blog post covering the details of OMI and the goals of the project.
OMI (formerly known as NanoWBEM) is an implementation of the DMTF Common Information Model (CIM) standard, which defines the semantics of management information for networks, applications, and services. Here’s a high-level overview of OMI’s implementation of a CIM server:
Just as the Hardware Abstraction Layer (HAL) helped open up the x86 hardware ecosystem and enable rapid innovation across the industry, CIM-based tools such as OMI form a Datacenter Abstraction Layer (DAL) that provides a framework for interoperability between management tools across diverse platforms and devices. As noted on the Windows Server blog:
“… the growth of cloud-based computing is, by definition, driving demand for more automation, which, in turn, will require the existence of a solid foundation built upon management standards. For standards-based management to satisfy today’s cloud management demands, it must be sophisticated enough to support the diverse set of devices that are required and it must be easy to implement by hardware and platform vendors alike. The DMTF CIM and WSMAN standards are up to the task, but implementing them effectively has been a challenge. Open Management Infrastructure (OMI) addresses this problem.”
Keep an eye on The Open Group’s OMI project site for the latest news about OMI’s evolution. You can download OMI source code and documentation today (available under an Apache 2.0 open source license), and soon you’ll find information about more detailed documentation, contribution facilities, and OMI developer conferences.
Doug MahughSenior Technical EvangelistMicrosoft Open Technologies, Inc.
by Sam Ramji on December 19, 2007 11:03pm
First, let me say thanks to Jeremy Allison and Andrew Tridgell for their decades of hard work and their optimism.
Back in March, Jeremy invited me to talk about Samba and Microsoft, and how we could work together. It turned out that our first opportunity to meet was actually at the annual Samba developers’ conference, SambaXP in Gottingen, Germany in late April. I spent three days there listening to the Samba Team's reports on work they were doing, their observations relating to Microsoft protocols, and at breakfast with Tridge, Jeremy, and other team members we established a potential roadmap for collaboration. Frankly, I think my commitments were viewed with disbelief by some but with cautious optimism by Tridge and Jeremy – as well as by Dan Shearer and by John Terpstra, a man of vision and entrepreneurial spirit.
I worked with legal and engineering teams at Microsoft once I returned from Germany, and over a few weeks in May I got consensus that we could help the Samba Team by delivering on the roadmap. This included donating software licenses (MSDN Premium subscriptions) to the core team, building a test bed and beginning to share testing tools, preserving the UNIX extensions in CIFS to ensure that the work Jeremy and Steve French were doing would continue to be compatible with Microsoft implementations, accepting Samba Team’s observed bugs in Microsoft’s CIFS implementation and vice versa, providing some technical support on CIFS questions, and sending Microsoft engineers to the CIFS Conference @ Google in September 2007.
About the same time, Tom Hanrahan of IBM’s Linux Technology Center and the OSDL joined my team at Microsoft. His experience in working with Linux – and with Tridge – made it clear that we could sustain the work required to support the roadmap. Apart from his three decades of software engineering and management, one of Tom’s greatest assets is his combination of patience and perseverance; we knew it would take time and progress would be slow, but worthwhile. We’re still early in the process of doing joint testing and engineering with the Samba Team, and have many milestones to achieve (for example, shared test suites & frameworks). Thanks to Tom’s work with key engineers and managers in the company, we have already made progress and are committed to the long term.
Based on the dialog we’d established with Tridge and Jeremy, when the European Commission published the terms that would satisfy them in regards to Microsoft protocols, I saw an opportunity to continue aligning our work with the Samba Team. The terms were good, but the Samba team wanted Microsoft to make some changes to fully conform with the existing practices of the Samba developer community. Jeremy and Tridge saw the opportunity as well, and thus began a 6+ week process of improving and correcting the agreement to arrive at terms that both dramatically expanded their access to protocol information and enabled the Team to continue developing Samba as they have in the past. Attorneys and technologists (always an odd combination) on both sides worked hard to refine the language and do so in a clear and cooperative way. The discussions were masterfully led by Microsoft’s GM of Protocol Programs, Craig Shank (ex-Lineo!) and Samba’s Andrew Tridgell.
Today the Samba Team announced that they’re satisfied with the agreement, and are taking a Work Group Server Protocol Program (WSPP) trade secret and copyright license. This will give them access to Microsoft specifications for the protocols in WSPP (such as file, print, and user and group administrative services) and allow the Samba Team to create, use, and distribute implementations. I expect that this will significantly improve the process of Samba development, and produce better quality interoperation between Windows and Linux/UNIX environments.
What this process has shown me is that if we focus on technology, and patient, diligent execution, we can make real progress together.
This is a historic moment, and one that I’m proud of. But it is only a moment, and now it’s time to get back to working on interoperability, one day at a time.
By Gianugo RabellinoSenior Director Open Source CommunitiesMicrosoft Open Technologies, Inc.
As I write this, I’m exploring the public preview of VM Depot, a new service from Microsoft Open Technologies, Inc. VM Depot is a community-driven catalog of open source virtual machine images for Windows Azure. On VM Depot the community can build, deploy and share their favorite Linux configuration, create custom open source stacks, work with others and build new architectures for the cloud that leverage the openness and flexibility of the Windows Azure platform.
The preview launch of VM Depot today is an introduction of things to come: you can already easily deploy different Linux-based virtual machines that include custom and curated installations and configurations. (We have the latest, full-fledged distributions of Debian, Alt Linux and Mageia for your hacking pleasure.) You can comment on them. You can rate them. And, what’s more, you can remix them to your liking and possibly share the results with other members of the community. Or why don’t you go ahead and just create a new one from scratch with your favorite software? For ultimate speed, you can quickly deploy images already customized for specific business scenarios. All this is just a few clicks away, completely free of charge and just waiting for your input to make it better. To learn more, see Getting Started with VM Depot.
VM Depot is another illustration of how the Azure platform is effectively open. As complex as it may seem, VM Depot was relatively easy to build as it relies exclusively on published Azure APIs. As we explore the meaning of openness and interoperability of cloud platforms, I can now say that Windows Azure is at the forefront of the debate and provides compelling proof that documented APIs can do wonders to enable building amazing new applications that leverage the cloud.
Some days you can’t help smiling. I had a big smile on my face back in June when Microsoft announced it was making preconfigured Linux images available in Windows Azure gallery and today I have another reason to be happy as I see how Microsoft Open Technologies is helping open source communities work even more collaboratively with the Windows Azure platform.
VM Depot wouldn’t have been possible without the support of a number of partners who have contributed images and packages for this preview launch, including Alt Linux, Basho, Bitnami and Hupstream. Here what they have to say about VM Depot:
"Ease of deployment is one of the key discussions we have with all of the companies leveraging Riak for their highly-available, scalable data storage needs. The VM Depot indicates that Microsoft Open Technologies is dedicated to supporting the needs of today's enterprise with the Windows Azure Platform" - Tyler Hannan, Director of Technical Marketing, Basho Technologies, Inc.
“The launch of Azure Virtual Images and now the VM Depot demonstrate that Microsoft is serious about building out its cloud computing platform. We are thrilled to be a part of this new marketplace, which simplifies deployment of the top open source applications to the enterprise-ready Azure platform, taking Windows Azure to a whole new level.” – Erica Brescia, CEO of BitRock, developers of Bitnami
“The demand for cloud computing is there, and Hupstream had the skills to adapt a distribution to the specifics of cloud computing, and provide support as needed. We also wanted to make Debian and Mageia more accessible, and cloud platforms are the simplest way to get started. This was also an opportunity to establish a conversation between actors that traditionally shun each other. Notably, we had excellent collaboration with Microsoft engineers and other community members, while working on a common goal: expanding the reach of developers with Linux.” – Romain d'Alverny, Managing Partner & Engineer at hupstream
I have been doing a fair amount of traveling for MS Open Tech lately where I’ve met a number of great people from the open source community. After a wonderful holiday break, we’re off to an exciting and busy New Year. I know I will use every free moment this month to peek at the VM Depot dashboard and see our latest creation take its first baby steps. Expect more in the upcoming weeks and please help us make VM Depot the best place for open source communities to work together and build shared images for the cloud. See you there.
From Jean Paoli
Since we launched Microsoft Open Technologies, Inc. (MS Open Tech) as a subsidiary, project ideas have poured into our team from inside and outside the company as we shipped many open source projects and participated in many open standards activities.
After a few months of existence I want to provide you some insights on how we are functioning internally: we are working on many projects and are hiring ten full time employees: we are hiring developers, technical program managers, standards professionals and technical evangelists! We will be posting the jobs descriptions in a few weeks (and will update this blog with a link to apply).
We have also been thinking about how to scale in order to be able to work across the many projects that could be interesting to MS Open Tech, Microsoft, and to the industry as a whole.
I am pleased today to introduce the MS Open Tech Hub (the Hub):
We created the Hub as new engineering program for MS Open Tech engineers: It is a collaborative place to build open source projects, exchange and evolve open source engineering best practices, and marshal and temporarily assign resources from Microsoft to MS Open Tech (in addition to MS Open Tech full time employees) based on the needs of specific projects.
As the photograph above shows, the entire MS Open Tech team is excited and energized around the announcement of the Hub.
The number one goal of the Hub is to build, accept contributions or contribute to open source projects. Based on the needs of open source projects, engineering resources from Microsoft teams may be temporarily assigned to MS Open Tech to participate in the Hub, where they will collaborate with the community, work with the MS Open Tech full time employees and contribute to MS Open Tech projects. This collaboration will further help us exchange and evolve open source engineering best practices for open source.
The goal of the MS Open Tech Hub is to create a pool of talent where developers, testers, architects and others push boundaries, explore the toughest questions, and advance our investment in openness. The Hub brings together some of our best and brightest engineers to join together, work with the open community and toward the ultimate goal – building, accepting and contributing to interoperability, standards and open source projects.
For example, the Entity Framework team joined the MS Open Tech Hub, and brought today’s open source Entity Framework project to life. This team was able to quickly organize engineering and open development resources to be ready to start collaborating with the open source communities. EF will join the other open source components of Microsoft’s dev tools and frameworks – MVC, Web API, and Web Pages with Razor Syntax – to help increase development transparency for this project.
Get to know our team and find out what they like about collaborating in the Hub.
We’ve learned through the years that great ideas happen when smart, passionate and creative people come together in a collaborative environment that enables new ideas to flourish.
A few photos of a typical day in the MS Open Tech Hub
Jean Paoli President Microsoft Open Technologies, Inc. A subsidiary of Microsoft Corporation
by Peter Galli on July 06, 2009 12:27pm
I have some good news to announce: Microsoft will be applying the Community Promise to the ECMA 334 and ECMA 335 specs.
ECMA 334 specifies the form and establishes the interpretation of programs written in the C# programming language, while the ECMA 335 standard defines the Common Language Infrastructure (CLI) in which applications written in multiple high-level languages can be executed in different system environments without the need to rewrite those applications to take into consideration the unique characteristics of those environments.
"The Community Promise is an excellent vehicle and, in this situation, ensures the best balance of interoperability and flexibility for developers," Scott Guthrie, the Corporate Vice President for the .Net Developer Platform, told me July 6.
It is important to note that, under the Community Promise, anyone can freely implement these specifications with their technology, code, and solutions.
You do not need to sign a license agreement, or otherwise communicate to Microsoft how you will implement the specifications.
The Promise applies to developers, distributors, and users of Covered Implementations without regard to the development model that created the implementations, the type of copyright licenses under which it is distributed, or the associated business model.
Under the Community Promise, Microsoft provides assurance that it will not assert its Necessary Claims against anyone who makes, uses, sells, offers for sale, imports, or distributes any Covered Implementation under any type of development or distribution model, including open-source licensing models such as the LGPL or GPL.
You can find the terms of the Microsoft Community Promise here.
I told you this was good news!
by Peter Galli on July 21, 2009 06:15am
Today, Microsoft announced the Live Services Plug-in for Moodle, a free download released under the General Public License v2 that integrates Microsoft's Live@edu services such as email, calendar, instant messaging and search directly into the Moodle experience. What's even better is that this new, integrated experience is accessible via a single sign-on, which lets teachers and students access the resources and services they need to efficiently communicate, collaborate and learn. Moodle is a free open source course management system that teachers use to create online learning websites for their classes, and has some 30 million users in 207 countries. The plug-in and its feature set was designed as a result of extensive feedback from teachers and institutional IT leaders, and licensed in a way that is consistent with the practices of the open source community - freely under the GPL v2. The news of the release of the Live Services Plug-in for Moodle under GPL v2 follows hot on the heels of Microsoft's release yesterday of 20,000 lines of device driver code to the Linux community under GPL v2. This means that teachers and institutions can download the plug-in under a widely used open source license agreement and under the same terms that Moodle itself is licensed. This approach underscores Microsoft's commitment to interoperability and open standards, as well as to collaboration so as to help customers, partners, educators and students across the world be successful in a heterogeneous technology world. With the Live Services Plug-in, educators can email class notes and lecture slides to everyone in the class as well as send alerts regarding homework assignments or quizzes - all from within the same environment. Students can also utilize Bing for search, check their calendar, send an email or just an instant message - without having to manage multiple accounts in multiple systems. They can do it all right within Moodle. They can also check unread emails using advanced features like keyboard shortcuts to check email quickly for example between class periods or just before lectures start. The Microsoft Live Services Plug-in for Moodle will be part of a growing collection of solutions available from the Microsoft Education Labs. For more on this news, you can read the blog from L. Michael Golden, Corporate Vice President of Microsoft's Education Products Group, as well as what Moodle founder Martin Dougiamas has to say about the plug-in.
Today, Microsoft announced the Live Services Plug-in for Moodle, a free download released under the General Public License v2 that integrates Microsoft's Live@edu services such as email, calendar, instant messaging and search directly into the Moodle experience.
What's even better is that this new, integrated experience is accessible via a single sign-on, which lets teachers and students access the resources and services they need to efficiently communicate, collaborate and learn.
Moodle is a free open source course management system that teachers use to create online learning websites for their classes, and has some 30 million users in 207 countries.
The plug-in and its feature set was designed as a result of extensive feedback from teachers and institutional IT leaders, and licensed in a way that is consistent with the practices of the open source community - freely under the GPL v2.
The news of the release of the Live Services Plug-in for Moodle under GPL v2 follows hot on the heels of Microsoft's release yesterday of 20,000 lines of device driver code to the Linux community under GPL v2.
This means that teachers and institutions can download the plug-in under a widely used open source license agreement and under the same terms that Moodle itself is licensed.
This approach underscores Microsoft's commitment to interoperability and open standards, as well as to collaboration so as to help customers, partners, educators and students across the world be successful in a heterogeneous technology world.
With the Live Services Plug-in, educators can email class notes and lecture slides to everyone in the class as well as send alerts regarding homework assignments or quizzes - all from within the same environment.
Students can also utilize Bing for search, check their calendar, send an email or just an instant message - without having to manage multiple accounts in multiple systems. They can do it all right within Moodle. They can also check unread emails using advanced features like keyboard shortcuts to check email quickly for example between class periods or just before lectures start.
The Microsoft Live Services Plug-in for Moodle will be part of a growing collection of solutions available from the Microsoft Education Labs.
Congratulations to all the people involved in the PhoneGap community for the recent release of version 1.3 of their HTML5 open source mobile framework!
This release includes many new features, and you can find more details here. You may remember that we announced back in Sept that Microsoft was helping to bring Windows Phone support in PhoneGap: I am happy to say we can now checkthis box!
We’re also pleased to note that all features in PhoneGap 1.3 are now supported for Windows Phone, as you can see on their site here.
Also, beyond the core PhoneGap features, developers can enjoy a selection of PhoneGap plugins that support social networks - including Facebook, LinkedIn, Windows Live and Twitter - and a solid integration into Visual Studio Express for Windows Phone.
We have also developed further plugins to give HTML5 developers a feel for Windows Phone’s unique features like Live Tile Update and Bing Maps Search.
Please check out Jesse MacFadyen’s blog, PhoneGap’s dev lead, on his experiences developing PhoneGap on Windows Phone.
For more technical details of using the framework, see Glen's and Jesse’s technical walk thru blogs. For a quick a spin of what PhoneGap and Visual Studio allow you to do, see this WP7 and Android camera app created in 3 minutes! Phonegap bits are located here; plugins are here.
As mentioned in PhoneGap’s announcement blog post, the next PhoneGap 1.4 release will be from the Cordova incubation project at Apache. We at Microsoft are proud to be members of this project and to offer technical resources. We welcome the involvement of Adobe, IBM and RIM and look forward to collaboratively growing PhoneGap at its new home in Apache while helping evolve an open web for any device.
Microsoft’s commitment to HTML5 in IE9 has been instrumental in achieving this level of support. We are also building on our HTML5 investment through initiatives like bringing jQuery Mobile support as we outlined few weeks ago. Partnering with open source communities to bring this level of openness continues to be an important goal here at Microsoft.
So, stay tuned for more news on our support for popular mobile open source frameworks on WP7.5!
Abu Obeida Bakhach
Interoperability Strategy Program Manager
by billhilf on May 18, 2007 09:22pm
It’s been an interesting week, with people offering a range of opinions about what they think is happening in Redmond. Despite a lot of pontification, our strategy regarding intellectual property and open source has not changed – and it is not frivolous litigation or fear.
IDG did an article – it’s a far more accurate reflection of Microsoft’s IP strategy than the Fortune article from earlier this week. Andy Updegrove also has a thoughtful article on his site, and Gartner’s lead open source analysts have been clear to customers: “don’t panic.” Our strategy remains the same:
Microsoft was created by developers, for developers and is only successful through developers and customers. Developers who write Open Source software are participating in a worldwide community of practice and a spirit of collaboration. These are noble characteristics and Microsoft both applauds and supports this work.
We continue to champion projects like JBoss, Zend (PHP), and SugarCRM, as well as Firefox, openwsman, Bandit and thousands of others. We are building relationships and a track record here and we ask that you judge us on these actions. We will work with commercial and non-commercial developers to increase the availability and quality of open source on Windows and interoperability with Windows.
Our IP strategy has not changed. Where we have unique and valuable intellectual property (as indicated by our high scores on the science strength of our patents) we will seek to license it to commercial entities (such as Samsung and Fuji Xerox).
It’s not us versus the free world. It’s about commercial companies working together around IP issues – it’s business as usual.
- Bill Hilf and Sam Ramji
by MichaelF on May 24, 2007 06:15pm
It's happened to me and I'm sure it has happened to you: your software won't load and your data is now trapped inside your PC. The problem may be a hardware or a software failure, and the problem may seem to be irrecoverable. Yet often Linux can be used to help recover data that otherwise might be lost. This paper describes how one can use Linux to recover data from a non-functioning Windows machine.
I’m really excited to be able to give you an update on our strategy and product roadmap for Big Data, especially around our embrace of Apache Hadoop as part of our data platform.
As you may remember, at the PASS Summit last October we laid out our roadmap for Big Data, with Microsoft Corporate Vice President Ted Kummert announcing plans to deliver enterprise class Apache Hadoop based distributions on both Windows Server and Windows Azure.
Even more importantly, he announced that Microsoft will be working with the community to offer contributions for inclusion into the Apache Hadoop project and its ecosystem of tools and technologies.
Now, this week at the O’Reilly Strata Conference, Dave Campbell, a Microsoft Technical Fellow, will give a keynote address on Wednesday morning where he will talk about how we are demonstrating our progress on this front as we strive to help organizations derive new insights from Big Data.
In a blog post today, Campbell notes that Microsoft has been working hard to bring the simplicity and manageability of Windows to Hadoop based solutions, and we are expanding the reach with a Hadoop based service on Windows Azure.
“Hadoop is a great tool but, to fully realize the vision of the modern data platform, we also need a marketplace to search, share and use 1st and 3rd party data and services. And, to bring the power to everyone in the business, we need to connect the new big data ecosystem to business intelligence tools like PowerPivot and Power View,” he says.
Microsoft is working closely with the community and ecosystem – including partners such as Karmasphere, Datameer and HStreaming – to deliver an open and flexible platform that is compatible with Hadoop and works well with leading 3rd party tools and technologies.
As Gianugo Rabellino, Microsoft’s Senior Director for Open Source Communities said last October, these moves benefit not only the broader Open Source community by enabling them to take their existing skill sets and assets use them on Windows Azure and Windows Server, but also developers, our customers and partners.
“It is also another example of our ongoing commitment to providing Interoperability, compatibility and flexibility,” he said at that time.
You can read Campbell’s blog here and learn more about what we are doing for Big Data here.
by Peter Galli on November 02, 2009 03:01pm
This week the Apache Software Foundation celebrates its 10th anniversary at its annual U.S. ApacheCon 2009 event in Oakland. As such, I though it would be interesting to chat with ASF President Justin Erenkrantz about the past 10 years and what's still to come going forward.
Peter Galli: Tell me about ApacheCon, who the audience is, what the goal of the event is.
Justin Erenkrantz: Since The Apache Software Foundation (ASF) is so globally distributed, with almost 2,000 Committers around the world working on over 100 different projects, we do all of our work virtually, via public mailing lists.
As such, ApacheCon presents a unique opportunity for our community - users, contributors, and developers - to get together face-to-face. We typically try to run at least two shows a year: we're currently holding our upcoming U.S. show in Oakland, and we held ApacheCon Europe in Amsterdam earlier this year.
At ApacheCon, we have a range of trainings, talks, and MeetUps. We have half-day, full-day, and two-day trainings typically led by key developers in the project. This immersive environment allows interested parties to dive down into tremendous detail about Apache projects - popular trainings include Hadoop, Solr, Tomcat, ActiveMQ, Wicket, Lucene and, of course, our well-known HTTP Server.
In addition to the trainings, we have three days of session tracks (usually hour-long talks) covering broad topics such as: Content Technology (content management systems including Sling and Jackrabbit, as well as CouchDB and POI), Web Services (Axis and other SOA tools), OFBiz (our Enterprise Resource Planning solution), Tomcat (our popular Java servlet engine...well it does much more than that these days!), Felix (our implementation of the OSGi framework) and, of course, some talks about the HTTP Server.
One thing that we're really excited about this year is our expansion of free MeetUps in the evening. These are a great opportunity to mingle with the community in a very low-key unstructured environment focused on a single topic. You can think of a MeetUp as an all-night "birds of a feather" (BOF) sessions. In addition, we will be holding BarCamp Apache -- our two day un-conference to talk about whatever folks are interested in, as well as the Hackathon, where participants can collaborate on various code bases alongside Apache Committers. The great thing about the MeetUps, BarCamp, and Hackathon is that they're open to the public, free of charge. All are welcome!
Peter Galli: You always hear a lot about the "Apache Way." Explain this to me.
Justin Erenkrantz: As an all volunteer, non-profit organization, the ASF is regularly praised for its consistent, repeatable, open development model. This model, affectionately dubbed by some as "the Apache Way", is behind the ASF's success in scaling from a single project to 70 primary projects today.
One of our biggest challenges, as the ASF has grown to nearly 2,000 Committers, is how to teach the Apache Way to those interested in bringing new Open Source projects to the Foundation. The way to address this on a formal level is through the Apache Incubator, created to "mentor" new projects and to assist in their learning how to operate as an ASF project. ASF Members who find the candidate technology (called a "podling") worth pursuing, they can then volunteer to be a mentor to the project.
Rather than overseeing its technical development, the mentor's main responsibility to a podling is more social, by helping to pass down the traditions and culture of other projects. Over time, once the podling has demonstrated that it has learned the Apache Way and can govern itself successfully, it can become a full-fledged ASF project and graduate to a top-level project.
Anyone can submit a podling proposal to the Incubator for consideration as a new ASF project. If you have an existing Open Source project and would like to join the ASF, we encourage you to check out the Incubator, and submit your proposals to email@example.com.
Peter Galli: Microsoft has been working closely with the Apache Community for some time now. Can you talk to how that works and why our participation is important?
Justin Erenkrantz: As you know, last year Microsoft announced its Platinum Sponsorship of the ASF, which it continued this year. While we are delighted to have Microsoft's financial support as a sponsor of the Foundation, I think the more important aspect of Microsoft's relationship is that they are now contributing to a variety of Apache projects.
Since we announced the sponsorship last year, Microsoft is now contributing to at least four Apache projects: HBase, Stonehenge, QPid, and POI. This really continues the significant sea change from within the organization - Microsoft now isn't afraid of having their employees contribute to Apache projects on Microsoft's time. Committers from Microsoft sign the same legal agreements that we require from all of our contributors.
Microsoft's involvement in these specific communities range from having their employees being core contributors driving the project, to having folks contributing patches or ideas on our mailing lists, to even commissioning a third-party to contribute to our project as a work-for-hire. In other words, Microsoft is now actively participating within Apache projects in a broad range of ways.
In recent conversations with the Port25 team at Microsoft, it sounds like there are even more Apache projects that Microsoft is interested in getting involved in. We look forward to Microsoft's continued and increased contribution and participation within Apache.
As a public charity, we rely on donations from the public. Our policy is not to provide direct funding for our projects (we do not pay for contributions to any of our projects), however there are a number of indirect needs to support our projects. The biggest chunk of our budget goes towards maintaining our servers - we maintain SCM systems (currently Subversion-based), mirror distribution system (seeding a large number of volunteer mirrors), build farms, Web sites, and mailing lists.
We have key data centers at Oregon State University's Open Source Lab and SURFnet in the Netherlands. Since we have a growing number of contributors in the Pacific Rim, we're looking to expand our server presence in those regions. Through our Travel Assistance Committee, we also use our funds to help community members (typically college students) who could not otherwise attend our events - this has been a fantastically successful project in helping to encourage further participation. Finally, we also use some of funds to help spread our message - so many folks still think that the ASF is just about the HTTP Server - it's not! It's only 1 of 70 different top-level projects - so we realize we still have to do some education on that front!
Peter Galli: What are some of the most exciting projects that have been developed by the Apache community, or are currently being worked on?
Justin Erenkrantz: There are so many exciting projects that it's hard to choose from! As before, some folks think that the ASF is just about the HTTP Server: we have projects ranging from Atom/RSS parsers/producers (Abdera) to generating high-quality printable graphics via XML (XMLGraphics). Some folks don't often connect the dots and realize that projects like CouchDB, SpamAssassin, and Hadoop are all Apache projects. And, it's important to know that via our Incubator and Labs projects that we're open to shepherding even more projects.
As we celebrate our tenth anniversary, we've established ourselves as an important player in the ecosystem. We were founded on pragmatic principles, but that hasn't meant that we shouldn't have a leadership position: our Apache License version 2 is the flag-bearer for permissive Open-Source licenses and we have been a strong advocate for openness and transparency within the Java standards process. Over the next ten years, it'll be an exciting ride!
We should also point out eWeek's recent story on eleven Apache technologies that have changed computing in the last 10 years.
Peter Galli: What do you hope to see coming from the community over the next years?
Justin Erenkrantz: Our purpose in founding the ASF ten years ago was to bring the "Apache Way" to a broader community than just the initial HTTP Server. Our goal is to continue that process: we realize that developers are best at coding and shouldn't have to worry about the gnarly details - be it setting up servers, distributing files, accepting donations, handling legalese, organizing events, etc. - and just focus on creating terrific code. So, we hope to see more ideas for projects come our way through our Incubator and Labs!
Today, at BSDCan 2012, Microsoft and partners NetApp and Citrix announced upcoming native support for FreeBSD support on Windows Server Hyper-V.
This move continues our commitment to extend support across platforms to the Windows Server Hyper-V solution, making it easier for more customers to realize the benefits of server virtualization and more easily adopt cloud computing.
This will allow FreeBSD to run as a first-class guest on Windows Server Hyper-V. The drivers and associated source code will be released early this summer under the BSD license, and will initially work with FreeBSD 8.2 and 8.3 on Windows Server 2008 R2.
You can read more about this on the Openness blog.
Joe CaraDonna, the Technical Director of Core Operating Systems at NetApp, says in an interview that he was thrilled to have had the opportunity to work with Microsoft and Citrix to deliver Windows Server Hyper-V support to FreeBSD.
“I think the combination of these virtualization technologies helps round-out the FreeBSD virtualization story, and makes the FreeBSD operating system a more compelling offering.”
He also notes how committed Microsoft is to open source initiatives: “we decided from the very beginning that we were going to open source the code under the BSD license. No strings attached. They were as eager as us to support the project, and then give the code away. How cool is that?”
You can read the full interview here.
by Sandy Gupta on September 29, 2009 06:15am
Microsoft recently made a significant code drop to the Apache Qpid project. For those of you who don't know, Qpid is Apache's implementation of the Advanced Message Queuing Protocol (aka AMQP), which is an exciting new reliable messaging protocol developed by some of the world's biggest messaging users (think names like JPMorgan Chase).
What we've done is a Windows Communication Foundation (WCF) Channel for AMQP. Our goal is to provide a first class AMQP experience for the .NET developer. And, since this is an Apache project we're talking about, all our code is obviously open source.
A couple of years ago the announcement of Microsoft making a major contribution to an open source project would have been sensational news, but things have moved on a little bit since then. Now it's just another day's work at Microsoft.
As the manager of this effort at Microsoft, I'd like to talk a little about what we bring to the open source table. We joined the Apache Qpid project, which was essentially focused on Linux, to help the community develop a port on Windows and integration with the .NET stack.
That was reflected both in the code itself and also in the build environment it used (autotools). One of the areas where we invested was the introduction of a cross-platform build and test environment (CMake), so as to smooth the way for cross-platform work.
We have continued to adopt our typical product development quality assurance mechanisms when working with open-source. These include team-based design and code reviews. We also use automated code-quality tools, such as StyleCop, to ensure consistent style and to detect common programming errors.
We developed the initial version of the WCF Channel on a private Subversion repository and used a private bug database for logging issues and work items. Now we have made the initial drop to the community, we intend to do all revisions in the Apache repository and switch to using the community Jira-based bug tracking system.
Today we have a group of 5 engineers working with Qpid, both vendors and full-time Microsoft employees. Over time, it's our goal for many of these folks to achieve committer status on the project.To date, we've worked on the following work items:
For me, leading AMQP initiative at Microsoft has been quite a learning experience. Our collaboration with the community has been strong and we have received full support from our executives.
Here at Microsoft we understand that AMQP can become the SMTP for Messaging. This means AMQP is going to have a huge beneficial impact on all kinds of users in the years to come, and we want to help make that happen.
Helping develop the open source AMQP reference implementation at Apache Qpid as part of a broad community effort is our way of moving the AMQP ball forward. I'll have a lot more news to report about our efforts in the months to come.