Difference between revisions of "Reporting Bugs"
m |
m (don't comment on what is or is not Gentoo policy) |
||
| Line 19: | Line 19: | ||
==== Upstream Bug Reporting ==== | ==== Upstream Bug Reporting ==== | ||
| − | Sometimes, it may be necessary to report bugs upstream, particularly to [http://bugs.gentoo.org Gentoo's Bugzilla]. You should be aware that Gentoo Linux has a | + | Sometimes, it may be necessary to report bugs upstream, particularly to [http://bugs.gentoo.org Gentoo's Bugzilla]. You should be aware that Gentoo Linux has a habit of marking Funtoo-related bugs as INVALID, even if they are clearly related to ebuilds that have originated from Gentoo Linux. While we find this policy to be questionable and unfortunate, it does mean that reporting bugs to [http://bugs.gentoo.org Gentoo's Bugzilla] must be handled with great care. Please follow these steps: |
* Try to get your bug resolved through the Funtoo Linux community resources and funtoo-dev mailing list first. | * Try to get your bug resolved through the Funtoo Linux community resources and funtoo-dev mailing list first. | ||
* If you feel it is necessary to file a bug with Gentoo, please inform the Funtoo core team that you are doing so, indicate that you are using Funtoo Linux in the bug report, also mention the troubleshooting steps you have performed so far (on Funtoo infrastructure,) and cc <tt>staff@funtoo.org</tt> on your bug report so that I can personally track the status of these bug reports and get involved as necessary. | * If you feel it is necessary to file a bug with Gentoo, please inform the Funtoo core team that you are doing so, indicate that you are using Funtoo Linux in the bug report, also mention the troubleshooting steps you have performed so far (on Funtoo infrastructure,) and cc <tt>staff@funtoo.org</tt> on your bug report so that I can personally track the status of these bug reports and get involved as necessary. | ||
Revision as of 22:00, 21 January 2011
The Funtoo community's goal is to provide a seamless and problem-free computing experience, and we take all bugs seriously. Please use the following resources for reporting bugs, technical support, and troubleshooting assistance:
Contents |
IRC
Our IRC channels are available for informal, real-time technnical support and troubleshooting. Please use Funtoo channels rather than Gentoo channels for Funtoo Linux support.
Support Forums
The following Web-based discussion resources are specifically created for community-based support and troubleshooting, and are monitored by the Funtoo Linux core team.
- Funtoo Linux Install Central - Web-based help with installation
- Tech Support/Troubleshooting - Web-based general troubleshooting assistance
- Hardware Compatibility - Web-based assistance with hardware compatibility issues
funtoo-dev Mailing List
The funtoo-dev mailing list should be used for reporting vetted bugs or issues that have not been resolved on IRC or the support Forums. We request that you do not use the mailing list for general troubleshooting or technical support, but try to use IRC or the Support Forums first, and then escalate to the funtoo-dev mailing list if your problem is unresolved within a reasonable time frame.
Upstream Bug Reporting
Sometimes, it may be necessary to report bugs upstream, particularly to Gentoo's Bugzilla. You should be aware that Gentoo Linux has a habit of marking Funtoo-related bugs as INVALID, even if they are clearly related to ebuilds that have originated from Gentoo Linux. While we find this policy to be questionable and unfortunate, it does mean that reporting bugs to Gentoo's Bugzilla must be handled with great care. Please follow these steps:
- Try to get your bug resolved through the Funtoo Linux community resources and funtoo-dev mailing list first.
- If you feel it is necessary to file a bug with Gentoo, please inform the Funtoo core team that you are doing so, indicate that you are using Funtoo Linux in the bug report, also mention the troubleshooting steps you have performed so far (on Funtoo infrastructure,) and cc staff@funtoo.org on your bug report so that I can personally track the status of these bug reports and get involved as necessary.
