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 On Wednesday, June 17, 2020 at 5:25:23 PM UTC+2, Tracy Miranda wrote: > > 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 > > On Tue, Jun 16, 2020 at 7:20 PM Daniel Beck <[email protected] > <javascript:>> wrote: > >> >> >> > On 16. Jun 2020, at 23:06, Oleg Nenashev <[email protected] >> <javascript:>> 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? >> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/7F13AC61-0CDB-4C7A-9CD9-411786F1D9D1%40beckweb.net >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f61c7074-1f90-42ce-9683-11655af1ce85o%40googlegroups.com.
