Hey guy, I'll try and keep this short. As most people have noticed, there has been a large influx of method proposals recently - which ISN'T a bad thing. However, many of these proposals are vapid, poorly thought out or reseatched, and/or are rehashing of previously proposed methods. The biggest culprit is obvious RouxFOP.. or BBOP.. or Roux-CFOP Hybrid.. etc. These proposals are very often tactless and have no interest in furthering method development.. which I feel is very frustrating for people that have poured HUNDREDS of hours into developing, testing, researching, and fine-tuning their own, unique, methods.
With this post I am hoping that we can come up with a way to raise the standards of method proposals by creating some sort of outline for what an acceptable proposal should be. I feel that one of the rules should be that, when the method is proposed, it should have prior developments via generated algsets/sheets, fleshed out logic trees, tutorials, and/or example solves. This would hopefully require people to put in a bit more effort when coming up with methods and to avoid the chronic 'list of steps' proposals ( One of my personal pet-peeves is seeing RouxFOP proposed yet there being no attempt to generate EO+DF/DB algs, arguably the only unique thing about the method ).
With this post I am hoping that we can come up with a way to raise the standards of method proposals by creating some sort of outline for what an acceptable proposal should be. I feel that one of the rules should be that, when the method is proposed, it should have prior developments via generated algsets/sheets, fleshed out logic trees, tutorials, and/or example solves. This would hopefully require people to put in a bit more effort when coming up with methods and to avoid the chronic 'list of steps' proposals ( One of my personal pet-peeves is seeing RouxFOP proposed yet there being no attempt to generate EO+DF/DB algs, arguably the only unique thing about the method ).