Skip to content

Update the schedule of NumPy triage calls#226

Merged
stefanv merged 1 commit intoscientific-python:mainfrom
InessaPawson:numpy-triage-schedule
Mar 21, 2022
Merged

Update the schedule of NumPy triage calls#226
stefanv merged 1 commit intoscientific-python:mainfrom
InessaPawson:numpy-triage-schedule

Conversation

@InessaPawson
Copy link
Copy Markdown
Member

The start time of NumPy triage calls is moving to 16:00 UTC as of March 23rd, 2022. This PR will update the calendar to reflect the change.

The start time of NumPy triage calls is moving to 16:00 UTC as of March 23rd, 2022. This PR will update the calendar to reflect the change.
@netlify
Copy link
Copy Markdown

netlify Bot commented Mar 21, 2022

✅ Deploy Preview for scientific-python-org ready!

🔨 Explore the source changes: 58f2868

🔍 Inspect the deploy log: https://app.netlify.com/sites/scientific-python-org/deploys/6237dd30a40f6b00096caee0

😎 Browse the preview: https://deploy-preview-226--scientific-python-org.netlify.app/reports/lighthouse

Comment thread calendars/numpy.yaml
Comment on lines +22 to +23
begin: 2022-03-23 16:00:00 +00:00
end: 2022-03-23 17:00:00 +00:00
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this remove the past meetings from the calendar? Not sure this is a problem but I was just wondering if we want to keep past meetings in the calendar or not... Maybe this is irrelevant as long as we have meeting notes.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this would remove them. Personally I don't think it matters, unless there are compliance reasons. Otherwise we could make multiple entries per calendar.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good then!

@jarrodmillman jarrodmillman requested review from stefanv and tupui March 21, 2022 14:28
Copy link
Copy Markdown
Member

@tupui tupui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @InessaPawson. LGTM, but letting others have a look before merging regarding @melissawm's point.

Comment thread calendars/numpy.yaml
Comment on lines +22 to +23
begin: 2022-03-23 16:00:00 +00:00
end: 2022-03-23 17:00:00 +00:00
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this would remove them. Personally I don't think it matters, unless there are compliance reasons. Otherwise we could make multiple entries per calendar.

@stefanv stefanv merged commit 0de2b1b into scientific-python:main Mar 21, 2022
@InessaPawson InessaPawson deleted the numpy-triage-schedule branch June 12, 2022 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants