close
The Wayback Machine - https://web.archive.org/web/20211031012833/https://github.com/spf13/cobra/issues/1493
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

Jump to bottom

slack link is not public #1493

Open
robberphex opened this issue Sep 22, 2021 · 4 comments
Open

slack link is not public #1493

robberphex opened this issue Sep 22, 2021 · 4 comments
Labels
area/documentation good first issue

Comments

Assignees
No one assigned
Labels
area/documentation good first issue
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
@marckhouzam @robberphex @jpmcb @umarcor
@robberphex
Copy link

@robberphex robberphex commented Sep 22, 2021

At README.md, there is a slack link:

Slack

Is it for public discussion for the project?

But the slack link shows "You need to sign in to see this page.", and I cannot sign up for this page(or workspace).

@spf13 please fix this.
@marckhouzam
Copy link
Contributor

@marckhouzam marckhouzam commented Sep 22, 2021

You have to have a Slack account (free) and join the Gophers channel.

@umarcor
Copy link
Contributor

@umarcor umarcor commented Sep 24, 2021

I can confirm that I cannot access the Gophers workspace/channel:

image

@robberphex
Copy link
Author

@robberphex robberphex commented Sep 24, 2021

You cloud visit https://invite.slack.golangbridge.org/ to get an invitation.

I can confirm that I cannot access the Gophers workspace/channel:

image

@jpmcb
Copy link
Collaborator

@jpmcb jpmcb commented Oct 11, 2021

Thanks for bringing this to our attention! Yes - you first need to be in the Gophers slack workspace and can get an invite with the above link. Otherwise the link works, but I think this could be good to document in the contributor docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment