README 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107
  1. DO NOT "FIX" CODE IN THIS DIRECTORY.
  2. ONLY UPSTREAM VERSIONS OF SOFTWARE GO IN THIS DIRECTORY.
  3. This directory is provided as a courtesy to our users who might be
  4. unable or unwilling to find and install libraries we depend on.
  5. If we "fix" software in this directory, we hamstring users who do the
  6. right thing and keep a single version of upstream libraries in a
  7. system-wide library. We introduce subtle and maddening bugs where
  8. our code is "accidentally" using the "wrong" library version. We may
  9. unwittingly interfere with other software that depends on the
  10. canonical release versions of those same libraries!
  11. Forking upstream software for trivial reasons makes us bad citizens in
  12. the Open Source community and adds unnecessary heartache for our
  13. users. Don't make us "that" project.
  14. Frequently Asked Questions
  15. --------------------------
  16. Q: What should we do when we find a bug in upstream software?
  17. A: First and foremost, REPORT THE BUG, and if possible send in a patch.
  18. Watch for a release of the upstream software and integrate with it
  19. when it's released.
  20. In the meantime, work around the bug, if at all possible. Usually,
  21. it's quite possible, if slightly harder or less efficient.
  22. Q: What if the bug can't be worked around?
  23. A: If the upstream developers have accepted a bug patch, it's
  24. undesirable but acceptable to apply that patch to the library in
  25. the extlib dir. Ideally, use a release version for upstream or a
  26. version control system snapshot.
  27. Note that this is a last resort.
  28. Q: What if upstream is unresponsive or won't accept a patch?
  29. A: Try again.
  30. Q: I tried again, and upstream is still unresponsive and nobody's
  31. checked on my patch. Now what?
  32. A: If the upstream project is moribund and there's a way to adopt it,
  33. propose having the GNU social dev team adopt the project. Or, adopt
  34. it yourself.
  35. Q: What if there's no upstream authority and it can't be adopted?
  36. A: Then we fork it. Make a new name and a new version. Include it in
  37. lib/ instead of extlib/, and use the GNUsocial_* prefix to change
  38. the namespace to avoid collisions.
  39. This is a last resort; consult with the rest of the dev group
  40. before taking this radical step.
  41. List of external libraries
  42. --------------------------
  43. A number of external PHP libraries are used to provide basic
  44. functionality and optional functionality for your system. For your
  45. convenience, they are available in the "extlib" directory of this
  46. package, and you do not have to download and install them. However,
  47. you may want to keep them up-to-date with the latest upstream version,
  48. and the URLs are listed here for your convenience.
  49. - DB_DataObject http://pear.php.net/package/DB_DataObject
  50. - Validate http://pear.php.net/package/Validate
  51. - OpenID by Janrain, http://janrain.com/openid-enabled/
  52. - PEAR DB. Although this is an older data access system (new
  53. packages should use PDO), the OpenID libraries depend on PEAR DB
  54. or MDB2.
  55. - OAuth.php from http://oauth.googlecode.com/svn/code/php/
  56. (has been edited to avoid colliding autoload)
  57. - markdown.php from http://michelf.com/projects/php-markdown/
  58. - PEAR Mail, for sending out mail notifications
  59. http://pear.php.net/package/Mail
  60. - PEAR Net_SMTP, if you use the SMTP factory for notifications
  61. http://pear.php.net/package/Net_SMTP
  62. - PEAR Net_Socket, if you use the SMTP factory for notifications
  63. http://pear.php.net/package/Net_Socket
  64. - XMPPHP, the follow-up to Class.Jabber.php. Probably the best XMPP
  65. library available for PHP. https://github.com/heshanlk/XMPPHP. Note that
  66. as of this writing the version of this library that is available in
  67. the extlib directory is *significantly different* from the upstream
  68. version (patches have been submitted). Upgrading to the upstream
  69. version may render your GNU social site unable to send or receive XMPP
  70. messages.
  71. - Facebook library. Used for the Facebook application.
  72. - PEAR Validate is used for URL and email validation.
  73. - Console_GetOpt for parsing command-line options.
  74. - HTTP_Request2, a library for making HTTP requests.
  75. - PEAR Net_URL2 is an HTTP_Request2 dependency.
  76. - Michelf/Markdown.php Markdown parser library
  77. - Mf2/Parser.php microformats2 parser library
  78. A design goal of GNU Social is that the basic Web functionality should
  79. work on even the most restrictive commercial hosting services.
  80. However, additional functionality, such as receiving messages by XMPP,
  81. require that you be able to run long-running processes on your account.
  82. In addition, posting by email require that you be able to install a mail
  83. filter in your mail server.