Epic: Send users to our community #10128
Comments
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
gtsiolis
added
meta: never-stale
|
Unfortunately this was not completed this quarter, will put on the roadmap backlog for future consideration. |
|
What are the expected changes in IDE to make^ this possible? |
|
@svenefftinge I'd love to work on this, how would we want to go about this? One suggestion could be linking our gitpod-samples repository and the discord community's link in the following places...
And adding some more context about how to go about asking questions as well in and around here somewhere... Would love to have your suggestions and work on getting our community resources more visible! |
|
In regards of IDE we have already kind of similar links like follow on to witted and go to community, but we consider removing them or making less prominent. Stats for last year showed that they are not used like 100 clicks a year or something for all users. There were complaints that prominent places should be used for actions facilitating work, ie stop workspace, manage timeouts and etc. We already have crowded command palette and remote indicator. |
|
Regarding the above comment, @Palanikannan1437. We are talking about this:
I Agree with @akosyakov that people are not using it. And, command palette is already have multiple options 😅 |
|
Woahhh..I had no idea the IDE had such a feature...pretty neat indeed! But I'm not sure if this is a feature I'd use regularly...but it might come in handy though to switch to discord quickly, not sure if that's the use case we were talking about in this issue 😅 As for new users discovering our community, it might be a bit difficult to discover it via the command palette but rather while exploring the docs I suppose? What are your suggestions about showing this on the docs as suggested above! @Siddhant-K-code @akosyakov |
We Kind of shows the command palette options in our VS Code Docs. Regarding community, Now, we already have this on our website
Regarding GitHub Repo, we have this callout on the top: |
Ohhh!! I see, in my case I discovered our discord community via Twitter... didn't scroll upto the footer 🙈... I meant showing the gitpod-samples repo with all the public resources, tools and templates😅 In this case, do we consider closing this issue? |
Summary
The gitpod community is a super helpful resource and we should make our users more aware of their existance.
Context
Users should not doubt how and where to ask questions, suggest features or even contribute to Gitpod.
After all, Gitpod is open-source, developed openly and sports a super friendly and engaging community.
We have two places we should send users:
Value
Users learn about the community and can engage with it, by learning about possibilities and solutions others have found.
Acceptance Criteria
More users engage on Discord and this repository (starring, issues, PRs).
Measurement
Increase growth of activity and number of users on Discord and GitHub (measure starring).
Growth Area
No response
Persona(s)
No response
Hypothesis
Engagement within the community allows for shorter help cycles and increases the emotional bond with Gitpod.
In scope
No response
Out of scope
No response
Complexities
No response
Press release
No response
The text was updated successfully, but these errors were encountered: