Replies: 4 comments 1 reply
-
|
A screenshot of a script Is awful, buy probably there will be free scripts.
Il Mer 14 Ago 2019, 17:07 Alessandro Ranellucci <[email protected]>
ha scritto:
… Maybe in a future version.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/italia/publiccode.yml/issues/67?email_source=notifications&email_token=AHDGY7OF2R4CWGW5O4LYPGLQEQNR3A5CNFSM4ILV6DV2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HFHNLHQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHDGY7NDII6ASEXCRPER4L3QEQNR3ANCNFSM4ILV6DVQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Not every project will have visual elements |
Beta Was this translation helpful? Give feedback.
-
|
Moved to GitHub Discussions |
Beta Was this translation helpful? Give feedback.
-
|
The "requirements" (as in things coded into the schema to flag files as invalid) should be as light as possible. Better for projects to start having a publiccode.yml early than to wait until they have more details and never get to it. The hard requirements should be oriented around a minimum viable project description -- probably just title+link+license. Beyond that, leave it to consumers of publiccode.yml files to express what additional fields are strongly recommended or even required for projects under their purview, but keep those opinions out of the common schema please. As a maintainer of a project that consumes publiccode.yml en masse, it doesn't help our efforts for project maintainers we're trying to encourage to adopt publiccode.yml to be getting confused by schema errors about fields we don't care about. |
Beta Was this translation helpful? Give feedback.
-
|
I fully agree with you! |
Beta Was this translation helpful? Give feedback.
-
Maybe in a future version.
Beta Was this translation helpful? Give feedback.
All reactions