The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-11-30T16:16:39Zhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/18Working on the content for the developer portal2023-11-30T16:16:39ZGabagaba@torproject.orgWorking on the content for the developer portal# About the project
* Contact: @gaba
* Chat: #tor-dev on `irc.oftc.net`
* Video room: https://tor.meet.coop/gab-tph-u9q-eo0
* Meet Monday, Tuesday, Wednesday, Thursday from 12UTC to 20UTC
# Participants
- @gaba
- you?
# Summary
...# About the project
* Contact: @gaba
* Chat: #tor-dev on `irc.oftc.net`
* Video room: https://tor.meet.coop/gab-tph-u9q-eo0
* Meet Monday, Tuesday, Wednesday, Thursday from 12UTC to 20UTC
# Participants
- @gaba
- you?
# Summary
The [developer portal](https://gitlab.torproject.org/tpo/web/dev/) has been on the back waiting for some time to get completed. At the beginning of this year Ura.Design worked on a [site/design](https://gitlab.torproject.org/tpo/web/dev/-/issues/6) for it. This is a project to get the content into the site and reviewing the information architecture.
## Project A : Get content into the portal
The content that we are planning to have in this portal is all over the place in repositories and wikis. With this project I will move the content to the dev portal, review the information architecture and organize the work that needs to happen next.
# Skills
- Gitlab
- Writing documentation
- MarkdownHackweek 2023Gabagaba@torproject.orgGabagaba@torproject.org2023-11-09https://gitlab.torproject.org/tpo/community/hackweek/-/issues/17Clean up and improve the user support FAQ text2023-11-30T16:16:39ZRoger DingledineClean up and improve the user support FAQ text# About the project
* Contact: Roger Dingledine
* Chat: #tor-www on `irc.oftc.net` / [#tor-www](https://matrix.to/#/#tor-www:matrix.org) on matrix
* Video room: https://tor.meet.coop/pav-g4m-iys-h7n (kick off meeting on Monday, 06 No...# About the project
* Contact: Roger Dingledine
* Chat: #tor-www on `irc.oftc.net` / [#tor-www](https://matrix.to/#/#tor-www:matrix.org) on matrix
* Video room: https://tor.meet.coop/pav-g4m-iys-h7n (kick off meeting on Monday, 06 November at 14 UTC)
* Pad: https://pad.riseup.net/p/improve-support-faqs-hackweek-qwjebqwjqedwqebdj
# Participants
- Roger Dingledine
- ebanam
- @gus
- you?
# Summary
Tor has a huge variety of FAQ entries on support.torproject.org, copied over from the original FAQ, the abuse FAQ, etc. When we made support.tpo, we only took some of the entries. Then we updated those over the years, but actually we have mostly left them alone -- I imagine it's hard for most individuals to decide to change one of these support entries, because they don't know who needs to buy in, or they worry that somebody else thinks it's perfect the way it is.
Let's look again at the big picture of which entries are useful, which ones are right, and whether there are any missing. The outcome will be a better support site.
# Skills
We will need people who know how to technical write, people who know what problems/questions/concerns Tor users encounter, people who know how Tor and Tor Browser work, people who have an interest in Tor comms and framing, and people who know basic html/markup. These don't all have to be the same people! :)
# LinksHackweek 2023Roger DingledineRoger Dingledinehttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/16Collaborative editing2023-11-30T16:16:40ZSilvio RhattoCollaborative editing# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @meskio
- @rhatto (I'm looking for someone to be the new maintainer/coordinator/asignee for this proposal, as I ma...# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @meskio
- @rhatto (I'm looking for someone to be the new maintainer/coordinator/asignee for this proposal, as I may participate only marginally on it)
- @micah
- @shelikhoo (Partially)
# Summary
This is about enhancing ways we deal with [Etherpads](https://etherpad.org/).
## Project A - Nextcloud collaborative editor
* [x] Try the Nextcloud collaborative editor as an attempt at reducing the number of external tools we have to deal with.
## Project B - Etherpad
* [x] Etherpad archival utility/GitLab bot (as ticket comments, merge requests etc). Use case: add pad links into the ticket description, and the bot will act regularly, submitting changes somewhere. Maybe this already exists? We may also try to expand this use case for other document sources/platforms.
* [ ] Investigate the possibility to run our own etherpad, and not use the pad cleanup that Riseup does, and then the pads can be integrated with Nextcloud.
## Project C - CryptPad
* [x] Etherpad may be winding down development, and we should re-consider [CryptPad](https://cryptpad.fr/), which has a number of document management utilities bundled with it.
## Project D - HedgeDoc
* [ ] Try [HedgeDoc](https://hedgedoc.org/), "an open-source, web-based, self-hosted, collaborative markdown editor".
# Skills
What are the skills needed for the project:
* Not sure yet! Maybe no specific skills needed.
* Etherpad autosaving may depend on the knowledge needed to create GitLab bots and other scripts.
# LinksHackweek 2023micahmicah@torproject.orgmicahmicah@torproject.org2023-11-09https://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/14Onion TeX Slim enhancements2023-11-30T16:16:39ZSilvio RhattoOnion TeX Slim enhancements# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
# Summary
This proposal is about making some enhancements to [Onion TeX Slim][].
[Onion TeX Slim]: http...# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
# Summary
This proposal is about making some enhancements to [Onion TeX Slim][].
[Onion TeX Slim]: https://gitlab.torproject.org/rhatto/onion-tex-slim
## Project A - Improving
* [~] Dockerfile for local builds. Moved to tpo/community/onion-tex-slim#5.
* [~] Test and improve the LaTeX templates. Moved to tpo/community/onion-tex-slim#6.
* [~] Add more functionality (graphics etc). Moved to tpo/community/onion-tex-slim#7.
* [~] Localization support, at least for the Markdown/Pandoc version. Moved to tpo/community/onion-tex-slim#2.
* [~] Make easier to add [Onion TeX Slim][] support in a `slides/` or `docs/slides` folder. Moved to tpo/community/onion-tex-slim#8.
## Project B - Trying
* [x] Use this project to build some presentations:
* [x] In the [Tor Community Training repository](https://gitlab.torproject.org/tpo/community/training/).
# Skills
Some knowledge in the following technologies may be needed in order to participate:
* Git/GitLab.
* Markdown.
* LaTeX.
* Basic scripting (Python, shell).
# LinksHackweek 2023Silvio RhattoSilvio Rhatto2023-11-09https://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-09https://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/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/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/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/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/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/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/3Hackweek 2023: create organization tickets2023-11-30T16:17:38ZSilvio RhattoHackweek 2023: create organization ticketsHackweek 2023Silvio RhattoSilvio Rhatto2023-06-30https://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/39Update mining documentation2024-01-31T18:27:20ZSilvio RhattoUpdate mining documentation# Tasks
* [x] Cleanup the [Tips when mining Onion Addresses][] page.
* [x] Update the [Tips when mining Onion Addresses][] page, including references to
* [x] [Onionmine](https://gitlab.torproject.org/tpo/onion-services/onionmine/).
...# Tasks
* [x] Cleanup the [Tips when mining Onion Addresses][] page.
* [x] Update the [Tips when mining Onion Addresses][] page, including references to
* [x] [Onionmine](https://gitlab.torproject.org/tpo/onion-services/onionmine/).
* [x] The [Vanity Addresses page](https://community.torproject.org/onion-services/advanced/vanity-addresses/).
[Tips when mining Onion Addresses]: https://tpo.pages.torproject.net/onion-services/onionspray/guides/mining/
# Time estimation
* Complexity: negligible (0.1 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Onionspray 1.6.0Silvio RhattoSilvio Rhatto2024-01-31https://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/34Minor documentation fixes2024-02-05T16:40:54ZSilvio RhattoMinor documentation fixes# Tasks
* [x] Do some minor documentation fixes.
# Time estimation
* Complexity: negligible (0.1 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)# Tasks
* [x] Do some minor documentation fixes.
# Time estimation
* Complexity: negligible (0.1 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Onionspray 1.6.0Silvio RhattoSilvio Rhatto2024-01-31https://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/19Fine tune the documentation2024-01-23T18:16:17ZSilvio RhattoFine tune the documentation# Tasks
* [x] Re-structure docs according to [Diatáxis](https://diataxis.fr/), or at least split some content between How-To Guides and Tutorials.
* [x] Do a more fine-grained edit in the docs, including:
* [x] [Survival Guide](https:...# Tasks
* [x] Re-structure docs according to [Diatáxis](https://diataxis.fr/), or at least split some content between How-To Guides and Tutorials.
* [x] Do a more fine-grained edit in the docs, including:
* [x] [Survival Guide](https://gitlab.torproject.org/tpo/onion-services/onion-support/-/wikis/Documentation/Survival-Guide) (EOTK portion).
* [x] Migration guide for those coming from EOTK, replacing the migration sketched in the ChangeLog (basically copying all `.conf`, `.tconf`, `secrets`; building and configuring; copying the certificates).
* [x] Improved introduction:
* [x] [Project description](https://gitlab.torproject.org/tpo/onion-services/eotk/-/issues/13#note_2986581).
* [x] What it does: adds Onion Service support for existing sites.
* [x] Overview how it works (rewriting proxy through .onion) (with a diagram). The proxy is mainly intended to replace regular domain names with their .onion counterparts, offering a seamless experience to users.
* [x] How it's usually installed: no need to changing existing setups, just provision the Onion Services infra in parallel of existing setups; can run anywhere, in a laptop, a single board computer, in servers; as standalone program, or as a container.
* [x] Use-cases.
* [x] On EOTK compatibility: the `eotk` script is kept as an alias to `onionspray`.
* [x] Replace `eotk` with `onionspray` in the CLI usage.
* [x] Installation:
* [x] Required knowledge (Onion Services and command line familiarity etc).
* [~] Using Tor and OpenResty upstream packages for your distro (when available) (moved to tpo/onion-services/onionspray#21).
* [x] Contact and reporting:
* [x] Contact info (tor-dev channel and mailing list?).
* [x] How to report bugs.
* [~] ChangeLog:
* [~] Update with everything (or just referring to) done in the [initial milestone](https://gitlab.torproject.org/tpo/onion-services/onionspray/-/milestones/1) (moved to tpo/onion-services/onionspray#28).
* [x] Setup the [Renovate Bot](https://gitlab.torproject.org/tpo/tpa/renovate-cron) to watch for changes in vendorized Git submodules.
* [x] Review the documentation.
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Onionspray 1.6.0Silvio RhattoSilvio Rhatto2024-01-31https://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/17Improve and cleanup the documentation2024-01-17T21:30:01ZSilvio RhattoImprove and cleanup the documentation# Tasks
* [x] Improve and cleanup the documentation.
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)# Tasks
* [x] Improve and cleanup the documentation.
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Onionspray 1.6.0Silvio RhattoSilvio Rhatto2024-01-31https://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/15Setup Onion MkDocs2024-01-17T16:35:02ZSilvio RhattoSetup Onion MkDocs# Tasks
* [x] Setup web documentation through [Onion MkDocs](https://gitlab.torproject.org/tpo/web/onion-mkdocs/).
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/...# Tasks
* [x] Setup web documentation through [Onion MkDocs](https://gitlab.torproject.org/tpo/web/onion-mkdocs/).
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Onionspray 1.6.0Silvio RhattoSilvio Rhatto2024-01-31