maintenance contacts/contractors must contains at least one #204
valeriocomo
started this conversation in
General
Replies: 1 comment
-
+1 for this approach. Empty contacts just don't make sense with those maintenance types. Mind my broadening the discussion? I was wondering why only one value is allowed. We have the following scenario: OpenCulturas is freely available and actively maintained. But we can also provide/arrange contracts for those who feel better with a full-service offer including hosting, customizations and regular updates. Therefore it really gave us headaches to decide in favor or against maintenance/community, maintenance/contract. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
maintenance
section is defined as stated at the following link.As defined by the standard, a
publiccode.yml
is compliant even if a list ofcontacts
or a list ofcontractors
is defined but empty.It sounds weird and I started to search for old discussion about
maintenance
section.I found out this issue (#30).
I suggest to declare explicitly mandatory that at least one item must be present in these lists.
Beta Was this translation helpful? Give feedback.
All reactions