LinkedIn post draft, referencing the CDF blogpost. CC @tracymiranda @MarkEWaite . I can also fit in one of the quotes into the text. Maybe the KK's quote or one from users?
_We are happy to announce that the Jenkins project has achieved the graduated status in the Continuous Delivery Foundation (CDF). Jenkins is the first project to graduate in the foundation.
To move from the maturity level of incubation to graduation, a project needs to demonstrate growing adoption, an open governance process, feature maturity, and a strong commitment to community, sustainability, and inclusivity. Jenkins has met all of these criteria. Thanks to all contributors who made our graduation possible!_
#jenkins #cdf #graduation #community #foundation
And the LinkedIn one:
An new Dark Theme is now available for Jenkins 2.239 and above! Also, we are happy to introduce a new Theme Manager Plugin. Check out the announcement by Tim Jacomb: https://cd.foundation/blog/2020/08/04/introducing-the-jenkins-dark-theme/
Recently the Jenkins project ran the Jenkins UX Hackfest, and one of the registration questions was “What are the top 3 UX improvements for Jenkins?” The highest actionable request was a “Dark mode/theme”. By the end of the hackfest, we had a working alpha version which required a pre-release version of Jenkins. Soon after the hackfest the Jenkins patches were merged and released in v2.239.
There was still a critical issue with it though: if an admin installed the theme it was forced on all users. We didn’t want that since the dark theme is a personal preference and the quality still needed improvement. We need a way to encourage early adopters to use it without affecting everyone using their Jenkins server. And that’s how the “Theme Manager” plugin was born.
#jenkins #darkmode #uxui #opensource #themes #userexperience #userinterface
A long time ago, on a computer not so far, war away, a single entity arose to serve the software builds. We asked our user community to say why #JenkinsIsTheWay. "Inspiring, their answers were" https://www.youtube.com/watch?v=fgd1bBlQXBE
Linked In edition for review:
Achievement unlocked: more than 500 Jenkins plugins now use Documentation as Code and store their docs on GitHub. Thanks to all contributors! https://www.jenkins.io/blog/2019/10/21/plugin-docs-on-github/
In September 2019 we announced support of GitHub as a source of documentation for the Jenkins Plugin Site. Thanks to Zbyněk Konečný, Gavin Mogan, Tim Jacomb, Olivier Vernin, Mark Waite, Oleg Nenashev and other contributors, now it is possible to store plugin documentation right inside plugin repositories instead of Jenkins Wiki which was historically difficult to maintain and use.
By using plugin GitHub repositories for documentation, plugin maintainers can follow the Documentation-as-code approach and make documentation changes a part of the pull requests so that documentation follow-ups do not get forgotten. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially combined with changelog automation. Last by not least, modern documentation improves Jenkins user experience and helps them to configure their instances and automation jobs.
#jenkins #documentation #documentationascode #community #opensource #github