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

How we will use issues #40

Open
elaineraybourn opened this issue Aug 3, 2020 · 8 comments
Open

How we will use issues #40

elaineraybourn opened this issue Aug 3, 2020 · 8 comments
Assignees
Labels
AM 🌊 ER 👽 Elaine has read this paper and/or comment. shared knowledge

Comments

@elaineraybourn
Copy link
Collaborator

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?

@amoralesg001
Copy link
Collaborator

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
because I think summarizing and posting what I read, personally helps me to retain information. So, I have tried to post in this repo as much as possible). I have no expectations that you will read all of these issues. I know you both are very busy. At first, I always assigned @elaineraybourn and @maherou to issues that I posted, but that fills up people's email notification on the issue. In finding ways to limit that, I have begun to only mention either of you two in the issue if I would like feedback or if I think said article or study has a good point. Otherwise, if you think the article or study sounds interesting please go right ahead and give me any feedback you would like -- I have found most of these articles interesting to read and think both you would as well.

Some things to know on how I ordered these issues:

  • The name of each issue, is always the name of the article along with the year it was made (a part from the issues I reposted from our previous repo).
  • labels help to give an idea of what the article will be talking about or topics it will include.

If you both have any preferences on how to go about it, please let me know 👍

@maherou
Copy link
Contributor

maherou commented Aug 4, 2020

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.

@elaineraybourn
Copy link
Collaborator Author

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?

@elaineraybourn
Copy link
Collaborator Author

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? 👽

@maherou
Copy link
Contributor

maherou commented Aug 5, 2020 via email

@amoralesg001
Copy link
Collaborator

@maherou @elaineraybourn Yes, I think the labeling of who read what is a great idea.

@elaineraybourn
Copy link
Collaborator Author

elaineraybourn commented Aug 10, 2020

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. ;-)

@elaineraybourn elaineraybourn added the ER 👽 Elaine has read this paper and/or comment. label Aug 10, 2020
@amoralesg001
Copy link
Collaborator

Works for me. Just added my label 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AM 🌊 ER 👽 Elaine has read this paper and/or comment. shared knowledge
Projects
None yet
Development

No branches or pull requests

3 participants