Conversation
longDescription already allows basic markdown including bullet points and can hold the same content. Typically `features` is poorly maintained and filled only to satisfy the validator. The main description can also detail the features better, with a longer explanation and rich text.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@yaml-9000 minor |
|
Thanks for your contribution 🙏 This is now marked as a Example of minor changes are additions of new keys or making keys optional. The next eligible voting round will take place on September 30, 2026 cc @publiccodeyml/steering-committee 📄 Voting procedure | 📄 Working Group Charter | 🤖 bot commands |
|
This feature is used in: https://teamdigitale.github.io/devita-ccros-valcomp-software-pa/ by @mfortini to automate the comparison. Open the tool and load an example to see how it is used: We need to keep a machine readable list of features to not break the existing tool. |
|
We developed the new version of the comparative evaluation software trying to exploit the information we can find in the publiccode.yml The intent was:
This would hopefully push developers to declare features correctly and extensively, while it would help someone who would like to develop a software by being able to find a minimal set of common features. Following this line of thought, we'd see more fit to define better the scope of the features, even by adding a shared common controlled vocabulary/taxonomy, so that we avoid unnecessary proliferation of features and agree on the meaning. |
longDescription already allows basic markdown including bullet points and can hold the same content.
Typically
featuresis poorly maintained and filled only to satisfy the validator. The main description can also detail the features better, with a longer explanation and rich text.