Easy path to source code

Open
#238 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Review the developer.thunderbird.net entry point, Thunderbird Help > About and Licensing, and Troubleshooting Information > about:buildconfig, along with the linked Reddit discussion. Determine which existing location should provide the source-code path and document the agreed route, including the relevant links and any needed wording changes.

Written by the indexing model from the issue text.

Description

https://www.reddit.com/r/Thunderbird/comments/1pny804/where_is_the_actual_source_code_it_seems_like_the/ makes the point, I think correctly, that it's not trivially easy to get to the source code from any obvious location.

Some possibilities could be:

  1. https://developer.thunderbird.net/ - but it first presents several preliminaries sections because it currently presumes the person is going to contribute code or documentation
  2. Thunderbird > Help > About
  3. Thunderbird > Help > About > Licensing - lacks any pointers to Thunderbird code in the text "All of the source code to this product is available under licenses which are both free and open source. A URL identifying the specific source code used to create this copy can be found on the build configuration page, and you can read instructions on how to download and build the code for yourself."
  4. Thunderbird Help > Troubleshooting Information > about:buildconfig > yields a link like https://hg-edge.mozilla.org/releases/comm-beta/rev/b1a35f8a7251dada824abd12b4de3b70e2064be1 where you have to know to click on "files".
Dominant language
No language data
Stars
114
Forks
86
Avg merge
2h 37m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from thunderbird/developer-docs

All issues in thunderbird/developer-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.