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.

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

Allow contributors to submit a GitHub URL for the aggregation of open-source without package file #49

Open
elijah286 opened this issue Jul 24, 2020 · 1 comment
Labels
user story Feature seen from an end-user perspective
Projects

Comments

@elijah286
Copy link

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.

@elijah286 elijah286 added the user story Feature seen from an end-user perspective label Jul 24, 2020
@chrisb2244
Copy link
Collaborator

chrisb2244 commented Jul 24, 2020

Released files (as given in releases) can be fetched using the API here: https://developer.github.com/v3/repos/releases/

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"?

@qalldredge qalldredge added this to Incoming User Stories in Story Board Apr 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user story Feature seen from an end-user perspective
Projects
Story Board
  
Incoming User Stories
Development

No branches or pull requests

2 participants