Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
It's become--alas--quite common for developers to review their own software, which undermines the very idea of a review.
It'd be useful to spot self-promoting reviews, to provide a more balanced idea of software quality to end users.
Ohloh could easily mark (via CSS fo example) reviews by developers affiliated with a project as contributors. Obviously, nothing prevents user X from registering a second account Y to write an independent
review of his/her product. But this CSS-trick could be a first approximation to spot blatant marketing.
What do you think?
The problem is where do you draw the line between an active user and a developer.
I've just reviewed DBIx::Class, but I've committed a couple of tiny patches - does that mean I'm biased ?
I also use a variety of other codebases heavily, and the ones I use the most I tend to commit or send patches to list - several projects have my patches in, but I didn't commit them - can I review them as unbiased ?
With Free Software, there should be no line drawn between users and developers :-)