treebeard5440

I have two (both many years ago)

1. Every line of every file in the project had its line ending changed

2. Python script that called a python script that called another python script

Anyone else have some good ones?

I’m curious if this is standard practice for most projects. If not, do you expect an error in your config files to be caught by unit and/or functional tests?

I’m the maintainer of a project[0] that could provide syntax validation for multiple config file types in a CI/CD pipeline. I haven’t really seen that type of quality gate in very many projects though.

[0] https://github.com/Boeing/config-file-validator

I been running an OSS project for almost a year now and I feel like it’s been fairly successful for a small project. We have had quite a few contributors - especially during hacktoberfest that have given us high qualilty PR’s. While the contributions have been better than ever expected we’re not as strong on some other “metrics” such as stars, forks, watchers, etc. Looking through discussions some people only value those things while others completely disregard them. I’m curious how other maintainers determine the success of their OSS projects. Outside of “metrics” and contributors is there anything else to consider?