Topics

Badges which are impossible to attain for some projects


Florian Weimer
 

Would it make sense to propose badges which are impossible to attain for some projects due to mismatches in technology?

I would like to explore some ideas related to the project build process, and some issues simply do not arise for, say, Perl or PHP projects, which are left in source form even for deployment, and build-related badges would not apply to such projects.

Thanks,
Florian


David A. Wheeler
 

Florian Weimer:
Would it make sense to propose badges which are impossible to attain for some projects due to mismatches in technology?
I would like to explore some ideas related to the project build process, and some issues simply do not arise for, say, Perl or PHP projects, which are left in source form even for deployment, and build-related badges would not apply to such projects.
Yes, we already have criteria that don't apply to all projects. Those criteria have the logical form "If X, then Y", and/or allow N/A as a response.

For example, criterion "build" says: "If the software requires building for use, the project MUST provide a working build system that can automatically rebuild the software from source code." There are 21 criteria that allow N/A (see the criteria stats page: https://bestpractices.coreinfrastructure.org/criteria).

--- David A. Wheeler