I'd love to be able to filter out the vipm.io content with labels such as "open source" to only list the projects that have a public repository that I can fork and/or contribute to.
This would filter out any package that do not accept contributions. Free does not mean opened. I know that "tags" could be useful filters, but tags do not mean that the information is verified.
If there are multiple packages that provide solutions to similar functionality, I'd like to further filter down the list. On the other hand, some users might want to filter out the open source projects in favor of commercially-supported packages...
Useful filters could be "open-source", "free", "free-trial", "driver", "commercially-supported", "alliance-partner", "NI", etc.
Those filters should be automatically set through the package publishing process, not through tagging.
Question
Francois Normandin
I'd love to be able to filter out the vipm.io content with labels such as "open source" to only list the projects that have a public repository that I can fork and/or contribute to.
This would filter out any package that do not accept contributions. Free does not mean opened. I know that "tags" could be useful filters, but tags do not mean that the information is verified.
If there are multiple packages that provide solutions to similar functionality, I'd like to further filter down the list. On the other hand, some users might want to filter out the open source projects in favor of commercially-supported packages...
Useful filters could be "open-source", "free", "free-trial", "driver", "commercially-supported", "alliance-partner", "NI", etc.
Those filters should be automatically set through the package publishing process, not through tagging.
Link to comment
Share on other sites
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.