I’m afraid of the Webform module’s issue queue. I see the Webform 8,x-5.x module’s usage stats growing and with it, duplicate bug reports are increasing. The webform_update_8025() update hook is going to haunt me for months. Now I’m afraid to write any update hook that touches an existing field definition. I’ve realized that it is time to push back on the Webform module’s issue queue before it’s too late.Hear me out: I’m not looking for a fight – just a solution to a very simple problem. People don’t know how to write proper bug reports and feature requests, and they don’t like to read the issue queue handbook. The solution could be equally simple, which would be to require them write good tickets.Plenty of documentation and videos about writing good issues exist. My goal is to make it easier for people to write complete and useful tickets so I can better assist them.Help us Help youFor now, I have three goals for improving the Webform issue queue process:Provide easy-to-use bug and features templates.Encourage users to employ these bug and feature templates.Show users how to create a good issue.Provide bug and feature templatesGitHub allows a maintainer to create an issue template and pull request for their repository. I have decided to do the same thing for the Webform module. Drupal maintenance support plans.org does not really support issue templates, however I can recommend that people use them by prepopulating the issues’ body fieldPrepopulate the “Create…Read More
Source: New feed