Skip to content

[Nomination] Hamza Gbada #58

@HamzaGbada

Description

@HamzaGbada

Select one:

  • I am nominating myself for the PyTorch Ambassador Program.
  • I am nominating someone else to become a PyTorch Ambassador.

Please confirm that the nominee meets the following requirements:

Nominee Name

Hamza Gbada

Nominee Email

[email protected]

Nominee's GitHub or GitLab Handle

HamzaGbada

(Optional) Organization / Affiliation

University of Sousse

City, State/Province, Country

Sousse, Sousse, Tunisia

Your Name

No response

Your Email (Optional)

No response

How has the nominee contributed to PyTorch?

  • An active contributor to PyTorch repositories (e.g., commits, PRs, discussions).
  • A speaker at PyTorch events or workshops.
  • A PyTorch user group organizer or meetup host.
  • A researcher or educator using PyTorch in academic work or training.
  • An active leader in the PyTorch community with at least one year of experience in:
  • Organizing events (virtual/in-person).
  • Speaking at AI/ML conferences.
  • Mentoring others in PyTorch.
  • Creating technical content (e.g., blogs, videos, tutorials).

🏆 How Would the Nominee Contribute as an Ambassador?

As a PyTorch Ambassador, I plan to build a strong bridge between the academic, open-source, and practitioner communities. I will continue producing and maintaining high-quality, PyTorch-based educational content—ranging from tutorials and research implementations to hands-on workshops. I also aim to initiate a PyTorch user group in Tunisia to host local meetups, webinars, and study sessions focused on real-world use cases of PyTorch, especially in document AI and graph learning.

Given my background as a university lecturer, I am well-positioned to mentor students and early-career professionals, helping them understand PyTorch beyond the basics and guide them in contributing to open-source. I am also eager to collaborate on technical challenges within the PyTorch ecosystem and contribute via code, documentation, or community discussions to ensure the framework continues evolving with user needs.

Any additional details you'd like to share?

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions