You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Data Science CoP Meeting Agendas (Monday 7PM PST) #137
changed the title [-]Data Science Community of Practice Meeting Agendas (Thursday 8PM PST)[/-][+]Data Science CoP Meeting Agendas (Thursday 8PM PST)[/+]on Jan 5, 2022
I tried to update the agenda with ChatGPT and Claude, but neither could access the comment content of the issues with their connectors. I'm upset about it. It was working last week. It says now:
|
What’s missing / why
The issue comment sections often aren’t exposed to web search indexing (GitHub sometimes hides or doesn’t index full comment threads).
The specific lines you wanted (last two comments with blockers & ETA) were not accessible publicly in the crawled content.
Some links (e.g. ai-skills-assessor #3, #152) did not surface in search results that show comment context.
I just had surgery and am feeling sick, I will be able to do the meeting checking everybody's issues. Unfortunately the agenda isn't updated.
I tried to update the agenda with ChatGPT and Claude, but neither could access the comment content of the issues with their connectors. I'm upset about it. It was working last week. It says now: | What’s missing / why
The issue comment sections often aren’t exposed to web search indexing (GitHub sometimes hides or doesn’t index full comment threads).
The specific lines you wanted (last two comments with blockers & ETA) were not accessible publicly in the crawled content.
Some links (e.g. ai-skills-assessor #3, #152) did not surface in search results that show comment context.
I just had surgery and am feeling sick, I will be able to do the meeting checking everybody's issues. Unfortunately the agenda isn't updated.
Unfortunately there must have been a change to the ChatGPT connector (and Claude, so Github did it) to Github. GPT said:
"GitHub access is working for the repo, but the connector doesn’t expose per-issue comments directly."
When I tried to update the agenda as a web scrape via GPT it said:
"I retried via web (no connector) and pulled what GitHub would serve publicly. GitHub’s issue pages load most timeline items via client-side JS, so full comment text isn’t accessible to scraping without being signed in. I still captured any visible status/labels and updated entries accordingly; where the last-month comments were not exposed, I preserved your original notes and marked them as “no public comment content retrievable.”" no comments were found at all.
I don't know what their concern was to un-expose the comments (maybe these spammy hawkers/solicitors ruined it by posting ads with GPT on publlic issues, we've seen it before) but the agendas can no longer be updated automatically. Rather than spend an hour going through every issue and then going through it again during the CoP meeting, I'm going to ask Bonnie if I can do the agenda a different way.
I wrote myself a small agenda which I will post after I fill it out with people's updates. This seems to me to be the better way rather than posting the agenda before the meeting and not knowing what happened.
Here is the results of my issue review and the updates from the DS CoP meeting:
#198 : max1million101 : I unassigned him we haven’t heard from this guy in a long time. #155 : nehathombare : didn’t attend #145 : xuyeluo : is doing great work next is a chapter on strings #154 : akiokaki : asked for update, can’t attend #153 : chinaexpert1 : Closed the issue this was moved to an Epic with sub-issues #157 : lindaworksondata : asked for update
She has done a good job with comments, a readme, and more conceptual discussion in the google doc. So I assigned @naveen3par to review #218 : sauravchangde : didn’t attend, but we are at a dead end finding the data if he comes back I’ll give him a new issue. #228 : ashhik96 : has a good dashboard building up, showing for instance that females are underrepresented in his sample. I told him to develop the hypotheses and do more exploration in preparation of a report that will be presented to the CoP and then, after feedback, turned into a GitHub action to keep tabs on these facts #177 : mru-hub : asked for update, she has done the script, basically finished the issue. #135 : venkata-sai-swathi and ayushpatel1501 : asked for update #130 : parcheesime : had an emergency at home will update next week #146: parcheesime : we still need the link to the repo to initiate transfer #118 : parcheesime : asked for update #45 : assigned myself to prepare for another volunteer #44 : Adaakal : Bonnie answered her questions, she needs to chunk the request to observe API limits, it also needs to be moved out of the 311 repo into its own appropriately titled repo, she will do that, after all that this will become a GitHub action. #107 : ssejal : asked for update, didn’t attend #223 : chinaexpert1 : I need a reviewer, haven’t assigned yet #179 : I asked for the files from pranjaliseth , didn’t attend #71 :Gvelis10 : created a document to track her work and you are adding graphs to it. She met with Bonnie in a breakout room. #152 : naveen3par : Bonnie saw they updated their website of climate projects. Now Naveen has to write a formula to make the last commit column filterable, so we can get closer to creating a dashboard to help people find active climate projects.
UPDATE THIS PART OF WIKI with links
• Compare to the Skills labels from our Internship dashboard, and provide a list of skills that apply for that user on that issues' history.
I don't know what do about this need clarification.
We need to find all the issues regarding 311-data-jupyter-notebooks repo and get them wrangled so nothing is being forgotten.
UPDATE THIS PART OF WIKI with links
• Compare to the Skills labels from our Internship dashboard, and provide a list of skills that apply for that user on that issues' history.
Here is the results of my issue review and the updates from the DS CoP meeting:
Activity
akhaleghi commentedon Nov 19, 2021
2021-11-18
akhaleghi commentedon Nov 19, 2021
2021-12-02
akhaleghi commentedon Dec 3, 2021
2021-12-09
akhaleghi commentedon Dec 17, 2021
2021-12-16
[-]Data Science Community of Practice Meeting Agendas (Thursday 8PM PST)[/-][+]Data Science CoP Meeting Agendas (Thursday 8PM PST)[/+]akhaleghi commentedon Jan 7, 2022
2022-01-06
akhaleghi commentedon Jan 14, 2022
2022-01-13
ExperimentsInHonesty commentedon Jan 20, 2022
add talking about this to the agenda. Its from Mike https://github.com/researchsherpa/graffiti-viz
56 remaining items
chinaexpert1 commentedon Sep 30, 2025
I tried to update the agenda with ChatGPT and Claude, but neither could access the comment content of the issues with their connectors. I'm upset about it. It was working last week. It says now:
|
What’s missing / why
The issue comment sections often aren’t exposed to web search indexing (GitHub sometimes hides or doesn’t index full comment threads).
The specific lines you wanted (last two comments with blockers & ETA) were not accessible publicly in the crawled content.
Some links (e.g. ai-skills-assessor #3, #152) did not surface in search results that show comment context.
I just had surgery and am feeling sick, I will be able to do the meeting checking everybody's issues. Unfortunately the agenda isn't updated.
chinaexpert1 commentedon Sep 30, 2025
the AISA team needs another meeting with Bonnie to get next steps/tasks. I'll schedule one with Bonnie for this week.
@sandy3w
@sauravchangde
@naveen3par
@ashhik96
@mru-hub
@Gvelis10
@xuyeluo
were in attendance and gave great updates.
from the old agenda, we have lots of things hung up on people who no longer attend...something to address.
chinaexpert1 commentedon Oct 6, 2025
Unfortunately there must have been a change to the ChatGPT connector (and Claude, so Github did it) to Github. GPT said:
"GitHub access is working for the repo, but the connector doesn’t expose per-issue comments directly."
When I tried to update the agenda as a web scrape via GPT it said:
"I retried via web (no connector) and pulled what GitHub would serve publicly. GitHub’s issue pages load most timeline items via client-side JS, so full comment text isn’t accessible to scraping without being signed in. I still captured any visible status/labels and updated entries accordingly; where the last-month comments were not exposed, I preserved your original notes and marked them as “no public comment content retrievable.”" no comments were found at all.
I don't know what their concern was to un-expose the comments (maybe these spammy hawkers/solicitors ruined it by posting ads with GPT on publlic issues, we've seen it before) but the agendas can no longer be updated automatically. Rather than spend an hour going through every issue and then going through it again during the CoP meeting, I'm going to ask Bonnie if I can do the agenda a different way.
chinaexpert1 commentedon Oct 14, 2025
I wrote myself a small agenda which I will post after I fill it out with people's updates. This seems to me to be the better way rather than posting the agenda before the meeting and not knowing what happened.
chinaexpert1 commentedon Oct 14, 2025
Here is the results of my issue review and the updates from the DS CoP meeting:
#198 : max1million101 : I unassigned him we haven’t heard from this guy in a long time.
#155 : nehathombare : didn’t attend
#145 : xuyeluo : is doing great work next is a chapter on strings
#154 : akiokaki : asked for update, can’t attend
#153 : chinaexpert1 : Closed the issue this was moved to an Epic with sub-issues
#157 : lindaworksondata : asked for update
She has done a good job with comments, a readme, and more conceptual discussion in the google doc. So I assigned @naveen3par to review
#218 : sauravchangde : didn’t attend, but we are at a dead end finding the data if he comes back I’ll give him a new issue.
#228 : ashhik96 : has a good dashboard building up, showing for instance that females are underrepresented in his sample. I told him to develop the hypotheses and do more exploration in preparation of a report that will be presented to the CoP and then, after feedback, turned into a GitHub action to keep tabs on these facts
#177 : mru-hub : asked for update, she has done the script, basically finished the issue.
#135 : venkata-sai-swathi and ayushpatel1501 : asked for update
#130 : parcheesime : had an emergency at home will update next week
#146: parcheesime : we still need the link to the repo to initiate transfer
#118 : parcheesime : asked for update
#45 : assigned myself to prepare for another volunteer
#44 : Adaakal : Bonnie answered her questions, she needs to chunk the request to observe API limits, it also needs to be moved out of the 311 repo into its own appropriately titled repo, she will do that, after all that this will become a GitHub action.
#107 : ssejal : asked for update, didn’t attend
#223 : chinaexpert1 : I need a reviewer, haven’t assigned yet
#179 : I asked for the files from pranjaliseth , didn’t attend
#71 :Gvelis10 : created a document to track her work and you are adding graphs to it. She met with Bonnie in a breakout room.
#152 : naveen3par : Bonnie saw they updated their website of climate projects. Now Naveen has to write a formula to make the last commit column filterable, so we can get closer to creating a dashboard to help people find active climate projects.
For the next agenda (these didn’t get answered)
• Assignee: [naveen3par](https://github.com/naveen3par)
o Issue: [Fixing Looker Dashboard Disconnection from Google Sheets #224](#224)
o Help: Bonnie to get them access today; ETA 1 week after access.
• Assignee: [ashhik96](https://github.com/ashhik96)
o Issue: [Create a Data Scientist’s Roadmap #228](#228)
o Next step: bring draft to CoP for review.
• Assignees: [ExperimentsInHonesty](https://github.com/ExperimentsInHonesty) & [chinaexpert1](https://github.com/chinaexpert1)
o Issue: [Template using ChatGPT for tutorials #223](#223)
o Next step: test with current authors.
We need to find all the issues regarding 311-data-jupyter-notebooks repo and get them wrangled so nothing is being forgotten.
New Code Self-Review Checklilst
https://github.com/hackforla/data-science/wiki/Self%E2%80%90Review-Checklist-for-Code-Commits
Need to provide education on this at the CoP meeting (keep forgetting to do that)
a note for the next agenda:
We need to find all the issues regarding 311-data-jupyter-notebooks repo and get them wrangled so nothing is being forgotten.
chinaexpert1 commentedon Oct 21, 2025
New Code Self-Review Checklilst
https://github.com/hackforla/data-science/wiki/Self%E2%80%90Review-Checklist-for-Code-Commits
(I don't know what to do about this very few people attended I have slacked it to Jason and Sandy3w
• Assignee: [ashhik96](https://github.com/ashhik96)
o Issue: [Create a Data Scientist’s Roadmap #228](#228)
o Next step: bring draft to CoP for review.
• Assignees: [ExperimentsInHonesty](https://github.com/ExperimentsInHonesty) & [chinaexpert1](https://github.com/chinaexpert1)
o Issue: [Template using ChatGPT for tutorials #223](#223)
o Next step: test with current authors.
Here is the results of my issue review and the updates from the DS CoP meeting:
I don't know what do about this need clarification.
chinaexpert1 commentedon Oct 23, 2025
FIRST during the meeting...everyone register for the meetings:
https://us06web.zoom.us/meeting/register/EdQprMkzQd2rBhbR3bvwBg
chinaexpert1 commentedon Oct 28, 2025
New Code Self-Review Checklilst
https://github.com/hackforla/data-science/wiki/Self%E2%80%90Review-Checklist-for-Code-Commits
(I don't know what to do about this very few people attended I have slacked it to Jason and Sandy3w
• Assignee: [ashhik96](https://github.com/ashhik96)
o Issue: [Create a Data Scientist’s Roadmap #228](#228)
o Next step: bring draft to CoP for review.
• Assignees: [ExperimentsInHonesty](https://github.com/ExperimentsInHonesty) & [chinaexpert1](https://github.com/chinaexpert1)
o Issue: [Template using ChatGPT for tutorials #223](#223)
o Next step: test with current authors.
Here is the results of my issue review and the updates from the DS CoP meeting:
I don't know what do about this need clarification.
chinaexpert1 commentedon Nov 11, 2025
New Code Self-Review Checklilst
https://github.com/hackforla/data-science/wiki/Self%E2%80%90Review-Checklist-for-Code-Commits
(I don't know what to do about this very few people attended I have slacked it to Jason and Sandy3w
Here is the results of my issue review and the updates from the DS CoP meeting:
CoP: Data Science: Create Data Analysis With R Tutorial #145 : xuyeluo : did string manipulation. I told him he has to get to statistical analysis quick - it's already 2000 lines.
CoP: Data Science: Create Data Ops Tutorial #154 : akiokaki : unassigned
Housing Rental/sales Prices in LA County Post Fires: Zillow #218 : sauravchangde : didn't come
MediaWiki API Project: Underrepresented Groups #228 : ashhik96 : will present next week
Create 311 data CSV files that can be accessed through a Jupyter notebook #177 : mru-hub : didn't come, Bonnie should look at it and close if satisfied
Create a Guide: Web Scraping #130 : parcheesime : asked for update
Create Web Scraping Tutorial #146: parcheesime : this is a dupe issue i just keep it here in case she posts there by accident
CoP: Data Science: Create district types reusable tool (API, single dataset, etc.) #118 : parcheesime : she provided update no blockers
CoP: Data Science: Native Land Attribution #45 : unassigned myself now it is in backlog
Neighborhood Council Website technologies #44 : Adaakal : needs more time to work on script before building dashboard
CoP: Data Science: Analyze correlations between metro locations and 311-data requests #107 : ssejal : provided update she's getting a presentation ready.
CoP: Data Science: Create a Networking/ Speaker Invitation Guide #223 : chinaexpert1 : I need a reviewer, got Chelsea
CoP: Data Science: City of Los Angeles Evictions #179 : pranjaliseth
Hack for LA Membership Insights live-dashboard-automation#70 : Gvelis10 : closed and tasks moved to feat: add hso revoked table #71
Transfer Meet Up Data to Google Sheets for Live Updates live-dashboard-automation#71 :Gvelis10 : building dashboard
CoP: Data Science: Open Source Projects Data Set for Climate projects #152 : naveen3par : ready to build dashboard
CoP: Data Science: Create Deep Learning Tutorial #157 : lindaworksondata : I asked for update
AISA :
Unit Test Research ai-skills-assessor#19 : waiting for Bonnie to close.
Isolate the two longest issues in issue_comments.json for Bonnie to consider ai-skills-assessor#23 : Closed as completed
Update Project ReadMe ai-skills-assessor#6 : ASSIGNED MYSELF
Repo labeler script documented in the repo's Wiki ai-skills-assessor#41 : added me as a reviewer
Comments and Issues scripts documented in the Wiki ai-skills-assessor#40 : added me as a reviewer
I don't know what do about this need clarification.
chinaexpert1 commentedon Nov 11, 2025
I need to ask Bonnie what to do about these next Monday:
hackforla/ai-skills-assessor#5
UPDATE THIS PART OF WIKI with links
• Compare to the Skills labels from our Internship dashboard, and provide a list of skills that apply for that user on that issues' history.
I don't know what do about this need clarification.
chinaexpert1 commentedon Nov 18, 2025
DS CoP meeting results: 11/17/25
New Code Self-Review Checklilst
https://github.com/hackforla/data-science/wiki/Self%E2%80%90Review-Checklist-for-Code-Commits
(I don't know what to do about this very few people attended I have slacked it to Jason and Sandy3w
QUESTIONS I NEED TO ASK BONNIE:
Note from today - she said get zoom stuff needed to start Next Monday's meeting
I need to get UIUX speaker consent form brought over to DS and the powerpoint template
1I need to ask Bonnie what to do about these next Monday:
hackforla/ai-skills-assessor#5
UPDATE THIS PART OF WIKI with links
• Compare to the Skills labels from our Internship dashboard, and provide a list of skills that apply for that user on that issues' history.
Here is the results of my issue review and the updates from the DS CoP meeting:
CoP: Data Science: Create Data Analysis With R Tutorial #145 : xuyeluo : didnt attend
CoP: Data Science: Create Data Ops Tutorial #154 : akiokaki : unassigned
Housing Rental/sales Prices in LA County Post Fires: Zillow #218 : sauravchangde : didnt attend
MediaWiki API Project: Underrepresented Groups #228 : ashhik96 : great presentation needs to create a Wiki page - description of the project
Create 311 data CSV files that can be accessed through a Jupyter notebook #177 : mru-hub : Bonnie should look at it and close if satisfied
Create a Guide: Web Scraping #130 : parcheesime : didnt attend
Create Web Scraping Tutorial #146: parcheesime : this is a dupe issue i just keep it here in case she posts there by accident
CoP: Data Science: Create district types reusable tool (API, single dataset, etc.) #118 : parcheesime : didnt attend
CoP: Data Science: Native Land Attribution #45 : unassigned now it is in backlog
Neighborhood Council Website technologies #44 : Adaakal : couldnt make it updated her issue
CoP: Data Science: Analyze correlations between metro locations and 311-data requests #107 : ssejal : didnt atend
0 Tutorial Template creation #225 : tutorial template kinda on hold for now
CoP: Data Science: Create a Networking/ Speaker Invitation Guide #223 : chinaexpert1 : I need to get UIUX speaker consent form brought over to DS and the powerpoint template
Job trends in software development by term frequency #226 : nadiaspn0503 : unassigned
CoP: Data Science: City of Los Angeles Evictions #179 : pranjaliseth
Hack for LA Membership Insights live-dashboard-automation#70 : Gvelis10 : closed and tasks moved to feat: add hso revoked table #71
Transfer Meet Up Data to Google Sheets for Live Updates live-dashboard-automation#71 :Gvelis10 : didnt attend
CoP: Data Science: Open Source Projects Data Set for Climate projects #152 : naveen3par : working on dashboard, got clarification
CoP: Data Science: Create Deep Learning Tutorial #157 : lindaworksondata : putting it in the wiki
Smair Ali is choosing a sub issue from Epic: MediaWiki Data Science Projects #191
AISA :
Unit Test Research ai-skills-assessor#19 : waiting for Bonnie to close.
Isolate the two longest issues in issue_comments.json for Bonnie to consider ai-skills-assessor#23 : Closed as completed
Update Project ReadMe ai-skills-assessor#6 : ASSIGNED MYSELF
Repo labeler script documented in the repo's Wiki ai-skills-assessor#41 : added me as a reviewer
Comments and Issues scripts documented in the Wiki ai-skills-assessor#40 : added me as a reviewer
Rabia2219 commentedon Dec 4, 2025