The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2024-03-19T15:07:31Zhttps://gitlab.torproject.org/tpo/core/arti/-/issues/1275Design the `VanguardMgr` and/or `VanguardPool`2024-03-19T15:07:31Zgabi-250Design the `VanguardMgr` and/or `VanguardPool`TODO: split into multiple issuesTODO: split into multiple issuesArti: Guard discovery researchgabi-250gabi-250https://gitlab.torproject.org/tpo/core/arti/-/issues/1274Use vanguards path selection in CircMgr::launch_hs_unmanaged.2024-03-20T18:09:26Zgabi-250Use vanguards path selection in CircMgr::launch_hs_unmanaged.The path selection will be handled by `VanguardHsPathBuilder`
(a new type similar to, or based on, the existing `ExitPathBuilder`).
See #1279
`CircMgr::launch_hs_unmanaged` will need to take an extra argument
specifying whether to use ...The path selection will be handled by `VanguardHsPathBuilder`
(a new type similar to, or based on, the existing `ExitPathBuilder`).
See #1279
`CircMgr::launch_hs_unmanaged` will need to take an extra argument
specifying whether to use full or lite vanguards when building the circuits.
`CircMgr::launch_hs_unmanaged` will only create STUB circuits.
If full vanguards are enabled, the circuits will be extended
by one hop as needed (outside of `launch_hs_unmanaged`), whenever
a STUB+ circuit is required (based on the `HsCircKind`).
Alternatively, `CircMgr::launch_hs_unmanaged` could
take an argument that specifies whether the circuit to launch
is STUB or STUB+. We will likely also need a corresponding
`TargetCircUsage::HsCircBaseWithVanguards (full|lite)` for it.
Then, based on the `TargetCircUsage`, `TargetCircUsage::build_path`
can dispatch to `VanguardHsPathBuilder::pick_path` (as opposed to
the `ExitPathBuilder::pick_path` currently used for
`TargetCircUsage::HsCircBase).
Since `launch_hs_circuits_as_needed`
preemptively populates the `HsCircPool` with circuits, it will need
to be modified too (to launch both STUB and STUB+ circuits).
Prerequisites: #1275, #1277, #1279Arti: Guard discovery researchgabi-250gabi-250https://gitlab.torproject.org/tpo/onion-services/onion-launchpad/-/issues/80Onion Launchpad build broken, maybe by some translation change2024-02-20T17:47:25ZSilvio RhattoOnion Launchpad build broken, maybe by some translation changeOnion Launchpad build is broken, possibly by some translation change.
Example job: https://gitlab.torproject.org/tpo/onion-services/onion-launchpad/-/jobs/458786
/cc @emmapeelOnion Launchpad build is broken, possibly by some translation change.
Example job: https://gitlab.torproject.org/tpo/onion-services/onion-launchpad/-/jobs/458786
/cc @emmapeelOnion Launchpad - 2024.Q2GusGus2024-03-28https://gitlab.torproject.org/tpo/tpa/team/-/issues/41469disable gitolite-merge-bot2024-01-16T19:25:25Zanarcatdisable gitolite-merge-botnow that we've confirmed most people have moved off of gitolite (#41214), this must mean no one is syncing repositories between gitolite and gitlab anymore. therefore, the @gitolite-merge-bot should be retired.
this probably means deact...now that we've confirmed most people have moved off of gitolite (#41214), this must mean no one is syncing repositories between gitolite and gitlab anymore. therefore, the @gitolite-merge-bot should be retired.
this probably means deactivating the account and removing all its accesses.legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41347Move tor-pristine-upstream.git to GitLab2023-11-29T22:24:59ZJérôme Charaouilavamind@torproject.orgMove tor-pristine-upstream.git to GitLabDuring a work session with @weasel today about releasing new tor versions to our Debian repository we agreed we should move over `tor-pristine-upstream.git` to GitLab, as it currently lives only on git-rw.tpo.During a work session with @weasel today about releasing new tor versions to our Debian repository we agreed we should move over `tor-pristine-upstream.git` to GitLab, as it currently lives only on git-rw.tpo.legacy Git infrastructure retirement (TPA-RFC-36)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41248Retire torproject-pusher GitHub account2023-08-02T18:04:56ZJérôme Charaouilavamind@torproject.orgRetire torproject-pusher GitHub accountWe currently have a `torproject-pusher` account that allows pushing commits from Gitolite (`cupani`) to GitHub. It used to also allow mirroring from tpo/web/lego and tpo/web/manual, but I migrated those to project-specifc deploy keys in ...We currently have a `torproject-pusher` account that allows pushing commits from Gitolite (`cupani`) to GitHub. It used to also allow mirroring from tpo/web/lego and tpo/web/manual, but I migrated those to project-specifc deploy keys in #41246.
In light of the migration off Gitolite, we should retire this account.legacy Git infrastructure retirement (TPA-RFC-36)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org2023-08-03https://gitlab.torproject.org/tpo/tpa/team/-/issues/41236gitolite: Redirect tor.git to Gitlab2023-06-26T16:15:35ZDavid Gouletdgoulet@torproject.orggitolite: Redirect tor.git to GitlabHello,
Network team is ready to have `tor.git` on Gitolite to be redirected to Gitlab and thus become canonical repository:
https://gitweb.torproject.org/tor.git -> https://gitlab.torproject.org/tpo/core/tor
Thanks!Hello,
Network team is ready to have `tor.git` on Gitolite to be redirected to Gitlab and thus become canonical repository:
https://gitweb.torproject.org/tor.git -> https://gitlab.torproject.org/tpo/core/tor
Thanks!legacy Git infrastructure retirement (TPA-RFC-36)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41235Redirect and destroy stem.git gitolite to Gitlab2023-06-26T16:15:01ZjugaRedirect and destroy stem.git gitolite to GitlabWe've just migrated stem to gitlab (https://gitlab.torproject.org/tpo/network-health/team/-/issues/307), so you can now destroy the one at https://gitweb.torproject.org/stem.git and redirect it to https://gitlab.torproject.org/tpo/networ...We've just migrated stem to gitlab (https://gitlab.torproject.org/tpo/network-health/team/-/issues/307), so you can now destroy the one at https://gitweb.torproject.org/stem.git and redirect it to https://gitlab.torproject.org/tpo/network-health/stem.git
Thanks!legacy Git infrastructure retirement (TPA-RFC-36)https://gitlab.torproject.org/tpo/tpa/team/-/issues/41232gitolite: Redirect or close several projects for Network Team2023-06-26T16:14:38ZDavid Gouletdgoulet@torproject.orggitolite: Redirect or close several projects for Network TeamGreetings,
The following can simply be **closed** without any redirections:
- https://gitweb.torproject.org/testnet.git/
- https://gitweb.torproject.org/tor-rust-dependencies.git/
The following should be **redirected**:
- https://git...Greetings,
The following can simply be **closed** without any redirections:
- https://gitweb.torproject.org/testnet.git/
- https://gitweb.torproject.org/tor-rust-dependencies.git/
The following should be **redirected**:
- https://gitweb.torproject.org/fallback-scripts.git/ -> https://gitlab.torproject.org/tpo/core/fallback-scripts
- https://gitweb.torproject.org/chutney.git/ -> https://gitlab.torproject.org/tpo/core/chutney
- https://gitweb.torproject.org/fuzzing-corpora.git/ -> https://gitlab.torproject.org/tpo/core/fuzzing-corpora
- https://gitweb.torproject.org/trunnel.git/ -> https://gitlab.torproject.org/tpo/core/trunnellegacy Git infrastructure retirement (TPA-RFC-36)https://gitlab.torproject.org/tpo/tpa/team/-/issues/41230git: Redirect torspec.git gitolite to Gitlab2023-06-26T18:56:28ZDavid Gouletdgoulet@torproject.orggit: Redirect torspec.git gitolite to GitlabGreetings TPA team!
If you could setup the redirection from
https://gitweb.torproject.org/torspec.git -> https://gitlab.torproject.org/tpo/core/torspec
On our side, we will make the Gitlab repository the canonical one for torspec and...Greetings TPA team!
If you could setup the redirection from
https://gitweb.torproject.org/torspec.git -> https://gitlab.torproject.org/tpo/core/torspec
On our side, we will make the Gitlab repository the canonical one for torspec and thus push there by default form now on.
Note that at the moment, we push to gitolite and there is a hook pushing to Gitlab. This of course, is not needed anymore :).legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41214review gitolite retirement progress and send a reminder2024-03-20T18:56:12Zanarcatreview gitolite retirement progress and send a reminderAs part of the Gitolite retirement procedure (TPA-RFC-36, #41180), review the progress of the migration and send a reminder:
- [x] how many repositories are left to migrate, populating #41215 with the result
- [x] did any repository get...As part of the Gitolite retirement procedure (TPA-RFC-36, #41180), review the progress of the migration and send a reminder:
- [x] how many repositories are left to migrate, populating #41215 with the result
- [x] did any repository get changes since the deprecation notice on 2023-06-08
- [x] send a reminder, similar to #41212legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcat2024-01-24https://gitlab.torproject.org/tpo/tpa/team/-/issues/41213lock down legacy git infrastructure2024-03-26T20:49:37Zanarcatlock down legacy git infrastructureAs part of the Gitolite retirement procedure (TPA-RFC-36, #41180), lock Gitolite repositories without any changes in the last
two years, preventing any further change.As part of the Gitolite retirement procedure (TPA-RFC-36, #41180), lock Gitolite repositories without any changes in the last
two years, preventing any further change.legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcat2024-01-31https://gitlab.torproject.org/tpo/tpa/team/-/issues/41212announce gitolite/gitweb deprecation to the community2023-06-08T18:11:37Zanarcatannounce gitolite/gitweb deprecation to the communityin #41180 we decided to migrate fully to GitLab, make people aware.
there will be a banner on the site (#41211 ) but we should also do an email announcement.in #41180 we decided to migrate fully to GitLab, make people aware.
there will be a banner on the site (#41211 ) but we should also do an email announcement.legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41211add a banner on legacy git servers to announce deprecation and migration2023-06-08T18:02:25Zanarcatadd a banner on legacy git servers to announce deprecation and migrationthere should be a banner of some sort on the git servers to announce their deprecation.there should be a banner of some sort on the git servers to announce their deprecation.legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcat2023-06-08https://gitlab.torproject.org/tpo/tpa/team/-/issues/41195More anti-censorship repositories to migrate2023-06-08T17:42:47Zmeskiomeskio@torproject.orgMore anti-censorship repositories to migrate| gitolite | gitlab | fate |
| ------ | ------ | -----|
| bridgedb.git | tpo/anti-censorship/bridgedb | migrate |
| project/bridges/bridgedb-admin.git | tpo/anti-censorship/bridgedb-admin | migrate || gitolite | gitlab | fate |
| ------ | ------ | -----|
| bridgedb.git | tpo/anti-censorship/bridgedb | migrate |
| project/bridges/bridgedb-admin.git | tpo/anti-censorship/bridgedb-admin | migrate |legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41193Redirect pluggable-transports to GitLab2023-06-08T17:42:47Zmeskiomeskio@torproject.orgRedirect pluggable-transports to GitLabI've migrated these repositories:
| gitolite | gitlab | fate |
| ------ | ------ | -----|
| pluggable-transports/httpsproxy.git | tpo/anti-censorship/pluggable-transports/httpsproxy | archive |
| pluggable-transports/obfs4.git | tpo/an...I've migrated these repositories:
| gitolite | gitlab | fate |
| ------ | ------ | -----|
| pluggable-transports/httpsproxy.git | tpo/anti-censorship/pluggable-transports/httpsproxy | archive |
| pluggable-transports/obfs4.git | tpo/anti-censorship/pluggable-transports/lyrebird | migrate |
| pluggable-transports/obfsproxy.git | tpo/anti-censorship/pluggable-transports/obfsproxy | archive |
| pluggable-transports/obfsproxy-legacy.git | tpo/anti-censorship/pluggable-transports/obfsproxy-legacy | archive |
| pluggable-transports/pyptlib.git | tpo/anti-censorship/pluggable-transports/pyptlib | archive |
| pluggable-transports/snowflake.git | tpo/anti-censorship/pluggable-transports/snowflake | migrate |
| pluggable-transports/snowflake-mobile.git | tpo/anti-censorship/pluggable-transports/snowflake-mobile | migrate |
| pluggable-transports/snowflake-webext.git | tpo/anti-censorship/pluggable-transports/snowflake-webext | migrate |
| pluggable-transports/websocket.git | tpo/anti-censorship/pluggable-transports/websocket | archive |legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41190Redirect pluggable-transports/{bundle.git,fog.git} to GitLab2023-06-08T17:42:47ZDavid Fifielddcf@torproject.orgRedirect pluggable-transports/{bundle.git,fog.git} to GitLab(Following [migration instructions](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/git?version_id=1f73e6c85b6645782b2348fa368dc278d182bb56#user-part-importing-the-repository-into-gitlab).)
In addition to those in tpo/tpa/team#...(Following [migration instructions](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/git?version_id=1f73e6c85b6645782b2348fa368dc278d182bb56#user-part-importing-the-repository-into-gitlab).)
In addition to those in tpo/tpa/team#41182,
I've also migrated these repositories I am responsible for.
Both of them have been archived.
|gitolite|gitlab|fate|
|---|---|---|
|/pluggable-transports/bundle.git|/tpo/anti-censorship/pt-bundle|archive|
|/pluggable-transports/fog.git|/tpo/anti-censorship/pluggable-transports/fog|archive|legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41189Migrating (etc) nickm's gitolite repositories.2023-07-04T13:58:51ZNick MathewsonMigrating (etc) nickm's gitolite repositories.Hello!
I believe that the following should be *archived*:
* `user/nickm/calltool`
* `user/nickm/tor`
* `user/nickm/tor-ideas`
* `user/nickm/tor-roadmaps`
* `user/nickm/torspec`
I believe that all other `user/nickm` repositories s...Hello!
I believe that the following should be *archived*:
* `user/nickm/calltool`
* `user/nickm/tor`
* `user/nickm/tor-ideas`
* `user/nickm/tor-roadmaps`
* `user/nickm/torspec`
I believe that all other `user/nickm` repositories should be destroyed, namely:
```
@ W user/nickm/bridgedb
@ W user/nickm/githax
R W user/nickm/libevent-ideas
@ W user/nickm/trunnel
```legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcat2023-06-09https://gitlab.torproject.org/tpo/tpa/team/-/issues/41182Redirect goptlib, meek, flashproxy repositories to GitLab2023-06-08T17:42:47ZDavid Fifielddcf@torproject.orgRedirect goptlib, meek, flashproxy repositories to GitLab(Following [migration instructions](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/git?version_id=1f73e6c85b6645782b2348fa368dc278d182bb56#user-part-importing-the-repository-into-gitlab).)
These repositories that I am responsi...(Following [migration instructions](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/git?version_id=1f73e6c85b6645782b2348fa368dc278d182bb56#user-part-importing-the-repository-into-gitlab).)
These repositories that I am responsible for have been moved to GitLab and need redirects.
The flashproxy respository has additionally been "archived" in GitLab.
|gitolite|gitlab|fate|
|---|---|---|
|/pluggable-transports/goptlib.git|/tpo/anti-censorship/pluggable-transports/goptlib|migrate|
|/pluggable-transports/meek.git|/tpo/anti-censorship/pluggable-transports/meek|migrate|
|/flashproxy.git|/tpo/anti-censorship/pluggable-transports|archive|legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41181redirect applications team repositories to GitLab2023-06-08T17:42:47Zanarcatredirect applications team repositories to GitLabin 2020, the applications team [announced their gitolite repositories were deprecated](https://lists.torproject.org/pipermail/tor-project/2022-December/003518.html). those are the repositories that need to be redirected by TPA and have a...in 2020, the applications team [announced their gitolite repositories were deprecated](https://lists.torproject.org/pipermail/tor-project/2022-December/003518.html). those are the repositories that need to be redirected by TPA and have already been imported in GitLab:
| gitolite | gitlab | fate |
|----------------------------|--------------------------------------|---------|
| builders/tor-browser-build | tpo/applications/tor-browser-build | migrate |
| builders/rbm | tpo/applications/rbm | migrate |
| tor-android-service | tpo/applications/tor-android-service | migrate |
| tor-browser | tpo/applications/tor-browser/ | migrate |
| tor-browser-spec | tpo/applications/tor-browser-spec | migrate |
| tor-launcher | tpo/applications/tor-launcher | archive |
| torbutton | tpo/applications/torbutton | archive |legacy Git infrastructure retirement (TPA-RFC-36)anarcatanarcat