Difference between revisions of "Contact"
(→Mailing lists: http://gramps.1791082.n4.nabble.com/ old link did not work) |
(→Mailing lists: clarify need to join the mailing list) |
||
(6 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
{{languages|Contact}} | {{languages|Contact}} | ||
− | |||
− | |||
− | |||
− | |||
==Reporting bugs== | ==Reporting bugs== | ||
− | The recomended way to report a bug is to use the [http://bugs.gramps-project.org | + | The recomended way to report a bug is to use the [http://bugs.gramps-project.org Gramps Bug Tracker], see [[How to report bugs]]. This allows the Gramps Developers to follow a formal method of tracking and resolving your report. Due to the high volume of email that the primary developers receive, there is always a chance that an email may slip through the cracks. Using the bug tracker will make sure that your issue will be handled. |
− | Bug reports submitted, directly to the [http://lists.sourceforge.net/mailman/listinfo/gramps-bugs | + | Bug reports submitted, directly to the [http://lists.sourceforge.net/mailman/listinfo/gramps-bugs Gramps Bugs mailing list] are not recommended. |
==Requesting enhancements== | ==Requesting enhancements== | ||
Requesting an enhancement can be done either through the gramps-users or gramps-devel mailing lists, or by [http://bugs.gramps-project.org/ creating a feature item] on the bug tracker. We would prefer that serious requests get submitted to the bug tracker. You switch to '''Project: Feature Requests''' on the top right head corner, and select '''Report Issue'''. Again, this allows us to formally track the request. | Requesting an enhancement can be done either through the gramps-users or gramps-devel mailing lists, or by [http://bugs.gramps-project.org/ creating a feature item] on the bug tracker. We would prefer that serious requests get submitted to the bug tracker. You switch to '''Project: Feature Requests''' on the top right head corner, and select '''Report Issue'''. Again, this allows us to formally track the request. | ||
+ | |||
+ | ==Wiki, Website/Blog, Bug Tracker applications== | ||
+ | |||
+ | For problems relating to the Gramps site and the applications used to support Gramps, contact Nick Wallingford [mailto:[email protected]] or raise the issue on the developer list described below. | ||
==Mailing lists== | ==Mailing lists== | ||
− | There are several mailing lists on various topics related to | + | There are several mailing lists on various topics related to Gramps: |
− | |||
− | |||
− | *;gramps- | + | *;gramps-announce ([http://lists.sourceforge.net/lists/listinfo/gramps-announce unsubscribe/subscribe], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-announce archives]) : Announcements and general important news items. Very low traffic. |
− | *;gramps- | + | *;gramps-users ([http://lists.sourceforge.net/lists/listinfo/gramps-users unsubscribe/subscribe], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-users archives]): Discussions on using Gramps. Medium traffic. |
− | *;gramps- | + | *;gramps-bugs ([http://lists.sourceforge.net/lists/listinfo/gramps-bugs unsubscribe/subscribe], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-bugs archives]): Filing and tracking of bugs in the software. Low traffic |
− | *;gramps-devel ([http://lists.sourceforge.net/lists/listinfo/gramps-devel subscribe], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-devel archives]): For issues relating to software development. Medium traffic. | + | *;gramps-devel ([http://lists.sourceforge.net/lists/listinfo/gramps-devel unsubscribe/subscribe], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-devel archives]): For issues relating to software development. Medium traffic. |
− | If the Sourceforge site is too slow | + | If the Sourceforge site is too slow for your liking, use the copy of the mailing lists stored [http://gramps.1791082.n4.nabble.com/ on nabble.com]. However, if you want to use nabble to send messages (as opposed to just reading them) then you must have subscribed to the related sourceforge mailing list first. |
==IRC (Internet Relay Chat)== | ==IRC (Internet Relay Chat)== | ||
Please feel free to drop by on channel '''[irc://irc.freenode.net/#gramps #gramps]''' over at '''irc.freenode.net''' server. All users and developers are welcome! | Please feel free to drop by on channel '''[irc://irc.freenode.net/#gramps #gramps]''' over at '''irc.freenode.net''' server. All users and developers are welcome! | ||
− | You can use the [http://webchat.freenode.net/?channels=gramps&uio=d4 freenode Web IRC] to connect if you do not have an [https:// | + | You can use the [http://webchat.freenode.net/?channels=gramps&uio=d4 freenode Web IRC] to connect if you do not have an [https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients IRC client]. |
+ | |||
+ | Some IRC guides: | ||
+ | *[http://freenode.net/using_the_network.shtml Using the IRC Network] - freenode.net | ||
+ | *[http://www.irchelp.org/irchelp/irctutorial.html An IRC Tutorial] | ||
+ | *[http://www.irchelp.org/irchelp/ircprimer.html A Short IRC Primer] | ||
==Copyright infringements== | ==Copyright infringements== | ||
Please, mail the Developers mailing list ([http://lists.sourceforge.net/lists/listinfo/gramps-devel subscribe first]) with the wiki page containing the infringement, as well as the manner of infringement. | Please, mail the Developers mailing list ([http://lists.sourceforge.net/lists/listinfo/gramps-devel subscribe first]) with the wiki page containing the infringement, as well as the manner of infringement. | ||
+ | |||
+ | [[Category:Documentation]] | ||
+ | [[Category:Community/General]] |
Revision as of 18:21, 22 March 2016
Languages: |
English • čeština • Deutsch • español • français • עברית • italiano • Nederlands • polski • русский • svenska • Türkçe |
Contents
Reporting bugs
The recomended way to report a bug is to use the Gramps Bug Tracker, see How to report bugs. This allows the Gramps Developers to follow a formal method of tracking and resolving your report. Due to the high volume of email that the primary developers receive, there is always a chance that an email may slip through the cracks. Using the bug tracker will make sure that your issue will be handled.
Bug reports submitted, directly to the Gramps Bugs mailing list are not recommended.
Requesting enhancements
Requesting an enhancement can be done either through the gramps-users or gramps-devel mailing lists, or by creating a feature item on the bug tracker. We would prefer that serious requests get submitted to the bug tracker. You switch to Project: Feature Requests on the top right head corner, and select Report Issue. Again, this allows us to formally track the request.
Wiki, Website/Blog, Bug Tracker applications
For problems relating to the Gramps site and the applications used to support Gramps, contact Nick Wallingford [1] or raise the issue on the developer list described below.
Mailing lists
There are several mailing lists on various topics related to Gramps:
- gramps-announce (unsubscribe/subscribe, archives)
- Announcements and general important news items. Very low traffic.
- gramps-users (unsubscribe/subscribe, archives)
- Discussions on using Gramps. Medium traffic.
- gramps-bugs (unsubscribe/subscribe, archives)
- Filing and tracking of bugs in the software. Low traffic
- gramps-devel (unsubscribe/subscribe, archives)
- For issues relating to software development. Medium traffic.
If the Sourceforge site is too slow for your liking, use the copy of the mailing lists stored on nabble.com. However, if you want to use nabble to send messages (as opposed to just reading them) then you must have subscribed to the related sourceforge mailing list first.
IRC (Internet Relay Chat)
Please feel free to drop by on channel #gramps over at irc.freenode.net server. All users and developers are welcome!
You can use the freenode Web IRC to connect if you do not have an IRC client.
Some IRC guides:
- Using the IRC Network - freenode.net
- An IRC Tutorial
- A Short IRC Primer
Copyright infringements
Please, mail the Developers mailing list (subscribe first) with the wiki page containing the infringement, as well as the manner of infringement.