Web Team issueshttps://gitlab.torproject.org/tpo/web/team/-/issues2022-03-24T19:23:36Zhttps://gitlab.torproject.org/tpo/web/team/-/issues/18Redirect old t-shirt page to new swag page2022-03-24T19:23:36ZKatRedirect old t-shirt page to new swag pagehttps://2019.www.torproject.org/getinvolved/tshirt.html should redirect to https://community.torproject.org/relay/community-resources/swag/
The old URL is shared widely on social media. When people go to the old page, they end up on the...https://2019.www.torproject.org/getinvolved/tshirt.html should redirect to https://community.torproject.org/relay/community-resources/swag/
The old URL is shared widely on social media. When people go to the old page, they end up on the old t-shirt inventory wiki page, which is no longer maintained.https://gitlab.torproject.org/tpo/web/team/-/issues/13archive 2019.www.torproject.org permanently2021-11-04T00:43:39Zanarcatarchive 2019.www.torproject.org permanentlyThe old website (https://2019.www.torproject.org/) has been replaced with the new, lektor-based website (https://www.torproject.org/) well over two years ago now. Since then (ie. since september 2019), only two commits were added to the ...The old website (https://2019.www.torproject.org/) has been replaced with the new, lektor-based website (https://www.torproject.org/) well over two years ago now. Since then (ie. since september 2019), only two commits were added to the [git repository](https://gitweb.torproject.org/project/web/webwml.git). And one of those was:
```
From 57b9f564bc03505e0189c2c22a9d2c7aa47c2ea1 Mon Sep 17 00:00:00 2001
From: gus <gus@torproject.org>
Date: Mon, 27 Apr 2020 15:48:17 -0400
Subject: Fix #26 - Notify users that 2019.www is an outdated website
```
I think it's time to completely archive the website. Concretely, that means it will not be migrated to GitLab CI, the Git repository will be disabled in gitolite (but still migrated to GitLab and archived), and no further changes should be performed on the site.
We can still make redirections if we need to redirect people away from old content, but I think whatever work that remained to be done on the site could have been done already, nothing is going to happen now that is going to make this magically worth it.
I bring this up now because otherwise this is one of the websites that would need to be migrated to GitLab CI. It's going to be much less work to simply archive it. If we want to revert that decision, we can still implement the site build in GitLab CI in the future, but I would strongly advise looking for other solutions instead.
Another reason I bring this up is that the site actually doesn't build at all right now, because of the tor.git repository change (tpo/tpa/team#40450). It hardly seems worth fixing this in Jenkins just to turn around and have to redo the fix in GitLab CI again...
retirement checklist:
* [x] [archive the repo on gitolite](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/gitlab/#how-to-migrate-a-git-repository-from-legacy-to-gitlab)
* [x] [fully retire the Jenkins jobs](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/jenkins#removing-a-job)
* [x] notify users about the migrationRetire Jenkinsanarcatanarcathttps://gitlab.torproject.org/tpo/web/team/-/issues/12Lektor adds text from po files when building on debian 11 / python 3.9.22021-11-08T19:20:27ZHackerNCoderhackerncoder@encryptionin.spaceLektor adds text from po files when building on debian 11 / python 3.9.2See https://community.pages.tor.encryptionin.space/
My server is running deb 11 and python 3.9.2, no matter how I have installed lektor the above is the result.
My local dev whonix is based on deb 10 and has python 3.7.3, I am running...See https://community.pages.tor.encryptionin.space/
My server is running deb 11 and python 3.9.2, no matter how I have installed lektor the above is the result.
My local dev whonix is based on deb 10 and has python 3.7.3, I am running lektor from source, the result of building is what it should be (no extra po file text)https://gitlab.torproject.org/tpo/web/team/-/issues/8Remove Documentation -> 2019.www.torproject.org from the menu2021-10-07T13:35:42ZGusRemove Documentation -> 2019.www.torproject.org from the menuWe have too many users visiting the old Tor docs and getting lost or using old instructions. That is because of search engines, but also because we say "Documentation," but most of the docs there live in the Support portal and Community ...We have too many users visiting the old Tor docs and getting lost or using old instructions. That is because of search engines, but also because we say "Documentation," but most of the docs there live in the Support portal and Community portal.
As the main team plan was to replace it with a new developer portal (See: tpo/web/dev), I would like to track the minimal work we need to do to remove that website from the header once for all.
### Tasks
* [ ] Finish old FAQ migration to support portal: https://gitlab.torproject.org/tpo/web/support/-/issues/43
* [ ] Find a new home for little-t-tor manual [stable](https://2019.www.torproject.org/docs/tor-manual.html.en) and [alpha](https://2019.www.torproject.org/docs/tor-manual-dev.html.en). see also: https://gitlab.torproject.org/tpo/core/tor/-/issues/40418
* [ ] Find a temporary place to move this document Tor Browser Design document - https://2019.www.torproject.org/projects/torbrowser/design/https://gitlab.torproject.org/tpo/web/team/-/issues/4create default gitlabCI.yaml file for lektor websites2021-10-07T16:23:34Zemmapeelcreate default gitlabCI.yaml file for lektor websitesAs we are moving out of jenkins to gitlabCI, we need to create a default gitlabCI file for our lektor websites.
The integration with gitlabCI will also help us to review merge requests, as merge requests should get results and appear un...As we are moving out of jenkins to gitlabCI, we need to create a default gitlabCI file for our lektor websites.
The integration with gitlabCI will also help us to review merge requests, as merge requests should get results and appear under users gitlab 'pages'.
First version was made by Gus at https://gitlab.torproject.org/tpo/web/support/-/snippets/89
I have made some changes and they are at https://gitlab.torproject.org/tpo/manual/-/blob/translations/.gitlab-ci.yml
There are still some unresolved issues:
- [x] The translations are not complete
- [ ] The packages are not the same we use on production, especially lektor and lektor-i18n package
- [ ] reduce the traffic w/docker, maybe have local images ready
- [ ] test before build
- [ ] stop spamming tor-bots (it is sending a minimum of 3 messages per event)
- [ ] the gitlabCI.yaml file should be configured in a way that allows contributors without commit rights on the repo to push a branch to their own fork and be able to see the build on their own 'pages'. This will allow them to preview their changes before submitting the merge request, without the need to install lektor and build it in local.Retire Jenkinshttps://gitlab.torproject.org/tpo/web/team/-/issues/3Please post metrics job description to website2021-02-05T14:00:44ZErin WyattPlease post metrics job description to websitePlease add this job description to the website. Thank you!
Internet Freedom Nonprofit Seeks Metrics Data Architect
February 4, 2021
The Tor Project, Inc., a 501(c)(3) nonprofit organization advancing human rights and freedoms by cre...Please add this job description to the website. Thank you!
Internet Freedom Nonprofit Seeks Metrics Data Architect
February 4, 2021
The Tor Project, Inc., a 501(c)(3) nonprofit organization advancing human rights and freedoms by creating and deploying free and open source anonymity and privacy technologies, is seeking an experienced Data Architect to take our metrics work to the next level.
Tor is for everyone, and we are actively working to build a team that represents people from all over the world — people from diverse ethnic, national, and cultural backgrounds; people from all walks of life. Racial minorities, non-gender-binary people, women, and people from any group that is generally underrepresented in tech are encouraged to apply.
This is a full-time remote position.
The team:
Historically our Metrics Team has been collecting data since 2004 to help improve the tools we build and learn more about the Tor network. For example, we monitor the number of relays and clients in the network, their respective capabilities, the number of clients connecting via bridges, fluctuations in network speed, etc. Gathering this data results in huge data archives, so we are also working to develop tools to process this data and make it available to everyone.
How we achieve our goals:
Robustness (We want to avoid bugs and/or bad design decisions that cause us to miss data)
Timeliness (users need up-to-date network status information)
Scalability (as the network grows, so does our data)
Transparency (our community rightly wants to know what data we're collecting)
The most interesting challenge for metrics collection at Tor is how to gather data on an anonymity system without de-anonymizing users.
We are integrating the metrics team with a new network health team that will be also focusing on taking care of the health of the Tor network. Additionally, Tor has just begin a large network performance improvement project that will vastly increase network utilization and client performance. There will be close interaction between this role and our performance effort, in the form of ensuring data is collected properly during deployment of new performance features and performance tuning. This will also include producing custom visualizations, doing analysis, and comparisons between historical and current data.
The job:
The person in this position will work directly with helping us maintain existing systems, and design new systems for gathering and analyzing data. They will help the rest of the teams understand the data available to improve our tools as well as the Tor network's health.
The bulk of our code is written in Java, but smaller portions are written in R, Python, PostgreSQL, and JavaScript. Part of this job will be to analyze and fix bugs in our current code and review patches.
You will be working with the existing teams in Tor with support and advice on data collection and measurements for their needs in their respective projects.
Our main five codebases:
- Collector (https://gitweb.torproject.org/collector.git/ )
- metrics-lib (https://gitweb.torproject.org/metrics-lib.git/ )
- Onionoo (https://gitweb.torproject.org/onionoo.git/ )
- Exonerator (https://gitweb.torproject.org/exonerator.git/ )
- metrics-web (https://gitweb.torproject.org/metrics-web.git/ )
Requirements:
Technical abilities/experience:
- Have experience finding your way into existing Java, R, and PostgreSQL-based code bases and the ability to review patches and make changes to fix bugs/smaller enhancements.
- Have experience with web application development in the Python programming language. Experience with known frameworks is a plus.
- Able to identify shortcomings in our data pipeline and suggest improvements to reduce complexity and future maintenance efforts.
- Experience working with Git and Gitlab or similar issue tracking tools.
- Ability to learn quickly and can adapt to our current processes; being able to improve future processes for releasing software and operating services.
- Understanding of the inherent privacy implications of gathering data in an anonymity system, the security implications of gathering metrics data from semi-trusted relays in the Tor network, and the challenges of processing large amounts of data per day (specifically performance and scalability challenges).
- Data analysis: Ability to make sense of data sets and use data analysis tools to find and visualize interesting patterns.
- Mathematics: Knowledge of basic statistics.
Collaborative requirements:
- Ability to work remotely 100% of the time, as synchronization happens via email and/or IRC.
- Participation in weekly IRC meetings and monthly team video chats.
- Language: write and speak fluent English.
- Comfortable posting to a public mailing list or speaking up in a public IRC channel to ask questions, even when you think the question might be obvious or silly.
Bonus skills:
- Open source experience: You have contributed to an open source project before, and you're accustomed to a pattern of early and frequent releases without attempting to finalize things on your own.
- Scientific writing: Experience writing technical reports about data findings.
- Networking background: Experience working with networks and measurements in the past.
- You support Internet Freedom!
To apply, submit a cover letter, your CV/resume (including three professional references), and a link to a code sample or some non-trivial software project you have significantly contributed to. In your cover letter, please include the reason you want to work at the Tor Project.
IMPORTANT: Please email application materials in plain text or PDF format to job-metrics at torproject dot org with “Metrics Data Architect” in the subject line.
The Tor Project's workforce is smart, committed, and hard working. We currently have a paid and contract staff of around 24 developers and operational support people, plus many thousands of volunteers who contribute to our work. The Tor Project is funded in part by government research and development grants, and in part by individual, foundation, and corporate donations.
Salary for this position depends on experience and there is voluntary opt-in salary transparency for employees and contractors.
The Tor Project has a competitive benefits package, including a generous PTO policy, 16 paid holidays per year (including the week between Christmas and New Year's, when the office is closed), and flexible work schedule. Insurance benefits vary by employment status and country of residence.
The Tor Project, Inc., is an equal opportunity, affirmative action employer.2021-02-05https://gitlab.torproject.org/tpo/web/team/-/issues/2Please add job opening to website2021-01-20T13:17:13ZErin WyattPlease add job opening to websitePlease add this job description to the website at https://www.torproject.org/about/jobs/. Thank you!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Internet Freedom Nonprofit Seeks Software Developer for Anti-Censorship Team
January ...Please add this job description to the website at https://www.torproject.org/about/jobs/. Thank you!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Internet Freedom Nonprofit Seeks Software Developer for Anti-Censorship Team
January 20, 2021
The Tor Project, Inc., a 501(c)(3) nonprofit organization advancing human rights and freedoms by creating and deploying free and open source anonymity and privacy technologies, is seeking an experienced Software Developer to take our anti-censorship work to the next level.
This developer will be tasked with improving the user experience and process of finding alternate routes to the Tor network when global censorship events block access to the Tor network. A personal commitment to free and open source software and the application of advanced programming skills for the greater good is essential.
This is a full-time remote position.
This developer position will be an integral part of our Anti-Censorship Team. Main responsibilities for this position are:
- - Continue development of our bridge distribution system, rdsys.
- - Maintain and improve the pipeline that distributes bridges to censored users.
- - Evaluate and incorporate new pluggable transports.
- - Collaborate with other teams in the Tor Project, external software projects (e.g. OONI), and research groups to move forward anti-censorship technology.
Required qualifications:
- - Experience with designing, implementing, testing, and reviewing complex codebases (ideally in Go and Python).
- - Ability to work in a self-directed and independent way.
- - Comfortable with working remotely, across time zones.
- - Strong familiarity with computer science fundamentals.
- - Familiarity with Internet security and censorship circumvention technologies.
Preferred qualifications:
- - Familiarity with reading research papers and turning research ideas into prototypes.
- - Understanding of the Tor pluggable transport ecosystem and the censorship circumvention research space.
- - Past contributions to and familiarity with the practices of free software projects.
- - Passion and dedication to Internet freedom is an added plus.
To apply, submit a cover letter, your CV/resume (including three professional references), and a link to a code sample or some non-trivial software project you have significantly contributed to. In your cover letter, please include the reason you want to work at the Tor Project.
IMPORTANT: Please email application materials in plain text or PDF format, if possible, to job-anticensor at torproject dot org with “Anti-Censorship Developer” in the subject line.
Tor is for everyone, and we are actively working to build a team that represents people from all over the world — people from diverse ethnic, national, and cultural backgrounds – people from all walks of life. We encourage applications from BIPOC, non-cis people, women, and from people in any group that is underrepresented in tech.
The Tor Project's workforce is smart, committed, and hard working. We currently have a paid and contract staff of around 24 developers and operational support people, plus many thousands of volunteers who contribute to our work. The Tor Project is funded in part by government research and development grants, and in part by individual, foundation, and corporate donations.
Salary for this position depends on experience and there is voluntary opt-in salary transparency for employees and contractors.
The Tor Project has a competitive benefits package, including a generous PTO policy, 16 paid holidays per year (including the week between Christmas and New Year's, when the office is closed), and flexible work schedule. Insurance benefits vary by employment status and country of residence.
The Tor Project, Inc., is an equal opportunity, affirmative action employer.
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIzBAEBCgAdFiEENecqn2ZVRfkstmYkugyUAPgPkc4FAmAHe5YACgkQugyUAPgP
kc4cTRAAlxVmQ+smVr/r8h0GcSxygU/8YLjR/5I76GA4bjFudPbuc1g5ZhX5ArZw
e7QFonj6pVuYs2qTH9OBbiLv5Tn8pLvDYb7JxOfr/6o42sSjOHL3LjV13B/4PtaP
tHLzTnH0o87vUl0DTEc1iAYr0R0yCEPl3EhTArYvZ/2tyj6s3AdSwbBiYInXo6bq
NB+6YyGZC1zYN2PzWg/Ip2pBQmkLm/n+VcmexfUNAnTj2EO6FSAJlWbRv2Kp2mAO
hBegT9MI/GJWm7Fk5eobxScxQoxoAmR3oZO8swFVwGWIhKCJGTwH6iAbVkln03mI
CyBCjtnf346+iEqzAoRK0SJokRNlzsz/q2I6AN3hVQaVHCiq6X8jmbzC9ssChhAQ
lA4/UYYrrIi8zYFPsMMoi3ZmXUzxV3SqGO4XLqStbcuBvINntZXmQ2C38rjtjixR
hRydIfVp2o2rsZsoOljiYfd+d81kNA5XzogcfzSRglkJ+OEtPuqbUEY1ppPbJq38
7ZCRctGmJiYhsdV7IC6/w/HUJvvJd/jisl0e/oZTqJf7NIMNam5zyqAwFS6KGVYk
kyjEfaf79lCDddCNIwcoQ/XHtbZg0pnw5DXFCAfrOiFegnDbs8aq6WfOt4Ak+D7q
NjkZkTC+Cb9bKyZqZ4m2g4EP1KXr1AI0RlQEE4vsX3AWY20+zpc=
=OjD/
-----END PGP SIGNATURE-----HiroHiro2021-01-20