-
Notifications
You must be signed in to change notification settings - Fork 1
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
How we will use issues #40
Comments
Hey Elaine, Good question and thanks for asking. I closed some issues yesterday because I realized that they did not necessarily pertain to virtual teams. I think that should be the only reason to close issues (if they are not relevant to virtual teams), because if we close a relevant issue, it sort of gets lost. As far as expectations or guidelines go(@maherou might have more insights on this), I believe this is a place that I summarize relevant articles or studies that I have read and find beneficial during the summer and where we can have conversations/gain new perspectives on what we got from said article or study. However, I think the issues grew a lot more than planned (mostly Some things to know on how I ordered these issues:
If you both have any preferences on how to go about it, please let me know 👍 |
In a sense we are probably outside the normal usage of GitHub issues, so the notion of closing one may not have meaning beyond what Alex has done (closing something because it is not in scope). It seems to me that leaving these issue open indefinitely might be the right approach. It is easy to view all issues, even closed ones, even if doing so is not part of the default view. So, even if we close them, we can find them later. |
It did seem to me that we have been using issues outside of the normal usage--so I'm glad you pointed that out, Mike. The only think I don't like about our use of issues is that I don't know how I can leave a marker for myself (like a "read" notification) that I have seen the documents. I am trying to track all of your comments and posts, Alex, otherwise why post them, right? I suppose I could track the number of the issue -- maybe that will help. Any suggestions @maherou? |
You know what @maherou @amoralesg001, unless you object, I will create a label for myself that says something like "Elaine read." How does this sound? 👽 |
I was thinking exactly that before I read this message.
On Aug 4, 2020, at 6:24 PM, Elaine Raybourn <[email protected]> wrote:
You know what @maherou<https://github.com/maherou> @amoralesg001<https://github.com/amoralesg001>, unless you object, I will create a label for myself that says something like "Elaine read." How does this sound? 👽
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#40 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHZIS4OQFOXVEGDNHPFSZLR7CKDHANCNFSM4PTZVYGA>.
|
@maherou @elaineraybourn Yes, I think the labeling of who read what is a great idea. |
Great! I will create labels for us. How about ER, AM, and MH? Take a look at the label I created for myself. I can generate one for you, but if you want to choose your own color and avatar, you may want to do it. ;-) |
Works for me. Just added my label 👍 |
Hi Alex,
It occurred to me that it would be nice to have some guidelines on how we will "use" these issues -- for instance, what does it mean when an issue is closed versus open, and what are the expectations?
The text was updated successfully, but these errors were encountered: