Skip to content
This repository has been archived by the owner on Oct 10, 2024. It is now read-only.

fix: removed tech channels #8669

Merged
merged 1 commit into from
Feb 12, 2024
Merged

fix: removed tech channels #8669

merged 1 commit into from
Feb 12, 2024

Conversation

eddiejaoude
Copy link
Member

closes #ISSUE-NO

What does this PR do?

Description of the task to be completed?

How can this be manually tested?

Any background context you want to provide?

Is there any relevant issue to this PR?

Screenshots (if appropriate)

Questions

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's great having you contribute to this project

Welcome to the community 🤓

If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord Server and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

TECH: Channels regarding specific areas

- **#frontend**, **#backend**, **#devops**, **#tech-other**

You can raise an issue or a Pull request here https://github.com/EddieHubCommunity/support/blob/main/docs/discord/discord-readme.md
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I belive correct url in this line should be: https://github.com/EddieHubCommunity/support/blob/main/docs/discord/discord-readme.md

@LeaDevelop
Copy link
Contributor

Looking at the entire file, from what I can tell there are some discord channels that are are missing in list or they to much. Which leads me to wonder, if they get unlocked at certain level for new members?

@eddiejaoude
Copy link
Member Author

Looking at the entire file, from what I can tell there are some discord channels that are are missing in list or they to much. Which leads me to wonder, if they get unlocked at certain level for new members?

Thanks Lea! It could be they got out of sync, could you let me know which ones you noticed are different?

Copy link
Contributor

@LeaDevelop LeaDevelop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed tech channels attempt looks legit to me, would approve, unless you'd like to make further changes and expand the scope of the PR itself?

@@ -64,10 +64,6 @@ TEXT CHANNELS: These consist of the server's main text channels, that are for di

- **#public-speaking**: improve your soft skills, public speaking, and build communities

TECH: Channels regarding specific areas
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed tech channels attempt looks legit to me, would approve, unless you'd like to make further changes and expand the scope of the PR itself?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like to keep PRs small if possible, so happy to merge and further changes can come in another PR

@LeaDevelop
Copy link
Contributor

Looking at the entire file, from what I can tell there are some discord channels that are are missing in list or they to much. Which leads me to wonder, if they get unlocked at certain level for new members?

Thanks Lea! It could be they got out of sync, could you let me know which ones you noticed are different?

Sure thing, on it now

@eddiejaoude
Copy link
Member Author

@LeaDevelop if you prefer, maybe I merge this PR and you can raise a new PR? Let me know what you prefer

@LeaDevelop
Copy link
Contributor

Looking at the entire file, from what I can tell there are some discord channels that are are missing in list or they to much. Which leads me to wonder, if they get unlocked at certain level for new members?

Thanks Lea! It could be they got out of sync, could you let me know which ones you noticed are different?

This is what I currently see with my entry level without touching the Browse Channels option in the discord (I used that now and can see them all). Screenshot took before I touched Browse Channels option
eddihub-discord

My discord level according to Becca Lyria bot is 3.
I would propose that you list all channels and their descriptions members are able to reach and also mention to take a look at Browse Channel to see all other channels.
If you lock some channels after certain level of activity, would also list and explain what action has to be taken to reach it :)

Summary:

  • would add disclaimer to use Browse Channels feature to find full channel list.
    • perhaps natural flow for others. I use discord for +8 years and still missed it haha
  • would list all channels, so people know what they can find and if they don't see it, they'll eventually look around and find the Browse Channels which empowers summary point one
  • consider helper role in future, or add disclaimer high chance you'll get tagged if you use certain roles. I joined community and read through initial code of conduct and had idea that it'll be vibrant interactive journey but not sure if all perceive the entry into your community like that (Most common in my surroundings when I talk to people, they join discord servers and before anything else is done, they mute server for any pinging and that's understanding when you are in 10 ore more servers, discord goes brrrrrr 😅)

GENERAL DISCUSSION
#readme - ⚠️ this one is not listed and explained currently
#roles - ⚠️it only enlists if one enters it via readme channel and then it vanishes. BTW I didn't realize that if I pick certain role in the discord channel, members will assume I am expert in that area. Have you considered adding a helper role, if people want to be tagged for topics, although that may not really solve the problem, cos you'd have to separate interested into topic and able and willing to help on specific topic :) long separate topic, no need to address here.
#general ✔️
#help ✔️
#content-share - ⚠️ this one I see after using Browse Channels feature
#career - ⚠️ this one is currently not listed and explained
#bot-chat - ⚠️ this one I see after using Browse Channels feature

DAILY
#standup ✔️
#wellness ✔️
#achievements - ⚠️ this one I see after using Browse Channels feature

COMMUNITY DISCUSSION
#ideas ✔️
#first-timers ✔️
#public-speaking ✔️
#maintainers - ⚠️ this one is not explained in the file
#hackathons - ⚠️ this one i don't see, maybe cos of my entry level

RadioEddieStage 00/99 - ⚠️ Maybe also add description here, is this for hangout when you got events going on? Which also leads me to question do you consider having create channels on demands for members, when they help each other, or does all run through pull requests and text chat? Sometimes it's easier to convey via screen share and being able to explain show, explain and discuss problem via voice.

Locked channels
#TeamEddie
#Maintainers
#Sponsors

@LeaDevelop
Copy link
Contributor

LeaDevelop commented Feb 11, 2024

@LeaDevelop if you prefer, maybe I merge this PR and you can raise a new PR? Let me know what you prefer

I think that'd be a best flow yeah :)

I set me reminder and will create issue and PR in one of the upcoming three days, heading off for today :)

@eddiejaoude
Copy link
Member Author

eddiejaoude commented Feb 12, 2024

That is very well written Lea! 👍 thank you!

I set me reminder and will create issue and PR in one of the upcoming three days, heading off for today :)

Thank you! I have created an issue #8671, please comment in the issue and then GitHub will let me assign it to you

@eddiejaoude eddiejaoude merged commit ecc4086 into main Feb 12, 2024
5 checks passed
@eddiejaoude eddiejaoude deleted the eddiejaoude-patch-1 branch February 12, 2024 07:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants