Thanks for working on it, Basil! I think the pull request documents the current process well, and I support merging it in the current form
On Friday, February 10, 2023 at 1:55:18 AM UTC+1 m...@basilcrow.com wrote: > Over the past few months and especially during Hacktoberfest, I have > observed several cases where the Jenkins core contribution process did > not go as smoothly as it could have gone. After thinking deeply about > several examples, I concluded that the existing process contains > several ambiguities that, once disambiguated, would make the process > go more smoothly in the future. I distilled my thoughts into a > concrete process improvement in > https://github.com/jenkinsci/jenkins/pull/7516 and submitted my > proposal for review in December. > > Response to this proposal has been mostly positive, with negative > feedback isolated to specific details of the proposal rather than the > overall concept. All feedback has been addressed at the present time. > > I would like to bring this proposal to a conclusion by March. If any > active core maintainers have not yet considered the proposal, please > do so and express (in the pull request) your view — positive, > negative, or neutral — and the reason for that view. If anyone has > left feedback already, please confirm that it has been addressed in > the latest revision by approving the pull request. > -- 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-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e8ed0948-f353-4762-a825-b6241e46b0ebn%40googlegroups.com.
