The move of enterprise and cloud-native specifications and technologies to the Eclipse Foundation under the Jakarta brand brings along with it the need to define a process for creating and evolving code-first specifications in open source. While specifications manifest as a collection of artifacts (a specification is a collection of APIs, descriptions of semantic behavior, data formats, and/or protocols intended to enable the development of independent compatible implementations), it's not quite as simple as dropping them into our existing Eclipse Development Process (EDP).
There are a lot of people out there, and at the conference — who are fairly new to the Eclipse community and projects. This is your chance to tell them about your project and introduce new members into your community. Explain why it is a good idea to go to the Eclipse Foundation with your open source project; How to set up a project, or even why make it open source; Why legal issues matter; What it means to be a committer, how you handle Graduation Reviews and Release Reviews and how to organize an Eclipse project. If you’ve founded a new Eclipse Working Group or plan to do so — please share your ideas and plans with the community.
As more Eclipse projects are migrated to the new cluster based build infrastructure, it's time for an update on the current status and to share best practices how projects can make the most of it. The following questions (and more) will be answered: Why does my build take so long and how can it be made faster? What are Jenkins pipelines and why/when should they be used? Can I finally run docker based builds?
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.
The Eclipse infrastructure is undergoing a massive overhaul, modernizing every* aspect from builds, to websites, our data and API, networking and virtualization. New tools and technologies are cropping up in our datacenter, including Kubernetes, Docker, 10GbE, nginx, and new developments with Gerrit and even our home-brewed Drupal-based codebase.
All the Eclipse projects progress thanks to their contributors, and without these contributions the Eclipse eco system would die. For several years, the Eclipse foundation has provided a modern and efficient software factory usable by anyone who want to be involved in any project.
This talk will give you an overview and all the entry points of this professional contribution system so as to be involved easily and make Eclipse everyday better.
Traditionally, a great deal of importance is placed on the value of technical contributions to a project. However, an oft-overlooked aspect of open source development is the community itself, as well as the ability of a project to attract (and maintain) a wide variety of contributors.
This talk will focus on the importance of growing new contributors using real-life lessons, and examples encountered in SWT.
It will begin with non-technical aspects of community management, namely: