-
Notifications
You must be signed in to change notification settings - Fork 44
CAL: SPEC meeting is now bimonthly #794
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
CAL: SPEC meeting is now bimonthly #794
Conversation
✅ Deploy Preview for scientific-python-org ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for scientific-python-org ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
What happens if you duplicate the entry? Does that not work? |
I had problems with adding an end date for the first batch. |
We should add a Tools calendar. I missed this PR and opened an new one: #798 |
Do we need to keep the old calendar? If it is going to cause problems, let's just focus on the calendar being correct going forward. |
I think it would be nice to keep the old one, but I couldn't figure out how to do it. |
@stefanv - is there a way to keep the old entry (e.g. an
end
field that shows when the last entry is rather than when the end of the individual meeting is) and add a new one with the same name?