Tracking and revisioning of set files
The more I look at the suggested set files, the more difficult it gets to understand the changes. However, in my opinion understanding the changes is critical to continuous improvement. Otherwise its like shooting in the dark.Some set files may be good, but the other users wont exactly know why.
This gets even more complicated the more features and parameters CP offers.
I would propose here a common "diff" process to a set file.
We can use meld (or any other diff tool for text files) to extract the differences between two files. Here you can see an overview of such tools for windows.
https://www.git-tower.com/blog/diff-tools-windows/
Given the Live CP CCI sets discussed here https://communitypowerea.userecho.com/en/communities/4/topics/301-improvement-o-live-cp-set-with-cci-closing?page=1#comment-1817
This is an example diff (screenshots) between the original set file and the latest one.
I suggest to integrate some kind of automated script scanning the forum and posting the diff screenshots or short summaries automatically after someone uploads a set file.
A summary could also look in short like this (example, where the DD was reduced by 2x of the latest proposal),
I could support the community with a python selenium script, which grabs the set files from the forum.
Please post your thoughts on this.
That is a nice thought. But not every set file posted may be an improvement.
So may be we need to selectively decide on this. Thanks.