best-practices-badge

This is great news! I lead the "CII Best Practices Badge" project for OSS projects - if you have an OSS project, and you meet certain requirements, you can get a badge. One criterion is that "The project sites (website, repository, and download URLs) MUST support HTTPS using TLS.": https://github.com/linuxfoundation/cii-best-practices-badge/... I think making GitLab pages part of the community edition will make it easier to meet this criterion. Congrats, and thanks!

Thoroughly agree that this is a human problem, but I think there are some amazing automated fixes for it, by incorporating code checkers into the continuous integration pipeline. Take a look at how the CII best practices badgeapp [0] uses pronto [1] to run rubocop [2] automatically for free via CircleCI [3] and surface those results via the Github Status API and email. The whole point is to avoid having to manually complain in a code review. Instead, code reviews become a much higher level exercise discussing proper APIs and code structuring, not sphaghetti issues. [0] https://github.com/linuxfoundation/cii-best-practices-badge/... [1] https://github.com/mmozuras/pronto [2] https://github.com/bbatsov/rubocop [3] https://circleci.com/

They're talking about a different kind of best practices, but I highly recommend taking a look at the Core Infrastructure Initiative's Best Practices Project [0], which was created partially in response to the Heartbleed disaster. It's a list of 66 practices that all open source software, including scientific software, should be following. [0] https://github.com/linuxfoundation/cii-best-practices-badge/... (Disclosure: I'm a co-founder of the project. It's completely free and open source, and the online BadgeApp itself earns the best practices badge.)

I am a co-creator of this program, and we very much had the HN crowd in mind for it. Please consider adding a badge for all of the open source projects you contribute to. Here's the badging app [0] and the open source project [1] where you can review and comment on the criteria. [0] https://bestpractices.coreinfrastructure.org/ [1] https://github.com/linuxfoundation/cii-best-practices-badge/

The issue is not whether projects are old, it's whether they're well-maintained. Please see the Core Infrastructure Initiative's Best Practices Badge project for one attempt at measuring the "health" of an open source project. https://github.com/linuxfoundation/cii-best-practices-badge#...