Here's an Evil Idea for a open source equivalent: foss-testing.org. Innocuous name, but it chains together user identities with checkins they've made that were

Here's an Evil Idea for a open source equivalent: foss-testing.org. Innocuous name, but it chains together user identities with checkins they've made that were 1) style violations 2) turned out to be bugs 3) turned out to be later security issues. What do I care whether I have a style violation? Well, it's about using the dark patterns to make your "user page" (collected from publically available information so legally proof) sound as bad as possible. Similar to the consumeraffairs deal where every review is bad. So your prospective employer searches for "Bob Bobson" and sees a nice, professionally designed page that claims: Bob Bobson has trouble following best practices for code styling, which could indicate a problem with following corporate standards: link to 37 instances of inconsistent naming/indentation/brace style on github Bob Bobson has 7 github repositories where he has checked in 90% of the source. This may indicate a "lone wolf" that does not play well with others Bob Bobson has 14 open issues in github trackers. This may indicate lack of following through on a project Bob Bobson has closed 41 github issues immediately as "wontfix". This may indicate a technologically orientated user that is insensitive to user and customer needs We've analyzed Bob Bobson's commit messages, and assigned it a English Comprehension Score of 4 (out of 10). This may indicate a communication problem. Failing anything else, you can smear Bob Bobson by the projects he associates with. Bob Bobson has contributed to TOR. The TOR tool is associated with child pornographers and drug traffickers. Bob Bobson has contributed to KDE. The KDE project has 523,123 outstanding bugs. We're not directly saying it's Bob's fault, but you know... Of course, you can't start off writing all negative smear about everyone. You want to start out by being positive, writing cool blogs about how your company analyzes OSS. Maybe buy some licenses for expensive static analyzers and share the results. Make some cool pages about Linus' or Guido's checkins. Maybe even sponsor a few OSS projects or OSS people. How does this make money? Well, Bob Bobson does not like to be known as a team player. Would Bob Bobson like to dispel that conclusion based on publically available data in our proprietary algorithms? Well, as it happens we also sell a "TeamWork Evaluation Survey", where if you think your team work skills have improved you under go a comprehensive psychometric test (signed off on by our team of psychometric specialists) that verifies your team work skills. Of course, such a test is expensive, but isn't the $199 worth it to be given a prominent "Team Work: Gold Badge" score? All that other stuff we said about you being a bad team player will go away.