Advocacy and Outreach

The special interest groups coordinates various outreach programs which help the project to facilitate contributions and to onboard more contributors. For a list of our on-going and planned programs, see the Outreach programs page.

Our SIG manages the Jenkins Online Meetup platform and helps to organize events on this platform. It includes user-focused and contributor-focused events. See the linked page for more information.

Our SIG is interested to help with organizing and promoting local events which focus on Jenkins or have a substantial representation of Jenkins in their agenda. These meetups are not limited to Jenkins Area Meetups or CI/CD Meetups, we are interested to help any other meetup group or entities organizing local meetups and conferences related to Jenkins.

The SIG does not manage meetup operations (creating new meetups, delivering swag, etc.), but we are ready to help to find proper channels if needed. This page summarizes the current state of meetup operations.

Our SIG coordinates Jenkins promotion in social media and other channels, including but not limited Twitter, YouTube and LinkedIn. If you would like to share any content about Jenkins on these platforms, please contact us, and we will try to help.

Channels within our scope:

The SIG coordinates adoption of inclusive naming in Jenkins, including the cleanup of former non-inclusive terms and growing awareness among end users and content creators. In 2016, the Jenkins community decided to change the non-inclusive terminology within the project. The “slave” term was deprecated and replaced by “agent” in Jenkins 2.0. In July 2020 we also adopted the “controller” term instead of “master”, and deprecated the “whitelist/blacklist” terms.

There are many places where the old terminology still needs to be replaced. We invite Jenkins contributors and end users to join us and participate in cleaning up our documentation, Web and CLI interfaces, localizations, codebase, and all other occurrences. We want to replace the deprecated terminology by new terms: “controller”, “agent”, “allowlist”, “denylist”, and “main” for branch names. We also encourage everyone to spread the word about new terminology inside their companies and communities, and to reach out to content creators to facilitate cleanup of old terminology.

References: