README_GIT 3.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. -*- mode: org; fill-column:65 -*-
  2. This is the GIT repository for the development of Org-mode, an
  3. Emacs mode for organizing your life.
  4. The text below explains the rules for participating in Org-mode
  5. development.
  6. * Main rules
  7. 1. The master git repository is hosted publicly at orgmode.org.
  8. Anyone can get a clone of the current repository state using
  9. the command
  10. git clone git://orgmode.org/org-mode.git
  11. Having a clone is sufficient to start hacking and to produce
  12. patches that can easily and consistently be applied to the
  13. main repository.
  14. 2. There is a mirror hosted publicly at repo.or.cz. Anyone can
  15. get a clone of the current repository state using the command
  16. git clone git://repo.or.cz/org-mode.git
  17. 3. People who are interested to participate in the Org-mode
  18. development can to so by sending patches to this address:
  19. emacs-orgmode@gnu.org
  20. 4. An interested developer can also request push access to the
  21. central repository by sending her/his user-info to the
  22. maintainer of Org-mode or the webmaster of orgmode.org.
  23. After you have been added as a user with push privileges,
  24. clone the repository through ssh using
  25. git clone orgmode@orgmode.org:org-mode.git
  26. By requesting push access, you acknowledge that you have read
  27. and agreed with the following rules:
  28. - Org-mode is part of Emacs. Therefore, we need to be very
  29. conscious about changes moving into the Org-mode core.
  30. These can originate only from people who have signed the
  31. appropriate papers with the Free Software Foundation. The
  32. files to which this applies are:
  33. - all *.el files in the lisp directory of the repository
  34. - org.texi, orgcard.tex in the doc directory
  35. - the corresponding ChangeLog files
  36. - Before making any significant changes, please explain and
  37. discuss them on the mailing list emacs-orgmode@gnu.org.
  38. This does obviously not apply to people who are maintaining
  39. their own contributions to Org-mode. Please, just use the
  40. new mechanism to make sure all changes end up in the right
  41. place.
  42. - Creating and pushing a change to the Org-mode core requires
  43. you also to provide ChangeLog entries. Just press `C-x 4 a'
  44. in each function or variable you have modified and describe
  45. the change you made in the ChangeLog buffer/file.
  46. - Among other things, Org-mode is widely appreciated because
  47. of its simplicity, cleanness and consistency. We should try
  48. hard to preserve this and I would like to ask everyone to
  49. keep this in mind when developing changes.
  50. * The contrib directory
  51. The git repository contains a contrib directory. This directory
  52. is the playing field for any developer, also people who have not
  53. (yet) signed the papers with the FSF. You are free to add files
  54. to this directory, implementing extensions, new link types etc.
  55. Also non-Lisp extensions like scripts to process Org-mode files
  56. in different ways are welcome in this directory. You should
  57. provide documentation with your extensions, at least in the form
  58. of commentary in the file, better on worg. Please discuss your
  59. extensions on emacs-orgmode@gnu.org.
  60. After files have been tested in contrib and found to be generally
  61. useful, we may decide to clarify copyright questions and then
  62. move the file into the Org-mode core. This means they will be
  63. moved up to the root directory and will also eventually be added
  64. to Emacs bzr repository. The final decision about this rests
  65. with the maintainer.