-
Notifications
You must be signed in to change notification settings - Fork 333
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
A simple idea to improve communication #2562
Comments
I agree with this. Keeping up with the chat during busy times can be a challenge. Maybe we can make this suggestion more visible with advice on the appropriate individuals to be tagged. |
I think your suggestion is going to be great because people will not just read the comment only and force them to make a reply on whatever comment their name is a tagged. |
@lmmrsa I would like to be assigned this issue. My proposed solution:I would like to add a note about this new convention to the Github issues page, or directly to the overview first steps page (The main one with the links to the individual steps). This issue is likely something a lot of first step interns have issues with. I have had 3 open issues for 5 days now and, while one has gotten commented on, none have gotten the okay from an active intern to work on. In my opinion, instantiating this as a new convention could possibly help expedite the first steps process. Screenshots |
A great approach to solving this problem @bradlet |
I think this is a great idea for us on the first steps to being an intern |
This looks like a good idea - do we know when this will be implemented? |
@nvrqt03 It does not really need implementation in that sense. It is a way for everyone to communicate better. It is suggesting everyone do so whenever trying to communicate. |
@bradlet @ChiragAwale Is bradlet still working on this issue or Can I help you in making the proposed changes |
It's a great suggestion! |
@dogi i should have done this in my profile PR #3141 (comment) |
…e#2561) (open-learning-exchange#2562) Co-authored-by: dogi <dogi@users.noreply.github.com>
Problem
Comments on PRs and Issues dont get read and replied as often
Steps to reproduce the problem
N/A
Screenshots
N/A
Proposed solution
I think tagging the person you are replying to in, 'Github comment itself', is a really good way which can be used alongside posting on Gitter chat to get faster responses as it will help us admins/interns to efficiently find those comments, and places where responses are required.
The text was updated successfully, but these errors were encountered: