Meeting Schedule & Notes Page

[kmpaul]

Creating a draft PR to address #8. We need to finalize a meeting schedule (day and time) and then I will:

• Create a Google Calendar for these recurring meeting times.
• Inform Ryan Abernathey of these times so they can be added to the Pangeo Calendar, too.
• Update the "Meeting Schedule & Notes" page with the correct times and embedded Google Calendar.

[kmpaul]

I don't think that we need a special Google Calendar. I've informed Ryan Abernathey, and he has offered to add these meeting times to the Pangeo Google Calendar, which you can get the link to here:

https://calendar.google.com/calendar/embed?src=ucar.edu_c23ln4014khs3f65o93vqv5kqc%40group.calendar.google.com

I think that is sufficient.

I'll work on adding the meeting times to the Pythia Portal.

[kmpaul]

I made a Google Calendar anyway so that we can link it to the Meetings page on the Portal:

https://calendar.google.com/calendar/u/0?cid=Y180cXB2ZjMxNmFmZDltdjBjaTdkMnVpYWZvZ0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t

[kmpaul]

I think the only think I am waiting on before opening this up to review is a Zoom meeting time.

@jukent: Do you might using your NCAR Zoom account to create a recurring Zoom meeting at 11AM Mountain every Thursday with the following settings (thanks to Ryan Abernathey)?

[clyne]

I made a Google Calendar anyway so that we can link it to the Meetings page on the Portal:

https://calendar.google.com/calendar/u/0?cid=Y180cXB2ZjMxNmFmZDltdjBjaTdkMnVpYWZvZ0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t

Is it worth the bother of having and maintaining a separate calendar for two meetings? Maybe we just list the time and coordinates on the website and have one less thing to keep track of... Just a thought.

[kmpaul]

It is definitely debatable whether having a separate calendar is useful, but it is nice to allow other people to easily add our meeting to their calendar. With a GCAL, they can add the Pythia calendar (with all of our meetings) to their own calendar with a single click. And if we change our meeting times, then they get updated.

If the only people we had to worry about communicating with was our own internal team, then I agree that having the separate calendar is not very useful. But is is very useful for communicating with people external to our organizations.

At least those are my thoughts. Do others feel differently?

[jukent]

I think the only think I am waiting on before opening this up to review is a Zoom meeting time.

@jukent: Do you might using your NCAR Zoom account to create a recurring Zoom meeting at 11AM Mountain every Thursday with the following settings (thanks to Ryan Abernathey)?

I was able to create a Zoom meeting (the meeting ID is different -- but consistent for each meeting -- since I do not know how to edit that).

Could you give me editing powers over the Pythia calendar so that I may add the Zoom meetings to that calendar?

And I'll send the correct meeting ID to Ryan Abernathy so that can be added to the Pangeo calendar.
It was easiest for me to just create one Pythia meeting -- so that I could maintain a constant meeting ID. But if you'd like I can go in an specify "Education" vs "Infrastructure" Working Group meetings.

[kmpaul]

@jukent: I just added you as a maintainer for the Pythia Google Calendar.

[kmpaul]

And I think 1 recurring weekly Zoom meeting should be fine.

[jukent]

The Zoom meeting information has been added to the calendar events.

[kmpaul]

@jukent: It looks like the Zoom meeting has a password, which isn't supposed to be set. Can you confirm that the meeting was set up with the same settings as shown above?

[jukent]

@jukent: It looks like the Zoom meeting has a password, which isn't supposed to be set. Can you confirm that the meeting was set up with the same settings as shown above?

Hmm for some reason it won't let me not have a password on recurring meetings. I will go ahead and fix this for the upcoming meeting ASAP and then try to figure this out.

E: It seems this option has been locked by the admin of my account. I can only have a meeting that doesn't require a password if I use my personal meeting ID - which Zoom won't let me use for recurring meetings. From their site: "Recurring meetings cannot be scheduled with your Personal Meeting ID (PMI) since your PMI is reserved so that you can start or schedule a meeting at anytime."

[kmpaul]

Ok. It looks like we can no longer create a recurring Zoom meeting without a password, at least the way NCAR's Zoom account is set up. So, we'll just proceed with a password.

[kmpaul]

@clyne, @jukent: I think this PR is now ready for review.

[clyne]

@kmpaul is there a way to build the documentation and preview it locally?

[brian-rose]

@kmpaul is there a way to build the documentation and preview it locally?

@clyne yes! From a local clone of the source repository, do this:

conda env create -f ci/environment.yml
conda activate
make html

This will build the site in a dedicated conda environment with all the same packages as are used to build it here on GitHub.

I'll try to submit a separate PR that describes how to do this briefly on the Contributors page.

[brian-rose]

Though I imagine there's a way to automate this? Can we have the site rendered and available as a zip file download anytime a new PR is pushed? That would be very useful.

[kmpaul]

Thanks, @brian-rose! Yes, @clyne, that's how you do it. Sorry. I'm in another meeting.

Following @brian-rose's instructions, then just do (on a Mac):

$ open _build/html/index.html

[kmpaul]

Oh, and these steps have to be done from within the content directory.

[kmpaul]

I think these instructions should be in the README.md and in the CONTRIBUTING.md page.

[brian-rose]

@kmpaul I'll whip something up.

[clyne]

@kmpaul is there a way to build the documentation and preview it locally?

@clyne yes! From a local clone of the source repository, do this:

conda env create -f ci/environment.yml
conda activate
make html

This will build the site in a dedicated conda environment with all the same packages as are used to build it here on GitHub.

I'll try to submit a separate PR that describes how to do this briefly on the Contributors page.

I had to install sphinx, and now I'm getting:

(base) bash-3.2$ make html
Running Sphinx v3.2.1

Extension error:
Could not import extension myst_nb (exception: No module named 'myst_nb')
make: *** [html] Error 2

[brian-rose]

Ok. It looks like we can no longer create a recurring Zoom meeting without a password, at least the way NCAR's Zoom account is set up. So, we'll just proceed with a password.

How do we plan to distribute the password? Currently the Meetings page provides the zoom link but doesn't say anything about the passcode.

[brian-rose]

@kmpaul is there a way to build the documentation and preview it locally?

@clyne yes! From a local clone of the source repository, do this:

conda env create -f ci/environment.yml
conda activate
make html

This will build the site in a dedicated conda environment with all the same packages as are used to build it here on GitHub.
I'll try to submit a separate PR that describes how to do this briefly on the Contributors page.

I had to install sphinx, and now I'm getting:

(base) bash-3.2$ make html
Running Sphinx v3.2.1

Extension error:
Could not import extension myst_nb (exception: No module named 'myst_nb')
make: *** [html] Error 2

@clyne looks like you are not running make html from the correct conda environment.

I think I mis-typed above, you should do this:

conda env create -f ci/environment.yml
conda activate pythia
make html

All the dependencies (including sphinx and extensions) should then be in the current conda environment.

[clyne]

that did it. Thanks!

[clyne]

Ok. It looks like we can no longer create a recurring Zoom meeting without a password, at least the way NCAR's Zoom account is set up. So, we'll just proceed with a password.

How do we plan to distribute the password? Currently the Meetings page provides the zoom link but doesn't say anything about the passcode.

@brian-rose with the exception of today's meeting I'm seeing the password in the calendar entries...

[clyne]

Looks good!

[brian-rose]

Ok. It looks like we can no longer create a recurring Zoom meeting without a password, at least the way NCAR's Zoom account is set up. So, we'll just proceed with a password.

How do we plan to distribute the password? Currently the Meetings page provides the zoom link but doesn't say anything about the passcode.

@brian-rose with the exception of today's meeting I'm seeing the password in the calendar entries...

True! @kmpaul maybe add a note on the page mentioning that the passcode can be found in the calendar entries. If you just click on the link as given in the first sentence, zoom prompts for a passcode.

[kmpaul]

@brian-rose: Would it be better to just remove the link to the Zoom meeting, and instead point people to the Google Calendar for information about how to join?

I agree that clicking the link and then immediately being asked for a password might be confusing for people...but maybe having people get the info from the Google Calendar is also confusing. ....I really wish I could remove the password from the meetings altogether.

[brian-rose]

Agreed it would be great to get rid of the passcode, but institutional rules are what they are. It would be the same if we used a UAlbany-hosted zoom meeting.

I guess I would vote for removing the first link altogether and just saying something like "We will meet on zoom, please find links in the calendar below".

[kmpaul]

Implementing @brian-rose's suggestion.

[kmpaul]

Is this ready to merge?

[brian-rose]

Looks great to me.