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

Sprint info #47

Merged
merged 29 commits into from
Jun 17, 2022
Merged

Sprint info #47

merged 29 commits into from
Jun 17, 2022

Conversation

symeneses
Copy link
Contributor

@symeneses symeneses commented Jun 14, 2022

It includes sprint info:

  • Sprint Requirements, Goals, Target Audience
  • Sprint Guide {include expected etiquette, Discord, structure of the day}
  • Sprint Cheat Sheet
  • Prep Work {include: videos, docstring tutorial}
  • FAQ
  • Resources

Additionaly:

sprint/index.md Outdated Show resolved Hide resolved
sprint/index.md Outdated Show resolved Hide resolved
symeneses and others added 2 commits June 15, 2022 10:03
Co-authored-by: Reshama Shaikh <reshama.stat@gmail.com>
Co-authored-by: Reshama Shaikh <reshama.stat@gmail.com>
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.

This looks great so far, thanks!

As a general comment, the sprint guide still needs significant updates. IIUC, we won't use zoom anymore but discourse and the info on breakout rooms also needs to be updated a bit. Mainly I won't be able to host a spanish speaking room because I might not attend any session (and will at most attend one).

We should also add resources on managing Discord in the "volunteer guide" section: blocking/kicking people out, disabling the chat/videos.... Hopefully we won't need to use it but it already happened once and I had no idea how to do any of those. cc @reshamas @cluhmann

@@ -1,3 +1,4 @@
(current_sprint)=
# July 2022 sprint
Copy link
Member

Choose a reason for hiding this comment

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

@reshamas should we update all mentions of "sprint" to "open source working sessions"?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, please!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

How to rename the headers Sprint info and Sprint events in a short form?

  • Something like: OS session info, or Session info and OS events or simply Events

Then, Sprint guide and Sprint preparation would be Session guide and Session preparation?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@reshamas should I change this as suggested here?

sprint/faq.md Show resolved Hide resolved
sprint/index.md Show resolved Hide resolved
sprint/index.md Outdated Show resolved Hide resolved
sprint/index.md Outdated Show resolved Hide resolved
sprint/index.md Outdated Show resolved Hide resolved
sprint/old-sprint-guide.md Outdated Show resolved Hide resolved
@reshamas
Copy link
Contributor

@OriolAbril
When ready, you can go ahead and merge this in, so the structure is set up.

It looks like I will need to go through all the pages and review and edit the text so it's not specific to a sprint, but rather a "general" reference, and I can work on that next.

@OriolAbril
Copy link
Member

The structure is set up already, this is working on the text of the "sprint info" navbar section. Current website generated from main: https://pymc-data-umbrella.xyz/en/latest/

@OriolAbril OriolAbril mentioned this pull request Jun 15, 2022
@reshamas
Copy link
Contributor

The structure is set up already, this is working on the text of the "sprint info" navbar section. Current website generated from main: https://pymc-data-umbrella.xyz/en/latest/

@OriolAbril
Got it. I will look it over and add text.

@symeneses symeneses marked this pull request as ready for review June 15, 2022 17:27
sprint/prep-work.md Outdated Show resolved Hide resolved
sprint/index.md Outdated Show resolved Hide resolved
symeneses and others added 2 commits June 15, 2022 20:05
Co-authored-by: Reshama Shaikh <reshama.stat@gmail.com>
@reshamas
Copy link
Contributor

@symeneses
So, that means we will have a FAQ, correct?
With the question here:

FAQ 1: Do I need to be a PyMC user to participate in the open source working session?

Response:  It is not necessary to be a PyMC user to contribute to this open source project. There are a number of issues where we could use your contribution. Examples:  
- Adding timestamps to videos from our PyMCon conference
- Updating docstrings in documentation
- Update notebooks to v4.  This video, [Contributing to PyMC Documentation](https://youtu.be/fzpmLWQNj4A) provides a background and examples.  

@symeneses
Copy link
Contributor Author

1: Do I need to be a PyMC user to participate in the open source working session?

Response: It is not necessary to be a PyMC user to contribute to this open source project. There are a number of issues where we could use your contribution. Examples:

  • Adding timestamps to videos from our PyMCon conference
  • Updating docstrings in documentation
  • Update notebooks to v4. This video, Contributing to PyMC Documentation provides a background and examples.

Added

@reshamas
Copy link
Contributor

@symeneses Another FAQ already!

**Q:  Is there a requirement to have attended #1 of the working session?**

The Pre-event office hours are an opportunity for incoming contributors to ask questions for the upcoming working sessions.  It is *not required* to attend a specific session as a prerequisite for other sessions.  Ideally, it is beneficial if folks can attend as many sessions as they can, to build up their open source skills and familiarity with the PyMC project. 

If you are unable to attend the Pre-event office hours, you can ask your questions in one of these ways:  
- Open an issue on the Data Umbrella & PyMC [Open Source Event Website's] GitHub repo:  https://github.com/pymc-devs/pymc-data-umbrella/issues
- Email us at:  info@dataumbrella.org

@symeneses
Copy link
Contributor Author

@symeneses Another FAQ already!

**Q:  Is there a requirement to have attended #1 of the working session?**

The Pre-event office hours are an opportunity for incoming contributors to ask questions for the upcoming working sessions.  It is *not required* to attend a specific session as a prerequisite for other sessions.  Ideally, it is beneficial if folks can attend as many sessions as they can, to build up their open source skills and familiarity with the PyMC project. 

If you are unable to attend the Pre-event office hours, you can ask your questions in one of these ways:  
- Open an issue on the Data Umbrella & PyMC [Open Source Event Website's] GitHub repo:  https://github.com/pymc-devs/pymc-data-umbrella/issues
- Email us at:  info@dataumbrella.org

Added

@symeneses
Copy link
Contributor Author

@OriolAbril could you please merge this PR? The only thing missing is to change sprint in the content. cc: @reshamas

@reshamas
Copy link
Contributor

@OriolAbril @symeneses
Yes, I think this PR can be merged in. I will review the text over the weekend and submit small PRs to update various pages.

Thank you both for your help with this!

sprint/faq.md Outdated Show resolved Hide resolved
**Response:** The Pre-event office hours are an opportunity for incoming contributors to ask questions for the upcoming working sessions. It is *not required* to attend a specific session as a prerequisite for other sessions. Ideally, it is beneficial if folks can attend as many sessions as they can, to build up their open source skills and familiarity with the PyMC project.

If you are unable to attend the Pre-event office hours, you can ask your questions in one of these ways:
- Open an issue on the Data Umbrella & PyMC [Open Source Event Website's GitHub repo](https://github.com/pymc-devs/pymc-data-umbrella/issues)
Copy link
Member

Choose a reason for hiding this comment

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

Would it be too much friction to have the questions on discourse? We can add a category and/or tag for them. I am not sure the distinction between questions about the working sessions but not about the contributions themselves or about pymc will be clear to participants. And the 2nd ones should clearly go on discourse.

sprint/tutorials/pr_tutorial.md Show resolved Hide resolved
sprint/tutorials/docstring_tutorial.md Outdated Show resolved Hide resolved
sprint/tutorials/environment_setup.md Outdated Show resolved Hide resolved
@OriolAbril
Copy link
Member

@symeneses I am working on this locally a bit now

@OriolAbril
Copy link
Member

Done 😄

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.

add these videos to prep work: Discord & LiveShare
3 participants