This repository has been archived by the owner on May 17, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 108
Qiskit qiskit.org Ideas Discussions
Pinned Discussions
Sort by:
Latest activity
Categories, most helpful, and community links
Categories
Community links
💡 Ideas Discussions
Share ideas for new features
-
You must be logged in to vote 💡 -
💡 Re-organize
organizationproject: type
labelsIssues related to team and project organization. -
You must be logged in to vote 💡 Include checklist in pull request template
organizationIssues related to team and project organization. -
You must be logged in to vote 💡 How can we improve our homepage CTAs
designDesign issues. -
You must be logged in to vote 💡 -
💡 Consolidate 1 "Projects" section and 1 "Discussions" section for all projects
organizationIssues related to team and project organization. -
💡 Set repository permissions using organisation teams
organizationIssues related to team and project organization. -
💡 Setup Storybook add-ons
code qualityIssues related to code health like refactors and cleanups. -
You must be logged in to vote 💡 Define directory structure for component files
code qualityIssues related to code health like refactors and cleanups. -
You must be logged in to vote 💡 Store reusable types and interfaces in a central directory
code qualityIssues related to code health like refactors and cleanups. -
You must be logged in to vote 💡 Documentation
documentationIssues related to documentation. (Not to the "Qiskit Documentation" project) -
💡 Update to Node 16 in all projects
code qualityIssues related to code health like refactors and cleanups. -
You must be logged in to vote 💡 Translations keys in textbook
code qualityIssues related to code health like refactors and cleanups. -
💡 Refactor CSS naming (drop BEM?)
code qualityIssues related to code health like refactors and cleanups. -
You must be logged in to vote 💡 Rethink the icons and links under maintainers on README.md file
documentationIssues related to documentation. (Not to the "Qiskit Documentation" project) -
💡 Use semantic versioning to tag releases
devopsIssues related to DevOps. -
💡 Name Vue component classes
code qualityIssues related to code health like refactors and cleanups. -
You must be logged in to vote 💡 Consider moving to a server-supported backend
devopsIssues related to DevOps. -
You must be logged in to vote 💡 Review rel attribute values for tag <a>
code qualityIssues related to code health like refactors and cleanups. -
💡 Unify vocabulary regarding place & location, and event location and region
contentIssues related to content information. -
💡 experiments page tagline grammar
contentIssues related to content information.