SUPPORT.adoc 6.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159
  1. = gpsd SUPPORT information
  2. :date: 9 February 2021
  3. :docinfodir: www
  4. :keywords: gps, gpsd, gnss
  5. :robots: index,follow
  6. :sectlinks:
  7. :toc: macro
  8. :type: article
  9. :webfonts!:
  10. include::www/inc-menu.adoc[]
  11. == GENERAL
  12. *gpsd* is developed and maintained by the open source community, and the
  13. project does not formally offer support. Many people are usually
  14. extremely helpful, particularly towards those people who have taken
  15. the time to try to understand things and appear likely to contribute
  16. to the community. This file explains how to ask for help.
  17. (For those used to interacting with and contributing to open source
  18. projects, note that this file is not attempting to say anything
  19. radical or unusual.)
  20. There is much documentation online at +
  21. {gpsdweb} +
  22. and that documentation should be consulted before asking for help.
  23. Details of *gpsd* support is described at +
  24. https://gpsd.io/faq.html#bug-reporting
  25. The following link is very useful to give a sense of how to ask
  26. questions: +
  27. http://www.catb.org/esr/faqs/smart-questions.html
  28. *gpsd* has not adopted the policy implicit in the following link, but it
  29. is an interesting discussion which may provide some insight into the
  30. response to requests for help: +
  31. https://berthub.eu/articles/posts/anonymous-help/
  32. You contact the *gpsd* project using IRC, one or our mailing lists, or
  33. use our issue tracker. To speed resolution of issues, a good start is to
  34. supply:
  35. * Your *gpsd* version
  36. * Are you building from our source, or using a package?
  37. * Your distribution name, version, and architecture.
  38. * Your GPS/GNSS receiver model.
  39. * How you are starting the gpsd daemon.
  40. == ISSUE TRACKER
  41. The *gpsd* source control website is at +
  42. https://gitlab.com/gpsd/gpsd/ +
  43. and contains an issue tracker.
  44. Issues may be created when you believe that something is wrong in the
  45. *gpsd* code, documentation, or website and can articulate why you
  46. believe that. This is not meant to be a particularly high bar, but
  47. asking questions in issues is not acceptable and "gpsd doesn't work"
  48. is not acceptable. Feature requests are sometimes acceptable,
  49. particularly when the feature is well thought out, appears
  50. implementable, is likely to be of broad interest, and the request is
  51. filed by someone with a history of participation in the community.
  52. Issues may be created for the most recent formal release of *gpsd*, or
  53. the current version of *gpsd*, the website or other project content.
  54. (Quality bug reports with specific references to problem code still
  55. present in the latest release are OK too.)
  56. Issues that are not valid issues (not a bug, or lack of a reasonable
  57. attempt to provide enough information) may be summarily closed.
  58. == USER MAILINGLIST
  59. The user mailinglist at +
  60. https://lists.gnu.org/mailman/listinfo/gpsd-users +
  61. is appropriate for questions about gpsd, after a reasonable attempt
  62. has been made to answer the question by reading the documentation.
  63. When posting to the user list, make sure to describe your question and
  64. situation well (see the links above). Please realize that you are
  65. asking for free help from strangers, rather than addressing your paid
  66. consultant.
  67. Generally, please update to at least the latest formal release before
  68. asking for help, particularly if you are trying to do anything that is
  69. not already known to work for everyone else. Almost no one on the
  70. mailinglist has shown an interest in addressing issues in old
  71. versions.
  72. == DEVELOPMENT MAILINGLIST
  73. The development mailinglist at +
  74. https://lists.gnu.org/mailman/listinfo/gpsd-dev +
  75. is appropriate for technical discussion about what changes should be
  76. made to *gpsd*. Questions about how to do things with *gpsd* are
  77. inappropriate on this list. (If you aren't reading the code, this
  78. list is likely not for you.)
  79. == IRC
  80. Some users and developers hang out on the "#gpsd" channel on IRC. All
  81. are welcome. Introduce your self. Depending on random chance someone
  82. may be available to chat right away, or it may require many hours for
  83. a response. Be patient, someone will reply.
  84. == PRIVATE MAIL TO MAINTAINERS
  85. A quick perusal of the lists will make it clear who is maintaining
  86. *gpsd* and contributing changes. Do not send private mail to these
  87. individuals asking for help. Ask your questions in public, on one of
  88. the *gpsd* mailing lists. Keep the conversation public, so that others
  89. can help you, and that the conversation will be of benefit to the whole
  90. community. The email lists are archived for the benefit of users in the
  91. future that encounter similar issues.
  92. If you need technical help in private, then you need a consultant, not
  93. free help from the project. Ask on one of the email lists if you need a
  94. consultant.
  95. It is acceptable to send private email when disclosing a security
  96. issue.
  97. == LONG TERM STABLE PACKAGING
  98. Note that there are a variety of distributions and packaging systems
  99. that contain *gpsd*. *gpsd* only provides source code and does not provide
  100. any packages. Some of these third party packages are kept relatively up
  101. to date, and some intentionally snapshot software at some point in time
  102. and then only apply security patches, sometimes for five years. These
  103. are typically called "long term stable" or "LTS", and are aimed at users
  104. who wish to avoid ABI or feature changes and only get bug reports.
  105. Occasionally, a user has appeared on the mailing list expecting support
  106. for an old version because it is contained in some LTS operating
  107. system they have chosen to run. The *gpsd* project lacks the resources
  108. to provide help about old versions, and support requests for old *gpsd*
  109. versions in LTS operating systems should be directed at the LTS OS
  110. supplier (or your paid consultant or support service).
  111. A related issue is obtaining a modified version of *gpsd* from a GPS
  112. chip vendor, leading to using old *gpsd* versions. The project
  113. encourages improvements to *gpsd* to be contributed back for the benefit
  114. of the greater *gpsd* community, and also to remove reasons for people
  115. to use old versions. People using an old version from a vendor should
  116. seek support from their vendor.
  117. == RESOURCES
  118. *Project web site:* {gpsdweb}
  119. == COPYING
  120. This file is Copyright 2020 by the GPSD project +
  121. SPDX-License-Identifier: BSD-2-clause