GSoC 2025 Proposal Draft: PyLadiesCon - Enhancing the PyLadiesCon Web Portal

[Ataeesabira]

Hi @Mariatta

My name is Sabira Ataee, and I’m excited about the opportunity to contribute to PyLadiesCon as part of Google Summer of Code 2025. I’ve drafted a proposal focused on enhancing the PyLadiesCon Web Portal and would love your feedback before officially submitting it.

Proposal Overview

• Sub-org: PyLadiesCon
• Project Title: Enhancing the PyLadiesCon Web Portal

Summary

The current PyLadiesCon portal relies heavily on spreadsheets for managing volunteers, sponsors, and event workflows, which leads to inefficiencies and limited collaboration. This project proposes to implement:

A sponsorship management system
Public and internal dashboards
UI/UX improvements and consistent branding
Automated tracking and better administrative workflows

Key Deliverables

• Django-based Sponsorship Portal with a tiered sponsorship model
• Admin review features and progress tracking dashboards
• Public dashboard for key conference stats
• Customized UI with improved styling and branding
• Optional groundwork for future team-specific dashboards

About Me

• Name: Sabira Ataee
• GitHub: Ataeesabira
• Email: sabiraataee2@gmail.com
• LinkedIn: LinkedIn Profile
• Timezone: Central European Summer Time (CEST)
• Commitment: Available full-time for GSoC 2025

Contributions
I’ve explored the PyLadiesCon codebase and reviewed open issues related to form styling, dashboard logic, and Django best practices.

Project Abstract
This project aims to replace spreadsheet-based workflows in the PyLadiesCon portal by building a full-featured sponsorship management system, a publicly viewable dashboard, and enhanced UI/UX. These improvements will streamline operations, support scalability for future events, and improve the experience for sponsors, organizers, and volunteers.

Detailed Description
Sponsorship Portal

• Build new Django models for SponsorshipTier, SponsorshipProfile, and related data
• Sponsor submission form with tier selection, logo upload, and contact details
• Review & Tracking Dashboard
• Admin panel for tracking sponsorship progress (e.g., contract sent, payment received)
• Internal dashboards showing current sponsors and stats
• Public Dashboard
• Display total funds, number of sponsors, and volunteer counts
• Automatically updates based on new data
• Accessible without login
• UI/UX & Styling Enhancements
• Integrate PyLadiesCon branding
• Improve error messages and template consistency (e.g., Django-Allauth views)
• (Optional) Future Work
• Foundation for team-specific dashboards (volunteer teams, organizers, etc.)
• Tech Stack: Python, Django, HTML/CSS, Bootstrap, JavaScript, PostgreSQL

Weekly Timeline

• Community Bonding (May 20 – June 17)
• Understand the current system
• Finalize design decisions with mentors
• Set up a local dev environment
• Phase 1 (June 17 – July 15)
• Implement sponsorship portal (models + forms)
• Begin frontend improvements
• Phase 2 (July 15 – August 12)
• Add sponsorship review features
• Start development of the public dashboard
• Midterm evaluation
• Final Phase (August 12 – September 9)
• Complete dashboard and UI updates
• Test and finalize documentation
• Submit final deliverables and presentation

I’d love your feedback!

Does this proposal meet the goals of PyLadiesCon
Are there additional features you’d recommend prioritizing?
Do you think the timeline would work?

[Mariatta]

Thanks for the proposal.
The timeline you shared seems to not match the GSoc timeline?
Eg community bonding period should start on May 8 and coding begins June 2 instead of June 17.

The timeline you provided seem broad and covering a month but there's not a lot of details. Would it be possible to have a more detailed plan by the week instead of by the month?
eg week 1, week 2, week 3, etc.