Skip to content
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

Initial setup for March 2023 sprint event #189

Merged
merged 30 commits into from
Feb 26, 2023

Conversation

reshamas
Copy link
Contributor

@reshamas reshamas commented Feb 12, 2023

Set up section for March 2023 LATAM sprint

References: #190

@reshamas reshamas changed the title initial setup for March 2023 event [WIP] initial setup for March 2023 event Feb 12, 2023
2023-03_sprint/sprint_parties/sponsors.md Show resolved Hide resolved
[{fab}`twitter`](https://twitter.com/JimenezLucyJ)

:::
:::{grid-item}
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we have to delete this line,in the preview the previous and next options are being displayed as if they were in the grid.

Copy link
Member

Choose a reason for hiding this comment

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

I would delete the grid elements we aren't using to see the start and closing of the colon fences. I am also not sure I understand the difference between this section and the community contributors in organizers file


| Event | Date | Time | Duration | RSVP |
|-------------------------------------------|--------------------|-------------------------|----------|-------------|
| Open Source Working Session #1 | Jul 9 (Saturday) | 9 ET / 13 UTC / 16 EAT | 3 hours | [MeetUp](https://www.meetup.com/data-umbrella/events/286552452/) |
Copy link
Contributor

Choose a reason for hiding this comment

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

Here, we could have the times in this format: Mex, Col, Peru: 8 am/ Vzla, Bo: 9 am/ Arg, Chile, Brzl: 10 am. Same for the banner.

Copy link
Member

@OriolAbril OriolAbril left a comment

Choose a reason for hiding this comment

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

looks good so far, the only important issues are with the grids/cards/comments.

You'll also need to update https://github.com/pymc-devs/pymc-data-umbrella/blob/main/index.md?plain=1#L10-L11 for the homepage to show this event.

2023-03_sprint/index.md Show resolved Hide resolved
2023-03_sprint/sprint_parties/community_partners.md Outdated Show resolved Hide resolved
[{fab}`twitter`](https://twitter.com/JimenezLucyJ)

:::
:::{grid-item}
Copy link
Member

Choose a reason for hiding this comment

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

I would delete the grid elements we aren't using to see the start and closing of the colon fences. I am also not sure I understand the difference between this section and the community contributors in organizers file

2023-03_sprint/sprint_parties/contributors.md Show resolved Hide resolved
2023-03_sprint/sprint_parties/media_kit.md Outdated Show resolved Hide resolved
Comment on lines 39 to 50
:::{grid-item}
:class: sd-text-center

<!-- <img alt="Sandy Weng" src="../../_static/people/sandy.jpg" class="rounded-circle">

Sandy Weng

[{fab}`linkedin-in`](https://www.linkedin.com/in/sandy-weng-a0959762)
:::
:::{grid-item}
:class: sd-text-center
-->
Copy link
Member

Choose a reason for hiding this comment

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

I think it would be less confusing if we deleted grid elements, however, if commenting, it would be clearer to comment a whole grid element:

<!-- :::{grid-item}
:class: sd-text-center

<img alt="Sandy Weng" src="../../_static/people/sandy.jpg" class="rounded-circle">

Sandy Weng

[{fab}`linkedin-in`](https://www.linkedin.com/in/sandy-weng-a0959762)
::: -->
:::{grid-item}
:class: sd-text-center

right now we start a grid element, comment its closing, comment an opening, add content to the element and then close the grid element

2023-03_sprint/sprint_parties/sponsors.md Show resolved Hide resolved
conf.py Outdated Show resolved Hide resolved
reshamas and others added 3 commits February 13, 2023 13:47
@reshamas
Copy link
Contributor Author

@OriolAbril
Preview is here:
https://pymc-data-umbrella--189.org.readthedocs.build/en/189/2023-03_sprint/sprint_parties/index.html

We are missing "Mar 2023 event" at top left of menu. Not sure where to make the adjustment in the file.

The social media kit on this page points to the one from 2022-07:
https://pymc-data-umbrella--189.org.readthedocs.build/en/189/2023-03_sprint/sprint_parties/community_partners.html

@OriolAbril
Copy link
Member

Everything kind of works now. The main issue is notebooks+translaitons does not work, and it breaks the whole build. For now notebooks are excluded from translated builds (I think the only two notebooks are the ones for the intro to arrays and intro to probabilistic modeling). I am reviewing below with some further comments and explanations

@@ -7,8 +7,8 @@ DO NOT EDIT! This is only a placeholder to define the nabvar and is deleted to r
:maxdepth: 1
:hidden:

July 2022 event <2022-07_sprint/schedule>
People <2022-07_sprint/sprint_parties/index>
Mar 2023 event <2023-03_sprint/index>
Copy link
Member

Choose a reason for hiding this comment

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

We are missing "Mar 2023 event" at top left of menu. Not sure where to make the adjustment in the file.

This was updated to 2023-03_sprint/schedule which does not exist. I noticed this thanks to an sphinx warning in the rtd logs:

/home/docs/checkouts/readthedocs.org/user_builds/pymc-data-umbrella/checkouts/189/index.md:6: WARNING: toctree contains reference to nonexisting document '2023-03_sprint/schedule'

@@ -28,7 +28,7 @@ Note: It is *not required* to attend a specific session as a prerequisite for

Note: You can click on the table image below to view the full spreadsheet with a larger view.

[![schedule with timezones](../_static/2022_07/2022_07_timezones.png)](https://docs.google.com/spreadsheets/d/1oO9OhsTh9PFcqKI7Exj_ZcH0GvunQVHtM4aqUh0kjTk/edit?usp=sharing)
[![schedule with timezones](../_static/images/2022_07_timezones.png)](https://docs.google.com/spreadsheets/d/1oO9OhsTh9PFcqKI7Exj_ZcH0GvunQVHtM4aqUh0kjTk/edit?usp=sharing)
Copy link
Member

Choose a reason for hiding this comment

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

the image was moved but the path still needed to be updated

@@ -1,14 +1,13 @@
# Community Partnership

(become_community_partner)=
Copy link
Member

Choose a reason for hiding this comment

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

I have deleted this to make sure we link to the current one

@@ -10,7 +10,6 @@ videos
../about/contributing_to_pymc/index
../about/contributing_to_documentation/index
donate
../2022-07_sprint/sprint_parties/media_kit
Copy link
Member

Choose a reason for hiding this comment

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

I also noticed this was here, so even though the path was sprint specific, it was listed inside the contributing section which was confusing. It is now listed in the "about" of the specific sprint.

@reshamas reshamas merged commit ab422f4 into pymc-devs:main Feb 26, 2023
@reshamas reshamas changed the title [WIP] initial setup for March 2023 event Initial setup for March 2023 sprint event Feb 26, 2023
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.

3 participants