In reply to Sayontan Sinha.

I'm going to address just a few items:

I can assure you that Carolina has been fighting for both developers and users for far longer than you seem to think she's been involved. She's been down in the trenches doing all the tough work that so many others have not even so much as glimpsed at. Sure, she and I have disagreed on many occasions, but she's always had the best interests of the project in mind.

As for the WPTRT mailing list, which we had pre-Slack, participation from developers was still relatively low compared to what was needed to improve the directory. And, much of that participation broke the universal "don't be a ****" rule. People seemed to be far more willing to break that rule through a fairly obscure mailing list but not on more public Slack and Make blogs. It was an untenable mess.

On the "responsive" name, you glossed over a much larger trademark/branding discussion, which is something directory personnel are pretty much required to deal with.

Since you brought it up for a second time in the comments without fully representing the situation, I'll address the Suffusion theme issue. You threw in the towel when it was taken down from the directory because of a fatal error. You avoided addressing valid licensing, security, and standards-compliance issues the reviewer brought up. The reviewer even offered to help you address things along the way. Then, you misrepresented your theme being taken down to your theme users as simply a reviewer requiring the use of the customizer, which was only a small piece of review.

The axe finally fell when a theme reviewer pulled Suffusion from the repository and listed Customizer integration as a requirement to get it relisted. And that is when I retired the theme.

Maybe that was your reasoning, but none of the other items were listed in your explanation. Were there some parts of the review that maybe were not 100% necessary for a functioning theme? Sure. But, those were not the major issues.

I hope that you at least addressed those security issues for end-users who continued using your theme via GitHub. At the end of the day, folks can quibble over things like using the customizer or branding guidelines, but security should be a top priority for the team.