Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider removing genericName #59

Closed
alranel opened this issue Apr 4, 2019 · 1 comment · Fixed by #146
Closed

Consider removing genericName #59

alranel opened this issue Apr 4, 2019 · 1 comment · Fixed by #146
Labels
standard-breaking-change This change breaks backward compatibility vote-draft Change proposal to the Standard or to the governance procedures

Comments

@alranel
Copy link
Contributor

alranel commented Apr 4, 2019

As of now, genericName is mandatory and limited to 35 characters.

However, field experience is showing that this field always contains information that is already carried by shortDescription, softwareType and categories. We should consider removing genericName if no good reason for it arises.
@alranel alranel added the meta Meta changes not related to the standard itself label Apr 4, 2019
@libremente libremente added the vote-draft Change proposal to the Standard or to the governance procedures label Jun 14, 2019
@bfabio
Copy link
Contributor

bfabio commented Jun 22, 2021

Posted to the forum as https://publiccode.discourse.group/t/consider-removing-genericname-issue-59/65

@bfabio bfabio added standard-breaking-change This change breaks backward compatibility and removed meta Meta changes not related to the standard itself labels Dec 5, 2021
bfabio added a commit to bfabio/publiccode.yml that referenced this issue Mar 28, 2022
@bfabio
docs(standard): make genericName optional and deprecate it
1edbf77 
genericName doesn't really fit software outside Desktop environments
and is often misused in practice. Also, we don't offer any controlled vocabulary
for generic names.

The 'shortDescription' and 'name' keys are good enough.

Fix publiccodeyml#59.
@bfabio bfabio mentioned this issue Mar 28, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
standard-breaking-change This change breaks backward compatibility vote-draft Change proposal to the Standard or to the governance procedures
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs(standard): make genericName optional and deprecate it bfabio/publiccode.yml
3 participants
@alranel @bfabio @libremente