-
Notifications
You must be signed in to change notification settings - Fork 13
Conversation
🦋 Changeset detectedLatest commit: bcbcf0a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Re: the changeset, should I be adding that? @1ucian0 perhaps how urgent is releasing a new version of this web component? |
Important, but not that urgent. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a small comments about whether we should keep Slack on the menu or remove it to direct all people to the support channels page which contain more information about Slack and which channels to join.
label: 'Stack Exchange', | ||
url: 'https://quantumcomputing.stackexchange.com/questions/tagged/qiskit', | ||
label: 'Support Channels', | ||
url: 'https://qisk.it/support', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Support channels page contain information about Slack as well. Should we remove the Slack link in this drop down menu?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that too. I think it depends how much we want people going to Slack? For Pantsbuild, that was a huge project priority so we referenced Slack everywhere like blog posts. Even if it was repetitive like this here would be.
For Qiskit, how much do want to specifically funnel people to Slack? If we want to, then I think it's worth repeating. Otherwise, we could probably remove.
The benefit of removing would be less text in the top nav bar, I suppose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me the benefits of removing it is so that people will read the information about different slack channels and where to get help for specific issues, similar to the spirit of this PR trying to guide people to read about what kind of questions should go to StackExchange instead of sending people there directly.
FYI, I created this an unrelated issue about removing Qiskit Textbook from the "Help and Learning" column: #214. That issue may need some more discussions. But if we reach consensus before this was merged. We can potentially address that issue in this PR if that helps to be reviewed and merged quicker. |
Bump @abdonrd when you get a chance |
You want to merge the PR? If you confirm it, I'll merge it! Anyway, I am not actively working on this project. Better to ping @y4izus @techtolentino @eddybrando |
Yes, please, to merging. All ready to go :) Ah, thanks for the FYI! |
Changes
Closes #210.
Idea comes from @1ucian0
Implementation details
Uses the short link https://qisk.it/support rather than https://github.com/Qiskit/feedback/wiki/Communication-Channels-&-Support because it is more stable, e.g. if we move that page away from GitHub Wiki.
Also removes Slack because it's already covered by the Support Channels link.