-
Notifications
You must be signed in to change notification settings - Fork 76
Project Roadmap
Add support for submission validation
A user submit a submission as a GitHub issue. Currently, no automatic data validation is happening. For example, no check that the description is <135. A validation mechanism is needed. This implies that the bot needs to comment with possible errors into the submission issue.
Add explanation about badges
- Create the badge as part the submission PR so it can be used immediately after the merge
- Maybe the issue can be closed with "next steps", and the badge can be an option
- Maybe the badge can be used for signaling the ecosystem "status"
Fetch data from GitHub for a submission
If a GitHub repo is provided, some of the information can be fetched automatically
- License
- Description: from the repository About
Clean submission template
- Update urls: github pages -> qisk.it
Remove "IBM maintenance status"Remove markdown support for text boxesRemove "Alternatives"- The action that updates stars, it can also update the list of topics and types.
Support for package repositories
- PyPI
- Crate
- Visual Studio | Marketplace (for example, https://marketplace.visualstudio.com/items?itemName=qiskit.qiskit-vscode)
- open-vsx: See https://open-vsx.org/swagger-ui/index.html#/registry-api/getExtension
curl -X 'GET' \
'https://open-vsx.org/api/qiskit/qiskit-vscode' \
-H 'accept: application/json'
- Opam (for example, https://opam.ocaml.org/packages/qiskit/)
Support other-than-GitHub repositories
- GitLab
- Bitbucket
- Azure DevOps
- GForge
- our project org
- GNU Savannah
- SourceForge
- Generic .git/mercurial/svn repo URL
Enrich members data
- pypi downloads
- last update date
- open issues
- last release
Regularly check the membership conditions and clean the members list
Regularly, the members need to be checked. Is the license still open? Is there any recent activity or abandon? is it archived?