HylaFAX Difference between revisions of "Get Involved"
m (→Join Development Team: Fix mailing list link) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Help make HylaFAX the best it can be by contributing back to the | + | Help make HylaFAX the best it can be by contributing back to the project. No matter your level of technical experience there is a way you can help. Please consider contributing back by participating in one (or all) of the following efforts: |
==Mailing Lists== | ==Mailing Lists== | ||
By subscribing to and participating in the HylaFAX-users [[Mailing Lists|mailing list]] you can help foster a lively user community. Many users of HylaFAX found the answers to their problems on the list and its archives; please consider passing some of your knowledge back to the community. | By subscribing to and participating in the HylaFAX-users [[Mailing Lists|mailing list]] you can help foster a lively user community. Many users of HylaFAX found the answers to their problems on the list and its archives; please consider passing some of your knowledge back to the community. | ||
| + | |||
| + | ==Documentation Project== | ||
| + | With the launch of the new hylafax.org website, we are attempting to consolidate and update the HylaFAX documentation. The documentation is now in wiki format so that any HylaFAX user can edit or add to it. Visit the [[Documentation]] section of hylafax.org to begin helping with this important task. | ||
==Reporting Bugs== | ==Reporting Bugs== | ||
| − | Faithful to our open-source bias, | + | Faithful to our open-source bias, HylaFAX bugs are tracked using [http://www.mozilla.org/projects/bugzilla/ Bugzilla], a product of the [http://www.mozilla.org/ Mozilla Project]. Please do your best to make sure you've really found a bug, and then file it on the HylaFAX Bugzilla, located at [http://bugs.hylafax.org/ http://bugs.hylafax.org/]. To confirm a bug one should first check the mailing list archives for other reports of this issue (and possible resolution) and then post to the developers mailing list (described above). Security-related bugs should be reported to security@hylafax.org in order to avoid exploitation of the problem before it can be publicly resolved. |
| − | |||
==Join Development Team== | ==Join Development Team== | ||
| − | The HylaFAX developer community is always looking for new recruits. Don't be scared, you're welcome to lurk until you feel comfortable! If you're looking to become involved on any level, you should definitely subscribe to to the hylafax developers [[Mailing | + | The HylaFAX developer community is always looking for new recruits. Don't be scared, you're welcome to lurk until you feel comfortable! If you're looking to become involved on any level, you should definitely subscribe to to the hylafax developers [[Mailing Lists|mailing list]]. |
| − | |||
| − | |||
| − | |||
Latest revision as of 18:57, 6 March 2009
Help make HylaFAX the best it can be by contributing back to the project. No matter your level of technical experience there is a way you can help. Please consider contributing back by participating in one (or all) of the following efforts:
Mailing Lists
By subscribing to and participating in the HylaFAX-users mailing list you can help foster a lively user community. Many users of HylaFAX found the answers to their problems on the list and its archives; please consider passing some of your knowledge back to the community.
Documentation Project
With the launch of the new hylafax.org website, we are attempting to consolidate and update the HylaFAX documentation. The documentation is now in wiki format so that any HylaFAX user can edit or add to it. Visit the Documentation section of hylafax.org to begin helping with this important task.
Reporting Bugs
Faithful to our open-source bias, HylaFAX bugs are tracked using Bugzilla, a product of the Mozilla Project. Please do your best to make sure you've really found a bug, and then file it on the HylaFAX Bugzilla, located at http://bugs.hylafax.org/. To confirm a bug one should first check the mailing list archives for other reports of this issue (and possible resolution) and then post to the developers mailing list (described above). Security-related bugs should be reported to security@hylafax.org in order to avoid exploitation of the problem before it can be publicly resolved.
Join Development Team
The HylaFAX developer community is always looking for new recruits. Don't be scared, you're welcome to lurk until you feel comfortable! If you're looking to become involved on any level, you should definitely subscribe to to the hylafax developers mailing list.
