Perfect … guess I do a fork to my account, then incorporate my (simple) adaptions and then add a pull request with the changes from my fork?
I’ve just called it CF 8, while retaining all pre-existing version numbers … but could also just call it Classic Contact Form 7 for now.
The CF8 relable thingy is, because CF 7 really came to be like this - in the early history of WP there were several (rather successful) contact form plugins with the fancy titles “Contact Form”, “Contact Form 2”, “Contact Form 3” and so on. Each one taking the best bits or whatever their author(s) considered to be useful and incorporating it into the new plugin. At some point, CF 7 was the only one that remained … hence my idea calling it CF 8 later on. Could do it similar to ClassicPress, ie. internally keeping the version numbers of CF 7 5.3.x, and enhancing it with own version strings / numbers and functions / methods for potentially supporting CF 7 / CF 8 add-ons.
Maybe when starting to do actual changes, eg. adding a less complicated way of parsing the CF 7 short tags / patterns.
Cause that is the main PITA for beginners but also professional users - you always have to stick to the patterns and try multiple times, rearranging things, when the field you wanted to add clearly does not work like it should.
I am aware of the efforts of establishing a secondary short code system just for CF 7, eg. using double square brackets (a la
[[my_tag]]), but it could easily be just a less strict shortcode pattern or just a bit more logical one (eg.
class:"class-name1 class-name2" instead of having to wonder whether
class:my-cllass classname2 is actually gonna work or not) and so on …