[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-dev] Piloting a new contributor workflow on gitlab.torproject.org



Hi all,

If you've recently tried to fork a Tor repository into your personal
gitlab.torproject.org namespace and received an error, you’re not
alone. This is a known limitation of our current GitLab setup.

To address this, we are piloting a new contributor workflow designed to
make it easier for community contributors like you to propose changes,
open merge requests, and collaborate, without needing write access to
Tor’s canonical GitLab repositories.

We’ve created a shared GitLab group for contributor forks called
tor-contributors[0].

This group hosts mirrored forks of selected Tor projects. When you want
to contribute, you can request access to the relevant contributor fork,
create a branch (e.g., username/fix-x), and open a merge request back to
the canonical repository.

We’re looking for contributors who are actively working on changes and
would like to participate in this pilot by trying out the workflow and
providing feedback.

If that’s you, please follow the onboarding instructions[1].

To help keep things manageable, we ask that people only request access
if they are preparing to open a merge request. If you're just curious or
want to follow along, there is no need to request access, we will
continue to share updates as the pilot evolves.

Thanks, and we look forward to your feedback.

Thanks,
Micah

0. https://gitlab.torproject.org/tor-contributors/
1. https://gitlab.torproject.org/tor-contributors/meta
-- 
Micah Anderson (he/him)
Director of Engineering
The Tor Project, Inc. <https://torproject.org>
_______________________________________________
tor-dev mailing list -- tor-dev@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-dev-leave@xxxxxxxxxxxxxxxxxxxx