简体中文
EnglishWhere to Report Bugs or Ask Questions About Freeplane
Updated
Freeplane's documentation site points to three separate channels depending on what you need: use the Issues tracker to report a bug, use Discussions for questions, ideas, or general thoughts, and edit the page on GitHub if you spot a documentation mistake. Contributors are explicitly welcomed. The site does not publish direct URLs for the Issues tracker or Discussions in the text captured here, so you'll need to reach them from the documentation site's own links.
Which channel to use
| What you have | Where it goes | Why |
|---|---|---|
| A reproducible bug or defect | Issues tracker | Bug reports are tracked and can be referenced later |
| A question about how something works | Discussions | Open-ended questions and answers, not defect tracking |
| An idea or feature thought | Discussions | The site groups "questions, ideas, or thoughts" together |
| A typo or error in the documentation | GitHub edit link | Documentation lives in a repo and is edited directly |
Reporting a bug
The documentation states plainly: "If you would like to report a bug, you can go report it over at Issues." That is the only bug channel named on the page.
Before you file, make the report usable:
- Confirm you are on the latest version — the site directs downloads to Sourceforge and notes a change log is available, so check whether the behavior was already changed.
- Note your environment. Freeplane is written in Java using OSGi and Java Swing and runs on any operating system with a current Java version, so the Java version and OS are relevant context.
- State whether you run it locally or portably from removable storage such as a USB drive — the site lists both as supported modes, and the distinction can matter for file-path and permission issues.
- Describe the steps, what you expected, and what happened instead.
Asking questions or sharing ideas
The site says: "Hop on to our Discussions if you have any questions, ideas, or thoughts you'd like to share." Discussions is the catch-all for anything that isn't a defect — how-to questions, workflow ideas, and feedback on the tool.
Because Discussions is also where ideas land, search it before posting a feature request; someone may have raised the same thought already.
Fixing documentation mistakes
Each documentation page carries an "Edit this page on GitHub" link. If the problem is with the text rather than the software, that link takes you straight to the source file, where you can propose a correction. This is the fastest path for typos, outdated wording, or broken explanations.
Contributing beyond reports
The page closes with "Contributors are very much welcome, of course!" If you want to go past filing issues, the same GitHub presence used for documentation edits is the natural starting point. Note that the site credits its tooling to third parties — YourKit for Java profiling and Weblate for translation management — which tells you translation work is handled through a separate web-based system rather than the main repo.
What the page does not give you
The captured documentation text names the Issues tracker and Discussions but does not include their direct URLs, and it does not describe response times, triage process, or whether an account is required to post. Treat the documentation site itself as the entry point and follow its links rather than guessing at addresses.