Jenkins Governance Meeting on Jun 17, 2020

22 views
Skip to first unread message

Oleg Nenashev

unread,
Jun 16, 2020, 5:06:36 PM6/16/20
to JenkinsCI Developers
Dear all,

The next Jenkins Governance Meeting will take place on June 17th, at 6:00-7:00PM UTC. The meeting will be held in Zoom, please use this link to join. This is an open meeting, everyone is welcome to participate.

You can find the draft agenda below. Please feel free to propose your topics here. The idea is to have a number of relatively short topics in the beginning of the meeting, and then to spend the second half of the meeting to discuss the terminology updates which is a quite hot topic in the developer mailing list.

As usual, the recording of the meeting will be published on June 18th after the call. Meeting notes will be available here.

Best regards,
Oleg Nenashev

Daniel Beck

unread,
Jun 16, 2020, 7:20:16 PM6/16/20
to Jenkins Developers


> On 16. Jun 2020, at 23:06, Oleg Nenashev <o.v.ne...@gmail.com> wrote:
>
> • Terminology updates
> • https://groups.google.com/forum/#!topic/jenkinsci-dev/CLR55wMZwZ8
> • Vote: Replacing the whitelist/blacklist terminology
> • Allowlist/Denylist
> • Allowlist/Blocklist

This seems premature. The scope is unclear. There's a single whitelist I can think of that's exposed on the UI and not effectively deprecated, and that's in a (bundled, but still) plugin. Are there others, or is this a matter of a single PR to a single component?

> • Discussion: Replacing master terminology

The discussion is ongoing on the dev list, adding a second channel that only some can participate in seems counterproductive. What's the goal here?

Tracy Miranda

unread,
Jun 17, 2020, 11:25:23 AM6/17/20
to jenkin...@googlegroups.com
It seems reasonable to me that we vote on the decision to deprecate whitelist/blacklist in favour of the new terminology. 
Similar to slave process that would be as a community we state our intent and have no new materials/code created with the deprecated terms. 
This also means we contact blog post/tutorial writes and let them know we've updated terms as we do already with slave term.

At the last advocacy & outreach meeting we did a quick search and there were a bunch of uses of the whitelist phrase beyond what you reference here (e.g. in JEPs). 
We can vote on the deprecation and then track places to upgrade, similar to https://issues.jenkins-ci.org/browse/JENKINS-42816 (i.e. separating out trivial changes and non-trivial ones that impact compatibility). 

There are many conversations on this happening in different forums which is good. The governance meeting seems a good place to continue these conversations and drive for shared understanding and work towards consensus. 

Tracy

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7F13AC61-0CDB-4C7A-9CD9-411786F1D9D1%40beckweb.net.

Oleg Nenashev

unread,
Jun 17, 2020, 1:54:14 PM6/17/20
to Jenkins Developers
I think it worth discussing the terminology ad collecting more feedbak about options listed in https://docs.google.com/document/d/1-8myIWOZZktR0HNtbFIiNA0RfDCvkfKKuNI0C3wcvbo/edit?usp=sharing
No strong opinion about voting today, but we could agree whether we change the terminology or not. That part looks relatively straightforward taking the feedback we've got from users and contributors.

BR, Oleg
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.com.

Oleg Nenashev

unread,
Jun 19, 2020, 7:42:00 AM6/19/20
to Jenkins Developers
Hi all,

Materials from the meeting:
Best regards,
Oleg
Reply all
Reply to author
Forward
0 new messages