|
| 1 | +--- |
| 2 | +title: "Sprints Guide" |
| 3 | +meta_title: "Sprints Guide" |
| 4 | +description: "Guide and Resources for Organizers and assistants" |
| 5 | +draft: false |
| 6 | +weight: 1 |
| 7 | +section: "speakers" |
| 8 | +--- |
| 9 | + |
| 10 | +# Sprints guide for PyLadies Conference 2025 |
| 11 | + |
| 12 | +## As conference assistant |
| 13 | + |
| 14 | +### What is a Sprint? |
| 15 | + |
| 16 | +Sprint are informal coding sessions, and knoweldge sharing where people gather |
| 17 | +together to work on Open-Source projects, suggest changes in existing libraries |
| 18 | +solve problems. A Sprint is an opportunity for learning and self-development |
| 19 | +while contributing to Open Source projects. |
| 20 | + |
| 21 | +### How will the sprint work at PyladiesCon? |
| 22 | + |
| 23 | +During the conference, we will conduct mentored Sprint sessions where projects |
| 24 | +will be presented. You can then join the specific Discord channel to |
| 25 | +coordinate, work on, or ask questions about particular issues. |
| 26 | + |
| 27 | +### What do I need to do to assist in the Sprint? |
| 28 | + |
| 29 | +First, secure your conference ticket, and then attend the mentored Sprint |
| 30 | +session. If your timezone prevents participation synchronously, you can still |
| 31 | +check out the proposed projects and join the Discord channel. |
| 32 | + |
| 33 | +### When and Where? |
| 34 | + |
| 35 | +The Sprint will take place after the talks and panels: |
| 36 | + |
| 37 | +* TBD: Sunday 7th of December |
| 38 | +* TBD: Add time to timezones |
| 39 | + |
| 40 | +### Where can I find the projects in advance? |
| 41 | + |
| 42 | +You can visit [the Sprints page](https://2025.conference.pyladies.com/en/sprints/) |
| 43 | +to see all the projects that are already participating. |
| 44 | + |
| 45 | +## As Sprint Organizer |
| 46 | + |
| 47 | +### Open-Source Projects |
| 48 | + |
| 49 | +Anyone can submit a project for the sprints, although sprints are typically |
| 50 | +submitted by project maintainers or frequent contributors. |
| 51 | + |
| 52 | +To submit a project for the sprints, you need to submit a Pull-Request |
| 53 | +to [this year's conference website repository](https://github.com/pyladies/global-conference-2025), |
| 54 | +specifically the |
| 55 | +[sprints.astro](https://github.com/pyladies/global-conference-2025/blob/main/src/pages/en/sprints.astro) |
| 56 | +file. |
| 57 | + |
| 58 | +And modify the `sprintsData` variable to include your project information, |
| 59 | +like it's shown in the following example: |
| 60 | + |
| 61 | +``` |
| 62 | +const sprintsData = [ |
| 63 | +{ |
| 64 | + name: "Project 1", |
| 65 | + project_url: "https://github.com/myossp/project2", |
| 66 | + project_doc_url: "https://docs.myossproject.com", |
| 67 | + description: "This is an example project that will help you contribute to an OSS initiative!", |
| 68 | + level: "Beginner friendly, some math knowledge", |
| 69 | + languages: "Python, Rust", |
| 70 | + }, |
| 71 | +]; |
| 72 | +``` |
| 73 | + |
| 74 | +### What worked very well in the past? |
| 75 | + |
| 76 | +Create issue that could be "first time contribution friendly" and assign assign |
| 77 | +tags to your issues. |
| 78 | + |
| 79 | +### First time runing a Sprint? |
| 80 | + |
| 81 | +1. Set clear objectives and desired outcomes for the Sprint. |
| 82 | +2. Gather all essential materials. |
| 83 | +3. Create issues of varying levels (beginner, documentation, etc.) on GitHub to make participation accessible. |
| 84 | + |
| 85 | +Recommended resources: |
| 86 | +- https://opensourceevents.github.io/ |
| 87 | +- http://open-advice.org/ |
| 88 | + |
| 89 | + |
| 90 | + |
| 91 | + |
0 commit comments