-
Notifications
You must be signed in to change notification settings - Fork 229
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
July 28 2021 Project Team Meeting #2159
Comments
Hello there @mariajoafana. I've joined the team today, and would be interested to speak with you about contributing to the Project Team Meeting! Let me know when you have scope to connect. |
Sure @Anisa-ProgHist I'll contact you via email so we can coordinate |
I now can't make this, apologies. |
Team Name: ProgHist By: Adam Crymble Date: 28 July 2021 Actions Completed Since Previous Report:
Actions Remaining Open Since Previous Report:
Queries for the Editorial Board:
6-month focus:
12+ month focus:
|
Technical Team ReportBy: @ZoeLeBlanc Date: 28 July 2021 Actions Completed Since Previous Report:
Substantive Actions Remaining Open Since Previous Report:
6-month focus:
12+ month focus:
|
FR Team Reportby @spapastamkou on 28 July 2021 Actions Completed Since Previous Report - New Actions: Actions Remaining Open Since Previous Report: Other Queries for the Editorial Board: 6-month focus: 12+ month focus: |
Communications Team ReportBy: @jenniferisasi Date: 28 July 2021 Actions Completed Since Previous Report:
Substantive Actions Remaining Open Since Previous Report:
6-month focus:
|
ES Team Reportby @rivaquiroga on 28 July 2021 Actions Completed Since Previous Report
Actions Remaining Open Since Previous Report:
3-month focus:
|
Dear @mariajoafana and dear all, Thank you for your time yesterday. I have added the Minutes to our private repository. They are available for you to view via this link: Please let me know if you feel I have missed any important points, or mis-represented something which you said. I will be happy to make adjustments. Very best, |
@Anisa-ProgHist you've done a brilliant job. Just one very minor note that this line doesn't technically apply to the "Project Team" (only to ProgHist): Quorum of 3 reached (per Article 9 of the Articles of Association). |
Ah! Thank you, @acrymble! Didn't realise this. I will remove that statement. |
July 28 2021, Time is 9:00 AM - Colombia, Mexico; 10:00AM EDT; 3:00 PM - London, Portugal; 4:00 PM CET - Paris. @mariajoafana will be facilitating the call.
You can use this time converter to double-check the time of the meeting in your time zone: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210728T1400
Zoom invitation: https://uniandes-edu-co.zoom.us/j/89661075902
Working agenda in progress. Please add in this agenda under "Issues and tasks for discussion" the tickets that you'll like to further discuss in the meeting. You can comment or edit this comment directly.
All team leaders please post a small report on your team's activities closer that day.
Actions Arising from May 2021 Project Team Meeting: Actions arising from May 2021 Meeting #2158
Issues and tasks for discussion:
@drjwbaker and @hawc2 on how to test and implement perma.cc for archiving project's weblinks Could perma.cc help PH keep weblinks sustainable? #2030
Team Leader - Terms & Selection Process #1986 - Team Leader Selection Process @acrymble @nabsiddiqui
Update from AGM: ProgHist Business Plan 2021 @acrymble - including new goal proposal by @spapastamkou on legal matters (Paper B ProgHist Business Plan 2021 AGM.pdf)
Update from AGM: ProgHist Service Agreement Terms 2021 @acrymble (https://github.com/programminghistorian/jekyll/wiki/Service-Agreement-Publisher-and-Publications)
Discussing a 3, 5, & 10 year plan @acrymble
Updates on tickets open for a long time with no clear path to completion:
@Anisa-ProgHist Proposal for new system to use Labels to identify:
Issues which represent Priority Actions arising from Project Team Meetings (relating to Item above)
Issues which are Closed but remain On Hold (to pick up again in the future)
@Anisa-ProgHist question of where best to save Project Team Meeting minutes so that they remain accessible to all
The text was updated successfully, but these errors were encountered: