Update Support_Question.md#9218
Conversation
Update community links in the Support issue template. Using the join links ensures that new users can get access as intended, rather than only allowing access for existing users.
| ## Community Resources | ||
|
|
||
| [Slack Community Chat](https://powershell.slack.com) - Interactive chat with other PowerShell enthusiasts | ||
| [Slack](https://j.mp/psslack) and [Discord](https://j.mp/psdiscord) Community Chat - Interactive chat with other PowerShell enthusiasts. Both Slack and Discord are bridged via a bot and can seamlessly talk to each other. |
There was a problem hiding this comment.
The existing link is not the join link. It simply links to the Slack space and does not allow new users to join it or view it.
The bitly links are easier to remember and both link to semi-permanent join links for each channel. On occasion these links have had to change, so having the shortlink that can be updated is a lot easier than updating the direct links everywhere they're posted.
If you guys would rather create an aka.ms link, you're more than welcome to! 😄
I think these links are maintained by @Jaykul, to the best of my knowledge.
There was a problem hiding this comment.
Since these two chat channels are community maintained and not Microsoft, I would not create aka.ms links to them. if we can confirm that Joel Bennett or some MVP is maintaining those links, I'd be more comfortable using them.
There was a problem hiding this comment.
Alternatively, we can have the long url at the bottom of the doc and ref the link that way so that the markdown is still readable as just text
There was a problem hiding this comment.
@SteveL-MSFT so I'm not against that, but the link currently in this document is unusable by anyone who's not already joined the slack space.
If we want to do that, we'd need the actual join link here (which I guess we can get from the shortlink either way).
@Jaykul, you're maintaining that shortlink, right?
There was a problem hiding this comment.
@vexx32 yes, I was suggesting using the resolved long url and to put it at the bottom of the doc to not impede readability since it's not made for human consumption
There was a problem hiding this comment.
Huh, looks like @TylerLeonhardt beat us to it, I didn't realize there were aka.ms versions already:
https://aka.ms/psdiscord https://aka.ms/psslack
I guess we'll use these instead then?
There was a problem hiding this comment.
I don't think anyone wants to maintain an aka.ms link for this from our side, so the fully qualified links are probably the way to go (anchored at the bottom, as @SteveL-MSFT suggested). It's going to be easier for everyone to spot and fix the breakage here than if they have to track down @TylerLeonhardt to get the aka.ms updated.
And yeah, we shouldn't ship bit.ly links we don't own for security reasons.
|
This PR has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs within 10 days. |
Add link-refs for readability
|
Manually queued static analysis since it didn't trigger: https://powershell.visualstudio.com/PowerShell/_build/results?buildId=21528 |
|
@PoshChan Please remind me in 1 hour. |
|
@TravisEz13, will remind you in 1 hour. |
|
@TravisEz13, this is the reminder you requested 1 hour. ago |
A little birdie told me PowerShell#9218 was having issues with the links.
|
@PoshChan please get failures |
|
@SteveL-MSFT, test results were not published for PowerShell-CI-install-ps at vstfs:///Build/Build/21613 |
|
@SteveL-MSFT, test results were not published for PowerShell-CI-linux at vstfs:///Build/Build/21611 |
|
@SteveL-MSFT, your last commit had 1 failures in Expected 1, but got 0.
at <ScriptBlock>, /Users/vsts/agent/2.150.0/work/1/s/test/powershell/engine/Help/UpdatableHelpSystem.Tests.ps1: line 181
181: $helpFilesInstalled.Count | Should -Be $expectedHelpFiles.Count |
|
@SteveL-MSFT, test results were not published for PowerShell-CI-static-analysis at vstfs:///Build/Build/21609 |
|
@SteveL-MSFT, test results were not published for PowerShell-CI-windows at vstfs:///Build/Build/21612 |
|
@PoshChan please retry macos |
|
@SteveL-MSFT, successfully started retry of |
Update community links in the Support issue template.
Using the join links ensures that new users can get access as intended, rather than only allowing access for existing users.
PR Summary
PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.[feature]to your commit messages if the change is significant or affects feature tests