Dne 30.11.2017 v 11:48 Stefan Hundhammer napsal(a):
On 30.11.2017 11:14, Josef Reidinger wrote: ... - codeclimate-duplication: Tries to find duplicate code. OK, that might be useful if it really works. But the question is if it works across package boundaries, e.g. between one YaST package and others. I am doubtful about that.
That works very well, it actually uses some fuzzy search, i.e. if you copy a block and slightly modify it (rename variables, change constants, call a different method...) then it will still complain about a similar piece of code. https://codeclimate.com/github/yast/yast-storage-ng/issues?engine_name%5B%5D... Of course, it does not work across the repository boundary so it cannot see the external duplicates. I wanted to run some duplication scan in YaST locally, but I do not know which tool they use, maybe it's their own internal tool.
4. provides badge for project, so it shows external people some idea about code quality
If it's badges we are after, I can offer you as many as you like - colored, black and white, whatever.
What's wrong with badges? When I want to use some rubygem and it has a codeclimate badge (usually displaying a good value otherwise they would not use it I guess ;-)) then it encourages me to use it. Or I might pick a different gem... The same with the Travis badge, if it is there it means the developers take testing (more) seriously...
But I am not sure how many users and customers care about that. As Arvin mentioned, the number and severity of bugs and our response time for a first reaction and until a fix is released will matter a lot more to them. But none of that is something we make easily accessible to the public.
Of course, the badge is not designed for the end users. Our end users also do not look at bugzilla (until they find an issue). But there is no point in discussing it, you just put a link to README and that's it. It's for free. -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org