You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Developers who have their LabVIEW source stored and managed on GitHub shall be able to submit the URL for their repository in order to have GCentral include the open source library in search results
The results page for the item would be expected to reflect standard artifacts to generate the meta data, including the Readme file, examples and any installation instructions.
If the Github page includes the package file, this will be served up on the webpage.
The text was updated successfully, but these errors were encountered:
For this to be practical I think GCentral would want to produce documentation as to what would be picked up from where (e.g. README.md, README.txt?... in root directory) and how that would be used to produce a GCentral entry/page.
How should GCentral deal with e.g. zip files in releases? Do nothing if it isn't a .nipkg, .vip, (.gpkg? not sure about extension here...) Or allow any "released file"?
Developers who have their LabVIEW source stored and managed on GitHub shall be able to submit the URL for their repository in order to have GCentral include the open source library in search results
The results page for the item would be expected to reflect standard artifacts to generate the meta data, including the Readme file, examples and any installation instructions.
If the Github page includes the package file, this will be served up on the webpage.
The text was updated successfully, but these errors were encountered: