-
Notifications
You must be signed in to change notification settings - Fork 6
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
Thread for CUSP winter 18-19 check in meetings #9
Comments
CC @williamburgson @jianweili0 Thanks much! |
My email is [email protected] at your convenience. |
My email is [email protected]. If you are sending the slack invitation |
Great I sent the slack invite the the emails in the calendar invite. For future reference you may not want to share your email on GitHub as its public facing. Probably fine though can be an invitation to get spam mail. Thanks much! For future notes, for each meeting notes please include:
Thanks much! |
Date: December 21st, 2018 Progress: Overview
|
Date: December 28st, 2018
|
@wz1405 what was the push access issue? LMK if I can be helpful there Also curious: what were the other visualization ideas discussed? |
Hi Patrick,
I was taking the notes for the previous meeting. Jianwei came up with some
pictures of the error types he came across namely the push access issue.
Guanjia found out that certain iterations within the loop call for the API
token excessive amount of times which is greater than the GitHub API limit.
Thus, I pinned Jianwei in the Slack Channel for his clarification on the
question.
Hope you a great start to the new year,
Wenjie Zheng
…On Mon, Dec 31, 2018 at 2:18 PM Patrick Atwater ***@***.***> wrote:
@wz1405 <https://github.com/wz1405> what was the push access issue? LMK
if I can be helpful there
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AnCSFcwwmj44HPWQwHmCvmWCoLflHE-4ks5u-mMJgaJpZM4YOmaz>
.
|
Date: Jan 4th, 2019 |
@wz1405 roger. Any updates or need anything from me? |
Date: January 11st, 2019 To do list:
Technical difficulties discussed:
Visualization questions refer to "#13" |
Repo data uploaded as gov_repo_count.csv and gov_repo_spec.csv, code is uploaded as DataCollaboratives.ipynb. The notebook takes a very long time to run due to the GitHub api rate limit. |
Great! Time to get visualizing -- when do classes start btw? |
Spring semester just started today |
Sounds good. Do you all have a desire to still work on this? (Fine if not though happy to help push this forward if you want to have something for your portfolio) |
I personally would like to continue to work on this since we are in school
now, I guess we can also coordinate better for the next phrase.
Jianwei
Patrick Atwater <[email protected]> 于2019年1月29日周二 上午1:16写道:
… Sounds good. Do you all have a desire to still work on this? (Fine if not
though happy to help push this forward if you want to have something for
your portfolio)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ad9jXRbFYTCM3edwgsNT_ovnQCKHsverks5vH-c2gaJpZM4YOmaz>
.
|
Sounds good @jianweili0 any visualizations to share? Where does the dataframe you parsed live? Please feel free to push (particularly the data) to the branch you created :) |
Visualizations are still in progress, and the dataframes are outputted to csv files: gov_repo_count.csv and gov_repo_spec.csv |
Scribe takes notes. (Feel free to rotate each meeting). Each meeting notes should include:
In addition, as available throughout the week, please share data visualization results in the issue thread linked here
The text was updated successfully, but these errors were encountered: