pymc-devs · OriolAbril · Jun 17, 2022 · Jun 14, 2022 · Jun 14, 2022 · Jun 14, 2022
diff --git a/2022-07_sprint/index.md b/2022-07_sprint/index.md
@@ -1,3 +1,4 @@
+(current_sprint)=
 # July 2022 sprint
 
 :::{toctree}

diff --git a/about/index.md b/about/index.md
@@ -1,3 +1,4 @@
+(about_pymc)=
 # About PyMC
 
 % TODO: add nice text

diff --git a/sprint/faq.md b/sprint/faq.md
@@ -0,0 +1,2 @@
+# Frequently Asked Questions
+
diff --git a/sprint/index.md b/sprint/index.md
@@ -1,10 +1,74 @@
 # Sprint info
 
-% TODO: arreglar toctree y texto
-
 :::{toctree}
-:maxdept: 1
+:maxdepth: 1
+:hidden:
 
+self
 sprint-guide
 sprint-cheatsheet
+prep-work
+faq
+resources
+:::
+
+::::{div} sd-fs-5
+:::{tip}
+* **Wondering if the sprint is for you?** We have got just {ref}`the page <decision_tree>`
+* **Ready to contribute?** Go to {ref}`docstring_tutorial` page
+:::
+::::
+
+(sprint)=
+## Open Source Working Sessions
+
+Data Umbrella is organizing a series of open source working sessions to contribute to the PyMC project. For more information, see {ref}`Resources <resources>` section.
+
+## Goals
+
+In this sprint we’re focusing on bringing in new contributors, we sincerely hope this will be a welcoming, inclusive experience for you into the world of open source software. We hope to help you to the best of our abilities and learn from you as well!
+The sprint will consist of small resolvable issues and contributing to the PyMC documentation, so if you aren’t experienced in software development no worries at all, you can contribute to documentation with knowledge of markdown or statistics.
+Here’s the fun part, we’ll be giving away stickers, mugs and the Bayesian Computation book by PyMC Developers Ravin, Junpeng and Osvaldo!!! Find the schedule and all other details {ref}`here <current_sprint>`.
+
+## Requirements
+
+- Get your laptop, and some stable internet connection!
+- Working knowledge of terminal and git
+- Setup a python virtual environment beforehand!
+- Other than these two you can make different kinds of contributions with different skill sets, for example:
+  - You can contribute to documentation with knowledge of markdown and maybe some basic statistics
+  - You can contribute to CI/CD issues or Python issues with basic knowledge of programming
+  - You can contribute to core codebase with knowledge of Python + Bayesian Statistics
+  - Note: {ref}`Check the sprint cheat sheet <decision_tree>` to know a suitable area of contribution and some resources to prepare you for it
+
+## Target Audience
+The following table answers the question **"This sprint is for someone who is/has ..."**
+
+:::{list-table}
+:header-rows: 1
+:stub-columns: 1
+:widths: 7 1 1
+
+* -
+  - Yes
+  - No
+* - New to Open source
+  - {fas}`check;sd-text-success`
+  - {fas}`check;sd-text-success`
+* - Statistical background
+  - {fas}`check;sd-text-success`
+  - {fas}`check;sd-text-success`
+* - Currently working in data science/software
+  - {fas}`check;sd-text-success`
+  - {fas}`check;sd-text-success`
+* - Knows/uses PyMC
+  - {fas}`check;sd-text-success`
+  - {fas}`check;sd-text-success`
+* - Member of the PyMC team
+  - {fas}`times;sd-text-danger`
+  - {fas}`check;sd-text-success`
 :::
+
+Read the {ref}`decision_tree` for more detailed answers and to see
+what types of contributions can you make depending on your interests and
+background.
diff --git a/sprint/old-sprint-guide.md b/sprint/old-sprint-guide.md
diff --git a/sprint/prep-work.md b/sprint/prep-work.md
@@ -0,0 +1,35 @@
+# Sprint preparation
+
+## Checklist
+
+:::{list-table}
+:header-rows: 1
+:stub-columns: 1
+:widths: 1 4 1 2
+
+* - #
+  - Task
+  - Status
+  - Notes
+* - 1
+  - Have a GitHub account?
+  - {fas}`check;sd-text-success`
+  - 
+
+:::
+
+
+## Sprint day
+
+%TODO: Improve text%
+
+:::{tip}
+To communicate during the sprint, we will be using Discord. The [Using the Discord Server](https://youtu.be/w2A8SknM-68) introduction video contains a brief introduction to the Discord Data Umbrella server with some tips on how to navigate the application.
+:::
+
+### Pair programming
+
+Live Share is an extension from Visual Studio Code that allows you to collaboratively edit and debug with others in real-time. It allows you to instantly share your current project, edit snippets of code at the same time or follow someone’s cursor while they program. To learn more about Live Share, visit [Live Share with Visual Studio Code](https://youtu.be/WHOiljOYGVw).
+
+
+### Environment setup
diff --git a/sprint/resources.md b/sprint/resources.md
@@ -0,0 +1,14 @@
+(resources)=
+# Resources
+
+- {ref}`PyMC - Data Umbrella series content and videos <about_pymc>` (all webinar materials have been uploaded to this website, videos are embedded too so you have everything just a click away)
+
+- {ref}`Sprint Cheat Sheet <decision_tree>`
+
+- [Reshama Shaikh: Example of Submitting a Pull Request to PyMC Documentation](https://www.youtube.com/watch?v=NbmdFJsnuuo)
+
+- [Using Discord for sprint](https://youtu.be/w2A8SknM-68)
+
+- [Live Share with Visual Studio Code](https://youtu.be/WHOiljOYGVw)
+
+- [Git Notes](https://www.dataschool.io/how-to-contribute-on-github/)
diff --git a/about/sprint-cheatsheet.md → sprint/sprint-cheatsheet.md b/about/sprint-cheatsheet.md → sprint/sprint-cheatsheet.md
diff --git a/sprint/sprint-guide.md b/sprint/sprint-guide.md
@@ -23,11 +23,11 @@ These breakout rooms aren't rigid, you can choose which one you wish to be in, t
 
 ## Volunteer Guide
 
-1. Breakout rooms will be created at the begining of the meeting, but do join 15 minutes before the sprint so you can get the hang of Zoom and these rooms to make things smoother.
+1. Breakout rooms will be created at the beginning of the meeting, but do join 15 minutes before the sprint so you can get the hang of Zoom and these rooms to make things smoother.
 2. Feel free to create new breakout rooms, if needed.
 3. Be patient and kind to sprint participants, if you feel unable to help someone with a doubt or issue, redirect it to another volunteer or PyMC team member if someone is available. If that does not work, consider suggesting a new issue to the participant.
 4. Encourage people to introduce themselves and ask questions. 
-5. Do flag any(really ANY) inappropriate behaviour. Warn the participant or remove them from the Zoom meeting in these cases:
+5. Do flag any (really ANY) inappropriate behaviour. Warn the participant or remove them from the Zoom meeting in these cases:
 
     - They make a discriminatory remark
     - They are being persistently rude
@@ -45,6 +45,3 @@ These breakout rooms aren't rigid, you can choose which one you wish to be in, t
 Cheers, have fun folks!
 
 [Sprint Organizers](https://github.com/pymc-devs/pymc/projects/4)
-
-
-