Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Nominations Open] Jenkins Security MVP 2025 🏆 #7980

Open
alyssat opened this issue Mar 14, 2025 · 2 comments
Open

[Nominations Open] Jenkins Security MVP 2025 🏆 #7980

alyssat opened this issue Mar 14, 2025 · 2 comments
Labels
community Posts and topics for community engagement events

Comments

@alyssat
Copy link
Contributor

alyssat commented Mar 14, 2025

This issue is to receive nominations for the Jenkins Security MVP 2025. This award is presented to an individual most consistently providing excellent security reports or resolving security issues.

To nominate someone, reply to this issue with the following:

Full name of the person you’re nominating
A short description of their contributions to Jenkins and why they should win.
Nomination Deadline: April 14, 2025

Please note: Last year's winner, Yaniv Nizry, cannot win the award for Jenkins Security MVP again this year.

Voting will be open from April 22 to June 5.
Winners will be announced at cdCon 2025, June 23–25.

More details are available HERE.

Award type:
The awards will be virtual credly badges again this year (not physical).

@alyssat alyssat added enhancement community Posts and topics for community engagement events and removed enhancement labels Mar 14, 2025
@kmartens27
Copy link
Contributor

I would like to nominate @yaroslavafenkin for his work on the CSP project. Yaroslav provided tons of work and insights into the project and how Jenkins' CSP can be enhanced. This work helped not only Jenkins core, but its plugin ecosystem as well. This was lot of work done in a somewhat short amount of time, yielding fantastic results.

@kmartens27
Copy link
Contributor

I would also like to nominate @shlomomdahan for his work on the CSP project. Shlomo contributed his time and effort to help enhance the Jenkins CSP and provided support for both Jenkins core and the plugin ecosystem. These efforts are crucial in ensuring that Jenkins is both secure and future proof. The work done in this project also helped educate and inform plugin maintainers about what is needed when it comes time to provide further safe-guarding in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Posts and topics for community engagement events
Projects
None yet
Development

No branches or pull requests

2 participants