The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-12-11T09:55:56Zhttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/134Add documentation on how to build documentation, run tests and add example co...2023-12-11T09:55:56ZjugaAdd documentation on how to build documentation, run tests and add example configurationsjugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/107Move all or part of the documentation about Tor and the bandwidth scanner2023-12-11T09:51:28ZjugaMove all or part of the documentation about Tor and the bandwidth scannerI've writing documentation in https://onbasca.readthedocs.io/ that i didn't know where else could go.
Some of it might be useful only for me but some might be useful for other people and should be in Tor project domain.I've writing documentation in https://onbasca.readthedocs.io/ that i didn't know where else could go.
Some of it might be useful only for me but some might be useful for other people and should be in Tor project domain.jugajugahttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/15Onion Reveal coding and documenting2023-12-11T09:46:02ZSilvio RhattoOnion Reveal coding and documenting# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
- @gus
- etc
# Summary
This is a proposal to write a [reveal.js](https://revealjs.com/) compiler similar...# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
- @gus
- etc
# Summary
This is a proposal to write a [reveal.js](https://revealjs.com/) compiler similar to [Onion TeX Slim][].
[Onion TeX Slim]: https://gitlab.torproject.org/rhatto/onion-tex-slim
## Project A - Writing
The first project in this proposal would be to actually write Onion Reveal. This software could work like this:
* [x] Use a Makefile/script target that traverses a folder looking for `.md` files.
* [x] Then it would build the HTML slides using a pandoc reveal template.
* [x] With CI/CD for automation, in a way that's easy to integrate into existing projects.
* [x] Localization support.
* [ ] With support for QR code generation, so it's easy to embed QR codes into slides.
Examples:
* [Files · main · The Tor Project / Web / community · GitLab](https://gitlab.torproject.org/tpo/web/community/-/tree/main)
* [templates/slideshow.html · main · The Tor Project / Web / community](https://gitlab.torproject.org/tpo/web/community/-/blob/main/templates/slideshow.html)
* [models/slideshow.ini · main · The Tor Project / Web / community](https://gitlab.torproject.org/tpo/web/community/-/blob/main/models/slideshow.ini)
* [assets/static/revealjs/dist/theme/tor.css · community](https://gitlab.torproject.org/tpo/web/community/-/blob/main/assets/static/revealjs/dist/theme/tor.css)
* [Helping Survivors of Domestic Violence](https://community.torproject.org/training/resources/helping-survivors/)
## Project B - Trying
* [x] Use this project to build some presentations:
* [x] Tor Training materials: tpo/community/training#122.
Related issues:
* [Make Tor training slides compatible with Reveal JS format (#268) · community](https://gitlab.torproject.org/tpo/web/community/-/issues/268)
Examples:
* [Tor Project | Helping survivors of domestic violence](https://community.torproject.org/training/resources/helping-survivors/)
* [content/training/resources/helping-survivors/contents.lr · community](https://gitlab.torproject.org/tpo/web/community/-/blob/main/content/training/resources/helping-survivors/contents.lr)
# Skills
Some knowledge in the following technologies may be needed in order to participate:
* Git/GitLab.
* Markdown.
* Writing documentation.
* Basic scripting (Python, shell).
# LinksHackweek 2023Silvio RhattoSilvio Rhatto2023-11-09https://gitlab.torproject.org/tpo/community/hackweek/-/issues/30design.torproject.org2023-12-08T21:30:56Zdonutsdesign.torproject.org# About the project
* Contact: @donuts
* Chat: **#tor-ux** on `irc.oftc.net`
* Video room: message donuts for the link
# Participants
- @donuts
- @jag
- @nicob
# Summary
The UX Team have been discussing replacing the [existing ...# About the project
* Contact: @donuts
* Chat: **#tor-ux** on `irc.oftc.net`
* Video room: message donuts for the link
# Participants
- @donuts
- @jag
- @nicob
# Summary
The UX Team have been discussing replacing the [existing styleguide](http://styleguide.torproject.org) with a new resource that's wider in scope – e.g. "design.torproject.org". In addition to updating our brand and web guidelines given their evolution over the past few years, we're also considering adding new sections to document our human-centered design principals, user research program, and overall methodology. The revised portal should serve as a central point of reference for external resources too, including for example our Figma libraries for the browser, web and VPN, and any open source design resources we use.
Given the large scope of this project, it's expected that we'll make some progress in planning the structure, content and design of the new portal – however we'll likely need to wait for a second hackweek or future funding opportunity to complete the implementation.
**Hackweek goals:**
- [x] Site map
- [x] Some content planning/development
- [ ] Figma prototype
- [ ] Basic HTML templates (stretch goal)
# Requirements
Institutional knowledge:
- Direct knowledge of the Tor Project's brand, design systems, user experience and/or user research practices.
- Or the ability to communicate your needs as a consumer of this documentation.
Technical skills:
- Graphic and/or web design (required)
- Front-end development (optional)
- Experience with lektor (optional)
# Links
Existing documentation:
- [Tor Project Styleguide](https://styleguide.torproject.org)
- [Community / User Research](https://community.torproject.org/user-research/)
- [User Research repo](https://gitlab.torproject.org/tpo/ux/research)
- [Firefox Acorn](https://acorn.firefox.com/latest/acorn-aRSAh0Sp) (external)
Design libraries:
- [Tor Browser for Desktop](https://www.figma.com/file/RtZ0fqkNMRc7GOjK3FLclz/Tor-Browser-for-Desktop?type=design&node-id=611%3A55&mode=design&t=1YIBBFxWnpmQUHwP-1)
- [Tor Browser for Android](https://www.figma.com/file/LaU3qFpem2xQOfBF6MEYVR/Tor-Browser-for-Android?type=design&node-id=611%3A55&mode=design&t=mjkrcP2LegGQLM8K-1)
- [Icons & Illustrations](https://www.figma.com/file/sd4yASXsToxFECsraTlAsw/Icons-%26-illustrations?type=design&node-id=0%3A1&mode=design&t=jGmz3Uwj5OmdsGoK-1)Hackweek 2023donutsdonutshttps://gitlab.torproject.org/tpo/web/donate-static/-/issues/35Update the donors FAQ2023-12-05T21:59:40ZemmapeelUpdate the donors FAQThe [donors FAQ](https://donate.torproject.org/donor-faq/) is a bit outdated.
There is also too many questions, we should simplify and not duplicate Tor Project FAQs, but replace them, for example, with links to the Support portal.
We h...The [donors FAQ](https://donate.torproject.org/donor-faq/) is a bit outdated.
There is also too many questions, we should simplify and not duplicate Tor Project FAQs, but replace them, for example, with links to the Support portal.
We have opened a pad to work on the changes at
http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/donateFAQ6hS-wFdjD7QyebyfuCCFRedesign donate.torproject.orghttps://gitlab.torproject.org/tpo/web/community/-/issues/180where to put the onion service webserver socket?2023-12-05T21:19:23ZRoger Dingledinewhere to put the onion service webserver socket?On https://community.torproject.org/onion-services/setup/ we have the suggestion
```
HiddenServiceDir /var/lib/tor/my-website/
HiddenServicePort 80 unix:/var/run/tor-my-website.sock
```
That second line looks weird -- it looks like they...On https://community.torproject.org/onion-services/setup/ we have the suggestion
```
HiddenServiceDir /var/lib/tor/my-website/
HiddenServicePort 80 unix:/var/run/tor-my-website.sock
```
That second line looks weird -- it looks like they meant to say "/var/run/tor/" but didn't.
Where should we recommend to put the unix socket for the webserver? Maybe the nginx package has a typical place it expects to be able to create its socket? I would expect that on my standard system, my webserver wouldn't be able to write to /var/run/ *or* to /var/run/tor/.Silvio RhattoSilvio Rhattohttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/15User permissions in TPO2023-12-05T18:45:51ZGabagaba@torproject.orgUser permissions in TPO- [ ] Move this into guides/documentation
- [ ] Include clear criteria on when to create an account in gitlab and how to assign permissions.
- [x] Can somebody else review who has permission to what group under tpo? Right now we have
tp...- [ ] Move this into guides/documentation
- [ ] Include clear criteria on when to create an account in gitlab and how to assign permissions.
- [x] Can somebody else review who has permission to what group under tpo? Right now we have
tpo:
* gaba - owner
* isabela - reporter
* roger - reporter
core:
* dgoulet - owner
* asn - owner
* nickm - owner
* ahf - owner
* gaba - owner
tpa:
* ahf-admin - owner
* hiro - owner
* weasel - owner
* gaba - owner
applications:
* acat - owner
* ahf-admin - owner
* antonela - owner
* sysrqb - owner
* gk - owner
* brade - developer
* mcs - developer
* bolkm - developer
* gaba - owner
ux:
* antonela - owner
* diogosergio - maintainer
* pili - maintainer
* emmapeel - maintainer
* torproject-pusher - maintainer
* nah - develper
* dunqan - developer
* gaba - owner
community:
* gus - owner
* pili - owner
* kat - guest
* alison - mantainer
* kushal - developer
* emmapeel - developer
* gaba - owner
metrics:
* ahf-admin - owner
* karsten - owner
* acute - developer
* djackson - developer
* phw - developer
* gaba - owner
anti-censorship:
* cohosh - owner
* phw - owner
* hiro- developer
* arma - developer
* gaba - owner
* antonela - developer
network health:
* dgoulet - owner
* gk - owner
* phw - owner
* arma - owner
* gaba - owner
web:
* gus - owner
* hiro - mantainer
* pili - maintainer
* emmapeel - maintainer
* torproject-ppusher - maintainer
* antonela - developer
* stephw - developer
* protechthor-guest - developer
* clash - reporter
* arma - reporter
* aya - developer
* bunnyapocalypse-guest - guest
* nemaniarjun-guest - guest
* claromes-guest - guest
* jacobo-guest - guest
* kjedidiahpark-guest - guest
* raviteja-guest
* rotationmatrix-guest - guest
* jaruga - guest
* gaba - owner
scalability:
* mikeperry - maintainer
* arma - maintainer
* gaba - owner
external users:
* all contributors that are not in a specific group/team. Limit projects creation to 5.
What should we change? I think we should at least remove admin users from ownership. They already have access to everything.
Permissions and roles in Gitlab: https://gitlab.torproject.org/help/user/permissionshttps://gitlab.torproject.org/tpo/onion-services/onion-support/-/issues/14Provide advice on the best way to monitor availability2023-12-05T14:53:12ZGusProvide advice on the best way to monitor availabilityNY Times and other onions wants a way to monitor their onion. @dgoulet might can help us here.NY Times and other onions wants a way to monitor their onion. @dgoulet might can help us here.Silvio RhattoSilvio Rhattohttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/25tor-browser-build project survey2023-12-01T14:28:56ZPier Angelo Vendrametor-browser-build project survey# About the project
* Contact: @pierov
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: nope
# Participants
- suggested: apps team members and other people who regularly use tor-browser-build or curious about it
- @boklm
...# About the project
* Contact: @pierov
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: nope
# Participants
- suggested: apps team members and other people who regularly use tor-browser-build or curious about it
- @boklm
# Summary
We have 120 projects in tor-browser-build.
Understand why we have some them is easy (e.g., Firefox), but some other are platform-dependent (e.g., the shenanigans that macOS signing needs), some other are Namecoin dependencies.
## Dependencies graph
It'd be great to create a graph with all the dependencies.
Hopefully it should contain just a single connected component (`browser`/`release`), or a few additional components that make sense to have (e.g., signing tools).
If we find components that don't make sense to have, we should then purge them from `tor-browser-build` (e.g., dependencies that aren't needed anymore and recursive dependencies).
I'd expect the graph to be directed and cyclical (some components depend on themselves with a different target).
So, we might find also some projects/nodes that just depend on other nodes, without being a dependency for anything.
We might want to purge them as well.
## Project readmes
At the moment, each project is required to have a `config` file, but most have also a `build` file.
It'd be great if we added a `README.md` (or something similar) to each project, to explain:
- what it is
- why we have it
- what we do here if it isn't trivial (e.g., for `browser`) and/or caveats of the build process (e.g., we have to do these additional steps because we cross compile, or we have to do also this for reproducible purposes)
- references (e.g., link to the website, when we follow Mozilla's build script, a reference to these build scripts, or known issues, such as NSIS requiring to be built with GCC).
# Skills
Know tor-browser-build (well, this documentation project might help knowing it more).
# LinksHackweek 2023Pier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/35Hackweek 2023 documentation2023-11-30T17:35:12ZSilvio RhattoHackweek 2023 documentationDocument the 2023 Hackweek.Document the 2023 Hackweek.Hackweek 2023Silvio RhattoSilvio Rhatto2023-12-07https://gitlab.torproject.org/tpo/community/hackweek/-/issues/12Create 2023 Documentation Hackweek proposals from a brainstorm2023-11-30T16:17:39ZSilvio RhattoCreate 2023 Documentation Hackweek proposals from a brainstormSome time ago I had a [quick brainstorm][] for the [2023 Documentation Hackweek][].
This ticket is about creating [proposal tickets][] from these ideas.
[quick brainstorm]: https://gitlab.torproject.org/tpo/team/-/issues/115#note_29165...Some time ago I had a [quick brainstorm][] for the [2023 Documentation Hackweek][].
This ticket is about creating [proposal tickets][] from these ideas.
[quick brainstorm]: https://gitlab.torproject.org/tpo/team/-/issues/115#note_2916524
[2023 Documentation Hackweek]: https://lists.torproject.org/pipermail/tor-project/2023-August/003675.html
[proposal tickets]: https://gitlab.torproject.org/tpo/community/hackweek/-/blob/main/.gitlab/issue_templates/Default.mdHackweek 2023Silvio RhattoSilvio Rhatto2023-10-17https://gitlab.torproject.org/tpo/community/hackweek/-/issues/6Hackweek 2023: call for proposals text2023-11-30T16:17:39ZSilvio RhattoHackweek 2023: call for proposals textCreate call for proposals text, inviting people to present proposals and join the Hackweek and including the following topics:
* [x] What:
* [x] Importance of documentation.
* [~] "How documentation affects me".
* [~] "How i can l...Create call for proposals text, inviting people to present proposals and join the Hackweek and including the following topics:
* [x] What:
* [x] Importance of documentation.
* [~] "How documentation affects me".
* [~] "How i can learn to help with this effort".
* [x] Why: goal of the Hackweek:
* [x] Explore how documentation is working or not in your projects.
* [x] Do problem-solving around documentation in the organization and projects we maintain.
* [x] Sharing the problems we have with documentation at Tor.
* [x] When: timeline:
* [x] Previous all hands meeting: people present the project they will work on.
* [x] During the Hackweek: people work on whatever they want related to
documentation (4-day Hackweek, from Mon to Thu).
* [x] Next all hands meeting: people present the project they worked on.
* [x] How: how the Hackweek is going to work (when, where):
* [x] People will add proposals to [Hackweek's issue tracker][] using an
[issue template][] and others can join to work together.
* [x] In order to join a proposal, subscribe yourself to it's ticket.
* [x] Accepting documentation in all formats, including videos/screencasts,
including things like "a video tutorial on my documentation best
practices".
* [x] References:
* [x] [Diátaxis](https://diataxis.fr/): The Grand Unified Theory of Documentation.
* [x] [How to pick up a project with an audit](https://bluesock.org/~willkg/blog/dev/auditing_projects.html)
[Hackweek's issue tracker]: https://gitlab.torproject.org/tpo/community/Hackweek/-/issues
[issue template]: tpo/community/hackweek#10Hackweek 2023Gabagaba@torproject.orgGabagaba@torproject.org2023-08-23https://gitlab.torproject.org/tpo/community/hackweek/-/issues/10Issue template for Hackweek proposals2023-11-30T16:17:39ZSilvio RhattoIssue template for Hackweek proposalsCreate an issue template for Hackweek proposals, ref. [ORGANIZE-PRE-HACKWEEK](https://gitlab.torproject.org/tpo/community/hackweek/-/blob/main/ORGANIZE-PRE-HACKWEEK.md).Create an issue template for Hackweek proposals, ref. [ORGANIZE-PRE-HACKWEEK](https://gitlab.torproject.org/tpo/community/hackweek/-/blob/main/ORGANIZE-PRE-HACKWEEK.md).Hackweek 2023Gabagaba@torproject.orgGabagaba@torproject.orghttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/7Hackweek 2023: save the date message2023-11-30T16:17:39ZSilvio RhattoHackweek 2023: save the date messageSend a mail now so people have time to organize (save the date).Send a mail now so people have time to organize (save the date).Hackweek 2023tylertyler2023-07-05https://gitlab.torproject.org/tpo/community/hackweek/-/issues/5Update and fix links2023-11-30T16:17:38ZSilvio RhattoUpdate and fix linksUpdate and fix links in the [Hackweek](https://gitlab.torproject.org/tpo/community/hackweek) project to point to archive instead of pads.Update and fix links in the [Hackweek](https://gitlab.torproject.org/tpo/community/hackweek) project to point to archive instead of pads.Hackweek 2023anarcatanarcathttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/8Hackweek 2023: call for proposals message2023-11-30T16:17:38ZSilvio RhattoHackweek 2023: call for proposals messageSend the call for proposals email.Send the call for proposals email.Hackweek 2023Silvio RhattoSilvio Rhatto2023-08-30https://gitlab.torproject.org/tpo/community/hackweek/-/issues/3Hackweek 2023: create organization tickets2023-11-30T16:17:38ZSilvio RhattoHackweek 2023: create organization ticketsHackweek 2023Silvio RhattoSilvio Rhatto2023-06-30https://gitlab.torproject.org/tpo/community/hackweek/-/issues/34Dockerfile for local2023-11-30T16:17:38ZSilvio RhattoDockerfile for local# About the project
* Contact: <YOUR NAME HERE>
* Chat: #tor-<FILL IN> on `irc.oftc.net`
* Video room: https://tor.meet.coop/<FILL IN>
# Participants
- <YOUR NAME HERE>
- etc
# Summary
A description of the work that you want to d...# About the project
* Contact: <YOUR NAME HERE>
* Chat: #tor-<FILL IN> on `irc.oftc.net`
* Video room: https://tor.meet.coop/<FILL IN>
# Participants
- <YOUR NAME HERE>
- etc
# Summary
A description of the work that you want to do this week.
## Project A
## Project B
## etc
# Skills
What are the skills needed for the project? For example, somebody that
knows onion services, a designer, a translator, etc.
# LinksHackweek 2023https://gitlab.torproject.org/tpo/community/hackweek/-/issues/9Review existing process2023-11-30T16:17:38ZSilvio RhattoReview existing process* [x] Review the [existing process](https://gitlab.torproject.org/tpo/community/hackweek/-/blob/main/ORGANIZE-PRE-HACKWEEK.md) about how to organize a Hackweek.
* [x] Make a merge request, updating the process.* [x] Review the [existing process](https://gitlab.torproject.org/tpo/community/hackweek/-/blob/main/ORGANIZE-PRE-HACKWEEK.md) about how to organize a Hackweek.
* [x] Make a merge request, updating the process.Hackweek 2023Silvio RhattoSilvio Rhatto2023-10-05https://gitlab.torproject.org/tpo/community/hackweek/-/issues/13Onion MkDocs tryout2023-11-30T16:16:40ZSilvio RhattoOnion MkDocs tryout# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
- @gus
- etc
# Summary
This is a proposal to try [Onion MkDocs][] for documenting things at Tor.
[Onion...# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
- @gus
- etc
# Summary
This is a proposal to try [Onion MkDocs][] for documenting things at Tor.
[Onion MkDocs]: https://rhatto.pages.torproject.net/onion-mkdocs/
## Project A - Support
* [x] Provide support for people/teams that want to convert their wikis
to or have docs for their projects using [Onion MkDocs][].
* [x] Improve [Onion MkDocs][] stylesheet, plugins etc.
* [x] Improve [Onion MkDocs][] documentation.
## Project B - Convert
* [x] Convert some GitLab wikis to GitLab pages using Onion MkDocs:
* [x] Overview:
https://gitlab.torproject.org/tpo/tpa/team/-/issues/41119#note_2898441
* [x] Candidates for merge requests:
* [x] The Hackweek project itself:
https://gitlab.torproject.org/tpo/community/hackweek, with site now available
at https://tpo.pages.torproject.net/community/hackweek/
* [~] Onion Support Wiki:
https://gitlab.torproject.org/tpo/onion-services/onion-support/. To be done on Project C below.
* [x] Tor Policies repository:
https://gitlab.torproject.org/tpo/community/policies/-/issues/3
## Project C - Investigate
* [x] Investigate how Onion MkDocs could be a [TPA-RFC-38 wiki replacement (#40909) · TPA / TPA team](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40909) ([tpa rfc 38 new wiki service](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service)):
* [x] One approach would be to create a script that import content from some existing GitLab wikis into a single Onion MkDocs instance, to see how it would like to have a convergent "documentation integration" place. How it could be structured? Could it be easily searchable? What would be the best practices for this?
# Skills
Some knowledge in the following technologies may be needed in order to participate:
* Git/GitLab.
* Markdown.
* Basic scripting (Python, shell).
# LinksHackweek 2023Silvio RhattoSilvio Rhatto2023-11-09