Knowing your way in open source has become increasingly important and these skills are considered essential by many today. Topics range from understanding the various licenses to building a thriving and diverse community around projects. How can you as a company or individual leverage your participation in the Eclipse community and become involved in contributing to software that forms the foundation of the modern world? This track is for you whether you are a beginner or an expert.
Many Eclipse projects chose to host their source code on GitHub. GitHub's blend of quick forks, pull requests, and easy communication certainly has benefits for communities, collaboration, and ultimately: contributions.
Before a person can contribute, however, they need to go through the tedious work of git-clone, install and configure the right tools and services, and compile. It can take several minutes to hours. It can make people say: "Contribute? Oh well, not today".
What if we could reduce this to one click of a hyperlink and 5 seconds?
The Eclipse Foundation’s IP Policy and procedures date back to 2004. Our policies and processes have gradually evolved over time; however, our current due diligence review process for third-party dependencies no longer supports agile development or continuous delivery. Additionally, it is becoming impossible to scale our current processes to modern day technologies such as Node.JS, NPM, etc.
Yes, you've read that right.
The Eclipse infrastructure is undergoing a massive overhaul, modernizing every* aspect from builds, to websites, our data and API, networking and virtualization. We're looking at the technological landscape and we're wondering why we're still doing some things the way we do. Also, we're recognizing the great value the Eclipse infra provides, and we're looking at ways of providing even more of it.
Join us in discussing where our server infra has been, what it does today, and where we want to be in 2022.
* Including Bugzilla
Many open source projects struggle to build a community of both contributors and adopters of their open source technologies. The good news is the Webdev + Marketing team from the Eclipse Foundation have prepared a list of best practices and things you can do to both help promote your open source initiatives and grow your technological presence.
In the past 20 years, software has become increasingly important for the successful operation of any kind of business. This trend is expected to continue in the future. At the same time, the amount of open source technologies used in the software industry has increased rapidly.
While closed software development can be considered daily business, active participation in open source communities still poses quite some challenges for companies coming from more traditional industry sectors like automotive and manufacturing.
Eclipse is a great platform for developing your own applications. However, once you want to share these applications with the community it becomes a bit trickier. Recently, we decided to bring our own project - “Virtual Satellite” - into the open source community of GitHub. Pushing the code to a repository is the first step. The next steps consider, continues integration, deployment, sharing of artefacts, maintaining code quality, etc. In this talk we present our architecture for an open source eclipse RCP application.
Ensuring Open Source compliance is a necessary step for organizations building software based products today. The usage of 3rd party components needs to be identified, metadata has to be retrieved in order to fulfill license obligations. Eclipse SW360 and SW360antenna allow to automate this process reducing the effort of project teams to ensure license compliance for the built product.
The Eclipse Development Process is based on some very principles that are considered key for successful open source: openness, transparency, first-class intellectual property management, and vendor neutrality. Over many years, we've developed practices and processes to support these concepts. While most of these practices and processes are captured in the Eclipse Committer Handbook, keeping track of it all can be a challenge.
Running an open source project is easy. All you have to do is make your source code available and you’re open source, right? Well, maybe. Ultimately, whether or not an open source project is successful depends on your definition of success. Regardless of your definition, creating an open source project can be a lot of work. If you have goals regarding adoption, for example, then you need to be prepared to invest. While open source software is “free as in beer”, it’s not really free: time and energy are valuable resources and these valuable resources need to be invested in the project.
An Open-source Product Testing Makeover
Here we intend to share a story of our evolution which made our product testing in opensource more adoptable, less complex with reduced cost and turnaround time.
In-house Vs opensource product
When products move from in-house to open, the challenges associated with testing such products are less predictable. An in-house product has mostly a known set of customers with a specific pattern of usage which helps the product team design the various testing scenarios.