search

UNCG-CSE / Library-Computer-Usage-Analysis

The University Libraries at UNCG currently track the state of a computer, determining whether or not a particular computer is in use. This data is compiled into a database, and a web app pulls from this database to show a map and number of available computers. As of Fall 2017, the data had not been used to determine which computers are used more frequently, aside from counting the number of times a computer transitions into/away from the 'in-use' state. This project attempts to correlate the usage of these computers with various factors, including: campus scheduling, equipment configuration, placement, population in the library, and area weather. Using this data, this project also uses machine learning to determine the best placement of computers for future allocation, and possible reconfiguration of equipment and space.
1 stars 1 forks source link

Communication #52

Closed brownworth closed 6 years ago

brownworth commented 6 years ago

As mentioned in our meeting today, we can communicate a number of different ways. I'm comfortable with the following, but this is by-no-means an exhaustive, or even ordered, list of what I'm willing to use. Please mention in the comments if there is something missing, or if you have preferences towards a particular (mentioned or unmentioned) tool.

Any thoughts?

smindinvern commented 6 years ago

I'm fine with literally anything. One thing I thought of shortly after our meeting is that it would definitely be easier for me to meet after class rather than before. If that poses challenges for any of you guys, though, before should be fine.

I would think that github issues should be more than sufficient as long as we use it extensively and reliably. Just my 2 cents.

mtellis2 commented 6 years ago

I'm fine continuing to use Issues as our communication tool, plus github notifications are sent to my email anytime something is changed or updated so it's also using email at the same time.

PatriciaTanzer commented 6 years ago

GitHub issues are still best for me. The short meetings before and after class are good for me, though if there's something extensive after (>10 min) I'll run into problems.

On Oct 23, 2017, at 15:24, Michael Ellis notifications@github.com<mailto:notifications@github.com> wrote:

I'm fine continuing to use Issues as our communication tool, plus github notifications are sent to my email anytime something is changed or updated so it's also using email at the same time.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHubhttps://github.com/UNCG-CSE/Library-Computer-Usage-Analysis/issues/52#issuecomment-338769004, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AdqT4pSXBo6Xxvdzw4I1KiQNi-ty6UiEks5svOfTgaJpZM4QDN-X.

brownworth commented 6 years ago

I am very flexible with meeting times; I work here so I'm happy to be a central point of communication, if that would help. As for the when of meeting, I can do either before or after class. I have another obligation on Mondays (and most Wednesdays) across town at 5:30, so I can't be here all that late.

smindinvern commented 6 years ago

I should be in the classroom at 3:15 on most class days (if not all), so if we can take advantage of that as a time to discuss a few things, that would also be great.

I've also arranged to take Fridays off for the rest of the semester to work on my two school projects, so if we ever need to call a longer meeting, Fridays would be the best time for me.

PatriciaTanzer commented 6 years ago

Seems like we've resolved this pretty well