A few weeks ago, Andrew called me into his office, and told me “I’m sure you’ve figured this out already, but I’m transgender.” To which I replied “Uhhh….I had no idea. ” I am so oddly oblivious to these sorts of things, it’s sad.
Today Andrew becomes Andrea.
What I know already is that Andrea retains all of the attributes that made me want to work with Andrew. She is a warm, and funny person who cares deeply about the technologies, communities, and people she works with. She is committed to her family and local community. We are lucky to have her at the Eclipse Foundation, and as part of the Eclipse, Eclipse Science, and LocationTech communities. She is on a very courageous journey of personal discovery, and to a small degree, we’re along for the ride.
Andrea is at once both an old and a new member of the Eclipse community. Please give her a warm welcome.
Last month I announced that the Eclipse Foundation is going to begin using personal and corporate donations to fund Eclipse platform development. Of course, the devil is in the details, and as an open source community we need to define an open and transparent process for how work is prioritized, and funds are allocated. Today, we are publicizing a draft document that lays out such a process.
One thing that we know is that the process can seem sort of heavyweight when you first read it. Be assured that we will be putting together some open-ended work packages to ensure that it remains lightweight and agile as possible.
We are looking forward to your feedback!
The news this morning that JetBrains is switching to a subscription-only model is a perfect example of why and how trusting a proprietary tools vendor leaves you and your business exposed to the whims of their profit margins. Make no mistake: this is motivated by what’s good for their business, not what is good for the developer community. Even if JetBrains backpedals on this decision, it is a lesson worth learning.
Eclipse is the only truly community-based tooling platform. We are 100% open source from top to bottom. There is no “Community Edition”. It’s all open source. We are not beholden to any vendor’s agenda.
We are well aware that IntelliJ is a great product. We are also aware that Eclipse has not been moving forward as quickly as we would have liked this last few years. But we are actively working to change things, and you — the developer community — can help. First of all, the Eclipse platform is now a truly open and community-driven project. Your time and code contributions will be welcomed. Also, we recently announced that 100% of all personal donations will be directed to funding Eclipse enhancements. So you can help in your personal capacity by donating even a fraction of JetBrain’s subscription fees to Eclipse. Just as importantly, we will take directed corporate donations to fund Eclipse enhancements as well. Is there a couple of missing features that is slowing down your company’s use of Eclipse? We can fix those for a fraction of what JetBrains wants to extract from your employer.
Eclipse is a true free and open source software community, focused on the needs of developers everywhere. Let’s use this opportunity to re-invest in it so that it is the tool that you want to use every day. For free. Now and forever.
Today, we are significantly lowering the barriers for companies and individuals to actively invest in the ongoing development of the Eclipse platform. Eclipse has an amazing community of individuals and companies that invest significant amount of resources in the development of Eclipse open source projects. We also have a huge community of users that benefit from Eclipse technology. They use Eclipse tools and technology to build their software products and applications. Most of these users don’t have the time required to participate in an open source project but they do want to see ongoing improvements and investment in Eclipse. We now have a way for these users to invest in Eclipse improvements.
We are pleased to announce the Eclipse Foundation has begun to fund development work on Eclipse projects. In fact, there are a number of features and issues in the Mars release that were funded through the Foundation. The initial focus is on improving the core Eclipse platform, JDT and Web Tools. As the program expands we expect the list of projects will grow too. The process by which funds will be allocated is still a work in progress, but will be made available soon. It will be based on the core principles of openness and transparency.
The funding for the development work will come from individuals and corporate users. Earlier this year, Ericsson provided the Eclipse Foundation funds to improve the Eclipse platform which resulted in SWT, GTK3 and PDE improvements available in the Mars release. Ericsson is a large user of Eclipse and they see the value of investing in ongoing improvements. We hope other large corporate users of Eclipse will follow Ericsson’s lead.
We are also pleased to announce that all users’ donations to our Friends of Eclipse program will be used to fund Eclipse development work. Last year we raised over $120,000 from the Friends of Eclipse program, so we hope the ability to directly fund Eclipse development will significantly increase the donations we gain from our individual user community. To make things even easier, we have added Bitcoin as a payment option. Please take this opportunity to help improve Eclipse by making a donation.
Eclipse open source development will continue to move forward through work of our committer community. Committers are the heart and soul of any open source project. However, we are confident having additional investment from our user community will help accelerate future improvement to Eclipse. If you are a user of Eclipse, individual or corporate, it is now simple to participate in the future of Eclipse.
Several weeks ago, the Git community announced a new 2.2.1 release which fixed a serious security vulnerability. You can read more here and here. The Eclipse JGit project had their fix available the day that the vulnerability was announced. However, since the vast majority of Eclipse users get their Eclipse via the packages, the decision was made to make new versions of those available as well. I am happy to announce that as of 10:00am Eastern this morning, those new packages are now available for download from Eclipse.
This is the first time the Eclipse community has done a re-spin of our current release for a security issue. Congratulations and thank yous are due to many people, but in particular the JGit project, the webmaster team, and to David Williams and Markus Knauer for all the hard work necessary to make this happen.
Eclipse users who use Git or GitHub through their Eclipse Workbench should either download the new package, or use “Help > Check for Updates” to update their existing installation.
This post was originally published on the Bosch Connected World Blog.
The Internet of Things is poised to become the next wave of technology to fundamentally change how humanity works, plays, and interacts with their environment. It is expected to transform everything from manufacturing to care for the elderly. The internet itself has — in twenty short years — dramatically transformed society. This scale of change and progress is about to be repeated, in perhaps even larger and more rapid ways. New ventures will emerge, existing businesses will be disrupted, and everywhere the incumbents will be challenged with new technologies, processes, and insight.
It is important to recognize that the internet is successful because it is one of the most radically open technology platforms in history. The fundamental protocols of the internet were invented in the 1970’s, and put in the public domain in the late 1980’s. The world-wide web was invented at the European Organization for Nuclear Research (CERN), which made it free for everyone. In subsequent years, open source technologies such as Linux, the Apache web server and the Netscape / Firefox browser ensured that the basic infrastructure for the web is based on open source. The technology behemoths of our day such as Google, Amazon, Facebook and Twitter are only able to scale their infrastructure and their business models by relying on open source. In short: our modern digital world is built on open source software.
The Internet of Things will be implemented using open source software platforms. There is utterly no alternative to this outcome. Anyone who says otherwise is fooling themselves.
There are four reasons why this is true.
- Scale: Depending on which analyst you prefer, the next decade will see between 50 and 70 billion sensors being deployed on Earth. This will require tens, if not hundreds of millions of routers, gateways, and data servers. There is simply no way to achieve those levels of scale without relying on open source software to drive the vast majority of that infrastructure. Any other approach will simply be unaffordable, and will be out-competed by the economies of scale achievable by the open source alternatives.
- Freedom to Innovate: Open source software allows permission-less innovation. In particular, open source allows innovation by integration, where developers create new and novel systems by combining freely available open source components. This approach is somewhere between difficult and impossible for proprietary software stacks, where the vendor has to drive all of the invention.
- Inter-operability: I am a big believer in open standards, and firmly believe that they will be an integral part of the IoT. However, it has been proven time and again that the best possible way to have a new technology achieve rapid adoption is by combining open standards with a robust open source implementation. OSS implementations provide an easy adoption path, near-perfect interoperability with others, and reduces the cost of entering the market. In a world where developers are becoming one of the most precious of commodities, it makes no sense to waste them on implementing a standard. They should be focused on building software which provides the firm with product differentiating features that customers value.
- Developers: Lastly, recruiting and enabling developers is a key, and often overlooked part of any IoT strategy. By the end of this decade the number of IoT developers needs to grow from a few hundred thousand to over four million. Today’s developers demand open source solutions and tools. Even a decade ago, technology acquisition was largely a top-down process. Now technology choices are largely made bottom-up, by developers experimenting with open source components and integrating them into a solution.
For these reasons, IoT is rapidly becoming a strategic area of focus for the Eclipse community. From three projects two years ago the Eclipse IoT community has grown to seventeen projects, implementing protocols, device gateway frameworks, vertical frameworks, and tools for the needs of IoT developers.
Bosch has been an active member of the Eclipse Foundation since March 2010. Their initial focus was on the Automotive Working Group, which has been working on tools and methods for automotive embedded systems. Its subsidiary Bosch Software Innovations (BoschSI) is one of the world’s thought leaders in driving open source platforms for the Internet of Things. They have recognized its importance, and with contributions such as the Eclipse Vorto project are helping to make it a reality. The Eclipse Foundation values the partnership that we have with the development teams, and look forward to a long and fruitful collaboration.
The digital world we have today is built on open source technologies. The Internet of Things will be too. Come join the Eclipse IoT community to help make that happen
This morning, the Eclipse Foundation announced a new industry initiative focused on building tooling platforms for the cloud. The team prepared an FAQ, but I thought it might be helpful to publish it here as well.
What is being announced?
Eclipse is announcing the formation of a new Top Level Project, “Eclipse Cloud Development” to create the technologies, platforms, and tools necessary to enable the delivery of highly integrated cloud development and cloud developer environments. The ECD charter is available here. This TLP initially combines Eclipse Orion, Eclipse Che, and Eclipse Flux with SAP signaling that Dirigible will become part of the initiative. The Eclipse board of directors voted to approve this new project on September 17th, 2014, and a new project management committee has been formed. Additionally, Codenvy is announcing the creation of project Che, which contains their IP that makes up the Codenvy SDK, Codenvy IDE, and 50 plug-ins that provide programming language, source code control, deployment, and build / debugger support for cloud development. Codenvy will be contributing 30 full time resources to the ongoing development of Eclipse projects, the development of the community around cloud development, and the promotion of the Ecosystem that makes up the ECD. Codenvy has become a strategic developer member of Eclipse, and taken a board of directors seat with the foundation.
Why is Eclipse creating a top level project dedicated to cloud development?
There are over 22 million professional developers, and more than 99% of all development is still done on the desktop. The cloud has proven benefits to eliminate configuration overhead and improve visibility and control for organizations. The transition to cloud development away from the desktop has begun. Over the past 5 years, there have been 100s of global initiatives to work on development tools or underlying infrastructure necessary to enable development entirely in the cloud. With three projects at Eclipse already working on cloud development, and more coming soon, the time has come to focus the industry’s efforts on enabling this transition. By creating a Top Level Project, the combined projects are better able to concentrate their resources, more easily align on technological and market objectives, and create a streamlined path for onboarding additional ecosystem projects, developers, and committers to cloud development.
Which projects will be part of the Cloud Development Platform top level project?
What is the Che project?
You can read the Eclipse Che project proposal here.
What is the difference between Orion and Che?
Orion & Che:
- Provide a runtime for hosting, managing and scaling developer environments as Web apps.
- Provide an SDK for packaging, loading, and running tooling plug-ins.
- Provide a default set of plug-ins related to programming languages, source code, deployment, and other elements that are part of the developer workflow.
- Provide a default cloud IDE that combines a set of plug-ins, the SDK, and runtime together to offer a hosted developer experience.
- Have ways (or plans for ways) to connect desktop IDEs (like Eclipse and IntelliJ) directly into the hosted services
What is Dirigible and how does that relate to Che and Orion?
Dirigible extends the concepts promoted by Orion and Che to deliver on a rapid application development framework, fully hosted in the cloud. Dirigible abstractions make developing Web services and the clients that consume them structured with scaffolding, rapid, and easier to maintain. Rapid development frameworks have commonly been deployed to support database and packaged application development, and Dirigible brings those concepts to cloud developer environments. All three projects provide hosted developer environments. But our commonality and agreement on a common vision means that there will be nice reuse and alignment between the projects. All of the projects agree on core principles relating to providing developer services as atomic microservices, decoupling the clients (IDEs) that consume those services from the services themselves, supporting a broad range of clients (whether our browser IDEs or desktop IDEs connected over a bus), and providing a consistent way to provision, share and scale hosted developer environments together.
When should a developer user choose Orion and when should they choose Che?
How will Orion, Che, Flux, and Dirigible collaborate together?
We have identified a number of initiatives that the projects will align on. These include: Finding ways to have Che and Orion plug-ins work within each other’s systems. Standardizing on the synchronous REST API model that allows browser clients to communicate with server-side systems. A sample set of APIs can be seen at docs.codenvy.com. Using Flux to standardize on the asynchronous communication model between various cloud systems, along with enabling browser and desktop clients to have decoupled access to cloud systems. Collaborating on a model that allows for on-demand, authentication-less environment creation through URLs, similar to the effects seen by Codenvy Factory, as documented at docs.codenvy.com/user. Temporary environments will be possible to be generated on any system supporting the format. Align on common underlying enterprise infrastructure, that will seamlessly take a single server cloud IDE package, and allow it to be deployed within an enterprise system that provides multi-tenancy, elasticity, and security. Incorporate the Dirigible configurate-stored-as-a-model approach to create an abstraction to support a variety of rapid development approaches and frameworks.
What is the future of cloud development, and your roadmap here?
Cloud development’s benefits are significant to individual developers, development teams, and enterprise organizations. There are huge configuration taxes that exist today due to environment creation, environmental technical debt, environmental tribal knowledge, hardware interoperability issues, and the general interoperability issues that exist between making an ecosystem of tools and plug-ins work together. All of these problems can be dramatically reduced with a cloud development platform that automates the full lifecycle of developer environment and its supported tooling. To achieve this vision, much more than a cloud IDE is required. A cloud development platform (CDP) takes a cloud IDE and turns it into an orchestration system for developer environments. The power of the CDP is that it can automate many of the workflows that make up the tasks carried out by developers, QA, product managers, documentation specialists, and devops professionals. Why should each developer only have a single developer environment that lives indefinitely (statically) on their desktop, when – with full automation – every developer and system can have a unique developer environment for each task they carry out during the day? Whether it’s fixing a bug, investigating a legacy branch, working on a new feature, or exploring a new technology library, a cloud development platform can auto-provision a specialized environment for each task, on-demand, with no downloads or configuration required by the developer. The CDP can then provide numerous services to make the developer’s workflow shorter and less error prone. These include advanced editors, dependency analysis, automated unit testing, debugging, building, packaging, and source code management integration. The CDP can take these operations at scale, and make them run faster than they would normally run on an individual desktop, but also require less hardware for a large organization than performing these functions on desktops since the cloud can be operated on a dense hardware cluster. Finally, with development centralized, devops and development leaders, can better support the development of a population of developers by incorporating best practices, behavioral access controls, and monitoring tools to ensure IP compliance and maximum productivity of individuals. Imagine being able to direct an extra 20GB of RAM to a developer that urgently needs it for compilation, or creating a special set of sand boxes to support white room development of secure IP, or allowing an instructor to create a programming exam accessible to his students for exactly one hour with controls to detect any plagiarism or cheating. With a CDP, all of these scenarios are configurable, simply. Net, net: Faster development. Cheaper development. Development done with compliance and security. Our roadmap to support this vision includes: Advancing each TLP project through their normal roadmap and evolution processes. Recruiting new projects that provide critical developer services in the cloud into the ECD TLP. Aligning core plug-in, editor, and API / interface models between the projects. There will be combined ecosystem, evangelism, and business development efforts to bring more developers, projects, and plug-ins to ECD model including special efforts and attention to migrating existing Eclipse plug-ins. Codenvy will create an additional project that focuses on the enterprise scale elements of a ECD, and Flux / Orion / Che will work to standardize deployment of each system within the enterprise infrastructure. An effort to study how analytics, events, and the BI of development workflows will be created.
Why is Codenvy donating their core IP?
Codenvy believes in openness, transparency, ecosystem, and Eclipse. The cloud development problem is massive and cannot be solved individually. By working with the Eclipse foundation, Codenvy is able to concentrate their resources with others that have a similar value system and vision.
When will the Che code be available? For which “parts” of the platform?
The initial Che code is available under EPL at github.com/codenvy/sdk. We are working within the Eclipse process to get through Incubation now.
What kinds of products, applications can we expect to see as a result of this collaboration?
You can expect to see new IDEs, new plug-ins, new enterprise technologies to support executing these systems at scale, and you can expect to see integration bridges that bind ECD into other core development platforms like Jenkins and Jira.
How can I contribute to and participate in the Che project?
Get started by cloning the source and getting active at Eclipse. https://github.com/codenvy/sdk