tor-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
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).