The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2021-07-15T17:32:56Zhttps://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/40023Go through process of distributing private bridges2021-07-15T17:32:56ZPhilipp Winterphw@torproject.orgGo through process of distributing private bridgesOver at legacy/trac#31872, we created a process for distributing private bridges to NGOs:
https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam/NGOBridgeSupport
It's now time to go through this process with a non-tr...Over at legacy/trac#31872, we created a process for distributing private bridges to NGOs:
https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam/NGOBridgeSupport
It's now time to go through this process with a non-trivial number of censored users. Once we did, we need to document our experience and iteratively improve the process.Sponsor 30 - Objective 2.3GusGushttps://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/31Document how rdsys tests bridges2021-01-08T19:32:22ZPhilipp Winterphw@torproject.orgDocument how rdsys tests bridgesLet's work on a new piece of documentation that details how rdsys tests bridges. In particular, the documentation should talk about the interaction between rdsys and bridgestrap.Let's work on a new piece of documentation that details how rdsys tests bridges. In particular, the documentation should talk about the interaction between rdsys and bridgestrap.Sponsor 30 - Objective 2.3Philipp Winterphw@torproject.orgPhilipp Winterphw@torproject.orghttps://gitlab.torproject.org/tpo/onion-services/onion-support/-/issues/100Write an Onion Service survival guide2022-08-31T21:49:04ZSilvio RhattoWrite an Onion Service survival guideNeed to start working on a survival guide for S123, something like [the one from the Anti-Censorship Team](https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Guides/BridgeDB-Survival-Guide). Topics to cover:
* [x] D...Need to start working on a survival guide for S123, something like [the one from the Anti-Censorship Team](https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Guides/BridgeDB-Survival-Guide). Topics to cover:
* [x] Diagnosing an error given by Onionprobe monitoring (and how to read Onionprobe reports).
* [x] Troubleshooting EOTK.
* [x] Other useful guidance.
This guide should be available at the Onion Support wiki and also be sent upstream via merge requests (like for EOTK-specific instructions).Sponsor 123: Tor Secure Access Package for USAGM [First Phase]Silvio RhattoSilvio Rhatto2022-08-31https://gitlab.torproject.org/tpo/onion-services/onion-support/-/issues/99General policy on how the Onion Support team should respond to Onionprobe alerts2022-09-27T09:49:18ZSilvio RhattoGeneral policy on how the Onion Support team should respond to Onionprobe alertsWrite a small quick policy in what to do when an incident happen and are detected/notified by Onionprobe, including:
* Inform the interested parties (like Sponsors and/or users) of the issue, if needed.
* Check agreement when/where admi...Write a small quick policy in what to do when an incident happen and are detected/notified by Onionprobe, including:
* Inform the interested parties (like Sponsors and/or users) of the issue, if needed.
* Check agreement when/where admins allow to be notified.
* Then check if admins online (or on shift) can work on it (depends on agreed channels and current time):
* Ping on IRC.
* Ping on email.
* Ping on Signal.
* Ping on X.
This policy should be available at the Onion Support wiki.Sponsor 123: Tor Secure Access Package for USAGM [First Phase]Silvio RhattoSilvio Rhatto2022-08-31https://gitlab.torproject.org/tpo/onion-services/onion-support/-/issues/64Organize documentation about Onion Services UX improvements2022-11-02T17:51:03ZSilvio RhattoOrganize documentation about Onion Services UX improvements* [x] Compile existing proposals related to Onion Services usability.
* [x] Merge wiki pages/discussions in a single, canonical place.
* [x] Organize and summarize.
* [x] Discuss how proposals can be compared.
* [x] Discuss how proposals...* [x] Compile existing proposals related to Onion Services usability.
* [x] Merge wiki pages/discussions in a single, canonical place.
* [x] Organize and summarize.
* [x] Discuss how proposals can be compared.
* [x] Discuss how proposals can be combined in incremental roadmaps.Sponsor 123: Tor Secure Access Package for USAGM [First Phase]Silvio RhattoSilvio Rhatto2022-10-31https://gitlab.torproject.org/tpo/community/support/-/issues/40096Prepare documentation for the Tor Browser 12 release2023-01-12T21:22:53Zchampionquizzerchampionquizzer@torproject.orgPrepare documentation for the Tor Browser 12 releaseAnother major Tor Browser stable release is scheduled for next month. We should review all the external support documentation (tb-manual, support.tpo) and our templates on RT and cdr.link if anything needs to changed and/or added.
(if n...Another major Tor Browser stable release is scheduled for next month. We should review all the external support documentation (tb-manual, support.tpo) and our templates on RT and cdr.link if anything needs to changed and/or added.
(if necessary I will file separate tickets for the manual and support portal but this is going to be the tracking ticket.)
/cc @ninaSponsor 9 - Phase 6 - Usability and Community Intervention on Support for Democracy and Human Rightschampionquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40081Update documentation for the translator community2023-01-11T16:09:19ZGabagaba@torproject.orgUpdate documentation for the translator communityOnce migration to Weblate is complete, update the documentation for translators.Once migration to Weblate is complete, update the documentation for translators.Sponsor 9 - Phase 6 - Usability and Community Intervention on Support for Democracy and Human Rightsemmapeelemmapeelhttps://gitlab.torproject.org/tpo/community/training/-/issues/21Update Tor Browser screenshots on Tor training materials2022-10-26T20:37:09ZGusUpdate Tor Browser screenshots on Tor training materialsThe UX Team did significant changes on Tor Browser 11 UI and we will need to update our training materials.The UX Team did significant changes on Tor Browser 11 UI and we will need to update our training materials.Sponsor 9 - Phase 6 - Usability and Community Intervention on Support for Democracy and Human RightsGusGushttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40035Use gitlabCI to tell when a translation update needs to be done.2023-05-16T15:11:13ZemmapeelUse gitlabCI to tell when a translation update needs to be done.The script at https://gitlab.torproject.org/tpo/community/l10n/-/blob/main/bin/check_po_status.py can be integrated on the gitlabCI of lektor-based websites with translation support (tpo, support.tpo, gettor.tpo, tb-manual.tpo, community...The script at https://gitlab.torproject.org/tpo/community/l10n/-/blob/main/bin/check_po_status.py can be integrated on the gitlabCI of lektor-based websites with translation support (tpo, support.tpo, gettor.tpo, tb-manual.tpo, community.tpo) and will let us know when there are updates needed in transifex.
This is important for websites with lots of small updates: we can review changes in batches and send them to translators.
This check is only informative, and should not trigger a build fail.
The information can be looked at on the job log.
Websites that should have the check:
- [x] Support https://gitlab.torproject.org/tpo/web/support/-/pipelines
- [x] Manual https://gitlab.torproject.org/tpo/web/manual/pipelines
- [x] TPO https://gitlab.torproject.org/tpo/web/tpo/pipelines
- [x] Community https://gitlab.torproject.org/tpo/web/community/-/pipelines
- [x] DocumentationSponsor 9 - Phase 6 - Usability and Community Intervention on Support for Democracy and Human Rightsemmapeelemmapeelhttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40094Localize materials into Arabic, Chinese, Farsi & Swahili2023-09-06T15:45:21ZGabagaba@torproject.orgLocalize materials into Arabic, Chinese, Farsi & SwahiliIn the context of [sponsor 134](https://gitlab.torproject.org/groups/tpo/-/milestones/45#tab-issues) localize the following materials:
- [ ] [the Tor Project’s main website](https://hosted.weblate.org/projects/tor/tpo-web/) (torproject...In the context of [sponsor 134](https://gitlab.torproject.org/groups/tpo/-/milestones/45#tab-issues) localize the following materials:
- [ ] [the Tor Project’s main website](https://hosted.weblate.org/projects/tor/tpo-web/) (torproject.org)
- [x] Arabic: <img src="https://hosted.weblate.org/widgets/tor/ar/tpo-web/svg-badge.svg" alt="Translation status" />
- [x] Chinese: <img src="https://hosted.weblate.org/widgets/tor/zh_Hans/tpo-web/svg-badge.svg" alt="Translation status" />
- [ ] Persian: <img src="https://hosted.weblate.org/widgets/tor/fa/tpo-web/svg-badge.svg" alt="Translation status" />
- [x] Swahili: <img src="https://hosted.weblate.org/widgets/tor/sw/tpo-web/svg-badge.svg" alt="Translation status" />
- [x] censorship circumvention portals (gettor and bridges.torproject.org) - bridges is not available for translation yet
- [x] Arabic: <img src="https://hosted.weblate.org/widgets/tor/ar/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] Chinese: <img src="https://hosted.weblate.org/widgets/tor/zh_Hans/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] Persian: <img src="https://hosted.weblate.org/widgets/tor/fa/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] Swahili: <img src="https://hosted.weblate.org/widgets/tor/sw/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] the [Tor Browser manual](https://hosted.weblate.org/projects/tor/tor-browser-user-manual/)
- [x] Arabic: <img src="https://hosted.weblate.org/widgets/tor/ar/tor-browser-user-manual/svg-badge.svg" alt="Translation status" />
- [x] Chinese: <img src="https://hosted.weblate.org/widgets/tor/zh_Hans/tor-browser-user-manual/svg-badge.svg" alt="Translation status" />
- [x] Persian: <img src="https://hosted.weblate.org/widgets/tor/fa/tor-browser-user-manual/svg-badge.svg" alt="Translation status" />
- [x] Swahili: <img src="https://hosted.weblate.org/widgets/tor/sw/tor-browser-user-manual/svg-badge.svg" alt="Translation status" />
- [x] our [support portal](https://hosted.weblate.org/projects/tor/support-portal/)
- [x] Arabic: <img src="https://hosted.weblate.org/widgets/tor/ar/support-portal/svg-badge.svg" alt="Translation status" />
- [x] Chinese: <img src="https://hosted.weblate.org/widgets/tor/zh_Hans/support-portal/svg-badge.svg" alt="Translation status" />
- [x] Persian: <img src="https://hosted.weblate.org/widgets/tor/fa/support-portal/svg-badge.svg" alt="Translation status" />
- [x] Swahili: <img src="https://hosted.weblate.org/widgets/tor/sw/support-portal/svg-badge.svg" alt="Translation status" />
_Farsi translations will be done by Localization Lab, paid by Tor._
_Chinese, Arabic and Swahili will be done by Localization Lab, paid by IRI._Sponsor 134: Localizing Tor tools and documentation into Arabic, Chinese, and Swahiliemmapeelemmapeel2023-08-11https://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/31Tweets for the comms team2023-11-30T16:16:40ZemmapeelTweets for the comms team# About the project
* Contact: emmapeel
* Chat: #tor-project on `irc.oftc.net`
* Video room: https://tor.meet.coop/<FILL IN>
# Participants
- emmapeel
- pavel
# Summary
Last year we started a bank of content to tweet, with a cale...# About the project
* Contact: emmapeel
* Chat: #tor-project on `irc.oftc.net`
* Video room: https://tor.meet.coop/<FILL IN>
# Participants
- emmapeel
- pavel
# Summary
Last year we started a bank of content to tweet, with a calendar as well for important dates. This was to be put for translation, and used in our social media.
This year we did a test in weblate with a simpler format ( Here you can see the format for the Spanish translation: https://gitlab.torproject.org/tpo/translation/-/blob/social-content/es.csv?ref_type=heads ) , and we want to review last year's strings and add them to this new format component in weblate. This format is easier to use for the comms team and does not use as much resources as the previous setup with lektor and gitlabCI etc.
Last years repo: https://gitlab.torproject.org/tpo/web/social-bank/
In weblate: https://hosted.weblate.org/projects/tor/social-copy/#translations
# Skills
- We need tweets to use and translate, please add your suggestions to this ticket.
# Links
Last years repo: https://gitlab.torproject.org/tpo/web/social-bank/
In weblate: https://hosted.weblate.org/projects/tor/social-copy/#translations
New repo in gitlab: https://gitlab.torproject.org/tpo/translation/-/tree/social-content?ref_type=headsHackweek 2023emmapeelemmapeelhttps://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/community/hackweek/-/issues/29Document how to verify reproducibility of build of a mullvad/tor browser release2023-11-30T16:16:39ZboklmDocument how to verify reproducibility of build of a mullvad/tor browser release# About the project
* Contact: @boklm
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: no
# Participants
- @boklm
# Summary
I think many users don't know that our builds are reproducible, or how they can rebuild to verify...# About the project
* Contact: @boklm
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: no
# Participants
- @boklm
# Summary
I think many users don't know that our builds are reproducible, or how they can rebuild to verify that they get a matching build.
We could generate a `reproducible-build.txt` file in the release directory containing the following informations:
* which git repository to clone
* which commit to checkout
* which command to use to start the build
* which sha256sums to expect after the build finished
* how to remove embedded signatures from exe and mar files we publish to check that they match the unsigned build
# Skills
Need to know how to build Tor Browser.
# Links
* tpo/applications/tor-browser-build#40997Hackweek 2023boklmboklmhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/28Public documentation about how we manage projects at Tor2023-11-30T16:16:39ZGabagaba@torproject.orgPublic documentation about how we manage projects at Tor# About the project
* Contact: Gaba
* Chat: #tor-project 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-project 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
We have some [outdated documentation](https://gitlab.torproject.org/tpo/team/-/wikis/process/How-we-do-project-management-at-The-Tor-Project) on how we do project management at Tor. We also have templates and checklists in Nextcloud about different parts of a project's lifetime. I would like to update and expand them to be more clear and all public.
# Skills
Experience working in a sponsored project a TPO.Hackweek 2023Gabagaba@torproject.orgGabagaba@torproject.org2023-11-09https://gitlab.torproject.org/tpo/community/hackweek/-/issues/27TPA issue templates2023-11-30T16:16:39ZanarcatTPA issue templates# About the project
* Contact: @anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
# Summary
An ancient ticket in the TPA issue tracker has been found, and i...# About the project
* Contact: @anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
# Summary
An ancient ticket in the TPA issue tracker has been found, and it is full of precious metals, behold https://gitlab.torproject.org/tpo/tpa/team/-/issues/29398. The idea is that many (MANY) tickets issued in TPA often require the same basic data. Want a server? How big? who's team? Your PGP key expired? Please ship the key, etc. We waste an inordinate amount of time collecting that information when people open new issues.
The task here is to setup those templates in the TPA issue tracker. The twist is that right now the TPA project doesn't have any code at all: it's a "wiki only" GitLab project, and the code is instead in the tpo/tpa/wiki-replica project, mirrored into the tpo/tpa/team wiki, which shows up as the frontpage for the project. We need to find a way to do this transition cleanly, probably by moving wiki-replica directly into tpo/tpa/team (in which case we lose the homepage) or some other sheninagan.
# Skills
Some experience with GitLab is important. Probably relevant only to TPA people, but other contributors are of course welcome!
# Links
* https://gitlab.torproject.org/tpo/tpa/team/-/issues/29398
* https://gitlab.torproject.org/tpo/tpa/wiki-replica/
* https://gitlab.torproject.org/tpo/tpa/team/Hackweek 2023anarcatanarcathttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/26wiki replacement considerations2023-11-30T16:16:40Zanarcatwiki replacement considerations# About the project
* Contact: anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
- @shelikhoo
# Summary
[TPA-RFC-38: Wiki replacement](https://gitlab.torproj...# About the project
* Contact: anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
- @shelikhoo
# Summary
[TPA-RFC-38: Wiki replacement](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service) is a draft from TPA aiming at reviewing whether or not to replace the current GitLab wiki(s) by something else. It's mostly stalled, so let's see if we can move it forward a nudge.
Let's review the requirements to see if they cover what we need and what we want to accomplish. I particularly want to discuss which content we intend to throw "in the wiki" and whether a wiki is the appropriate tool for this. I particularly do *not* feel like it's a good tool for technical team to document their software projects, where alternatives like mdbook, sphinx or mkdocs seem better suited (see the recent torspec change for example).
It's unclear how this should be organized. In Costa Rica we've had an informal discussion about this which was useful, maybe having a BBB call or two to shake things up could move this ahead?
# Skills
Everyone from the community is welcome to join the discussion.
# Links
* https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service
* https://gitlab.torproject.org/tpo/tpa/team/-/issues/40909Hackweek 2023anarcatanarcathttps://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/24Public documentation about project design and grant writing process2024-01-11T17:32:09Zal smithPublic documentation about project design and grant writing process# About the project
* Contact: @smith
* Chat: #tor-internal on `irc.oftc.net`
* Video room: tbd
# Participants
- @smith
- etc
# Summary
- Write a guide on the process of project design and grant proposal writing
- Publish that ...# About the project
* Contact: @smith
* Chat: #tor-internal on `irc.oftc.net`
* Video room: tbd
# Participants
- @smith
- etc
# Summary
- Write a guide on the process of project design and grant proposal writing
- Publish that guide
- Create a template spreadsheet with guidelines on how to do estimations (@gaba, any interest in helping?)
We created an [overview of the grants process in Costa Rica and presented it in an in-person session](https://gitlab.torproject.org/tpo/team/-/wikis/Meetings/2023/2023-Tor-Meeting-Costa-Rica-Wiki/overview-of-how-projects-get-funded). We can use this to create something that's easier to read, more well-resourced, and easier to find.
# Skills
- Familiarity with the project design and grant writing process, either from a team participant side (e.g., someone from the network team who has been involved grant writing before) or from the design and writing side (e.g., someone form the money machine team).
# LinksHackweek 2023al smithal smithhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/23Fix missing documentation in network-health land2023-11-30T16:16:40ZGeorg KoppenFix missing documentation in network-health land# About the project
* Contact: @gk
* Chat: #tor-dev> on `irc.oftc.net`
* Video room: non yet
# Participants
- @gk
- @juga
- etc
# Summary
Fix missing documentation in network-health land
## Project A
We'll go over the open ti...# About the project
* Contact: @gk
* Chat: #tor-dev> on `irc.oftc.net`
* Video room: non yet
# Participants
- @gk
- @juga
- etc
# Summary
Fix missing documentation in network-health land
## Project A
We'll go over the open tickets with the `Documentation` label in network health land try to prioritize them and then fix as many of them as possible (starting with the most important ones). Alternatively, it's fine if folks just pick up any of those tickets and fix them. :smile:
# Skills
No special skillz
https://gitlab.torproject.org/tpo/network-health/team/-/issues/201 might be related to https://gitlab.torproject.org/tpo/community/hackweek/-/issues/19
https://gitlab.torproject.org/tpo/network-health/bandwidth-authorities/-/issues/2 is related to other security guidelines
# Links
https://gitlab.torproject.org/groups/tpo/network-health/-/issues/?sort=created_date&state=opened&label_name%5B%5D=Documentation&first_page_size=20
https://gitlab.torproject.org/groups/tpo/network-health/-/issues/?sort=created_date&state=opened&label_name%5B%5D=Docshackathon&assignee_username%5B%5D=juga&first_page_size=100
Update: added juga, tentative issues and other teams' related issuesHackweek 2023Georg KoppenGeorg Koppen