-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Sprint info #47
Conversation
Co-authored-by: Reshama Shaikh <reshama.stat@gmail.com>
Co-authored-by: Reshama Shaikh <reshama.stat@gmail.com>
There was a problem hiding this 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 |
There was a problem hiding this comment.
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"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, please!
There was a problem hiding this comment.
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
, orSession info
andOS events
or simplyEvents
Then, Sprint guide
and Sprint preparation
would be Session guide
and Session preparation
?
There was a problem hiding this comment.
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?
@OriolAbril 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. |
The structure is set up already, this is working on the text of the "sprint info" navbar section. Current website generated from |
@OriolAbril |
Co-authored-by: Reshama Shaikh <reshama.stat@gmail.com>
@symeneses
|
Added |
@symeneses Another FAQ already!
|
Added |
@OriolAbril could you please merge this PR? The only thing missing is to change |
@OriolAbril @symeneses Thank you both for your help with this! |
**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) |
There was a problem hiding this comment.
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.
@symeneses I am working on this locally a bit now |
Done 😄 |
It includes sprint info:
Additionaly:
current_sprint
to be used in sprint goalsabout_pymc
to be used in resources