-
Notifications
You must be signed in to change notification settings - Fork 19
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.
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
update description of the categories #87
base: develop
Are you sure you want to change the base?
Conversation
"Frameworks": "" | ||
"Frameworks:Verification": "frameworks for verification" | ||
"Frameworks:Verification": "Frameworks for verification" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other types of frameworks to be considered?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
E.g. frameworks for "Internet of Things" including software and hardware modules that work together.
"Tools:Programmers": "Programmers" | ||
"Tools:Simulators": "Simulators" | ||
"Tools:Synthesizers": "Synthesizers" | ||
"Tools:Verification": "Verification" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure what to include here, having "Frameworks:Verification: and "Verification".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tools belong here, while libraries and scripts correspond to Verification or Frameworks:Verification. For example, Symbiyosys is a tool for formal verification, but it's useless without other tools for synthesis. A framework would include a synthesis tool, symbiyosys and helper libraries to be used all together.
Only 22 of 79 items has the categories field (and some can be wrong). We need to be clear the categories to produce a good categorization. |
"Tools:Programmers": "Programmers" | ||
"Tools:Simulators": "Simulators" | ||
"Tools:Synthesizers": "Synthesizers" | ||
"Tools:Verification": "Verification" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tools belong here, while libraries and scripts correspond to Verification or Frameworks:Verification. For example, Symbiyosys is a tool for formal verification, but it's useless without other tools for synthesis. A framework would include a synthesis tool, symbiyosys and helper libraries to be used all together.
"Resources:Books": "Books" | ||
"Resources:Social Media": "Social Media Network pages" | ||
"Resources:Websites": "Websites" | ||
"Resources:Weekly": "Weekly publications" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about this "Weekly" category. @Paebbels?
"Frameworks": "" | ||
"Frameworks:Verification": "frameworks for verification" | ||
"Frameworks:Verification": "Frameworks for verification" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
E.g. frameworks for "Internet of Things" including software and hardware modules that work together.
625e897
to
d6bde3b
Compare
Related #1 #69
I added some descriptions, but this PR is mostly to define the short descriptions to be included into config.yml (lot of definitions still needed).
I added Languages.
I belive that the general categories (Cores, Frameworks, any without a
:
) don't need a short description.