Juliette

> This link hadn't been copied over from the squizlabs/phpcs ticket that I filed over a year ago. @kenguest Yes, that comment was posted in the gap between when I...

@weierophinney Thank you for confirming what I suspected. I will go ahead and soft deprecate this in 3.9.0, hard deprecate in the last 3.x minor and remove in 4.0.

@stankarp If there had been volunteers, you would have seen their comments in this ticket (or a comment by me that people had reached out privately), so no progress so...

> @jrfnl I'm considering supporting this. I do not have loads of spare time, but I would love to work on this. According to your 'to do' list above, my...

> Fair enough. > > PER 1.0.0 is identical to PSR-12, so this will be an "easy fix". Correct, PER 2.0.0 is the bit which needs work (and setting up...

@VSlokker @aurimasbutkus Thank you both for your offer to help with this. To get you started, would it help to schedule a call ? Could you both DM me on...

@jaapio I understand what you are looking for and no, that's currently not available in this repo. However, I do not intend to accept new Commenting sniffs in this repo...

@jaapio I know where to find you 😆 and would welcome your input and help once I get started with the above, but first things first - let's get this...

@greg0ire Thanks for your input. I'm going to have to have a think about that. > Many, many contributors wrongly contributed backward-compatible changes to master, without being caught by maintainers....

> It's not a workflow I'm familiar with, but if stable is not supposed to receive PRs at all, then I suppose it makes sense to have develop be the...