README_GIT 3.4 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889
  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 git repository is hosted publicly at repo.or.cz. Anyone
  8. can get a clone of the current repository state using the
  9. command
  10. git clone git://repo.or.cz/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. People who are interested to participate in the Org-mode
  15. development can do so by sending patches to
  16. emacs-orgmode@gnu.org.
  17. 3. An interested developer can also request push access to the
  18. central repository by sending his/her user-info at repo.or.cz
  19. the maintainer of Org-mode.
  20. After you have been added as a user with push privileges,
  21. clone the repository through ssh using
  22. git+ssh://repo.or.cz/srv/git/org-mode.git
  23. By requesting push access, you acknowledge that you have read
  24. and agreed with the following rules:
  25. - Org-mode is part of Emacs. Therefore we need to be very
  26. conscious about changes moving into the Org-mode core.
  27. These can originate only from people who have signed the
  28. appropriate papers with the Free Software Foundation. The
  29. files to which this applies are:
  30. - all *.el files in the root directory of the repository
  31. - org.texi, orgcard.tex, and ChangeLog.
  32. - Before making any significant changes, please explain and
  33. discuss them on the mailing list emacs-orgmode@gnu.org.
  34. This does obviously not apply to people who are maintaining
  35. their own contributions to Org-mode. Please, just use the
  36. new mechanism to make sure all changes end up in the right
  37. place.
  38. - Creating and pushing a change to the Org-mode core requires
  39. you also to provide ChangeLog entries. Just press `C-x 4 a'
  40. in each function or variable you have modified and describe
  41. the change you made in the ChangeLog buffer/file.
  42. - Among other things, Org-mode is widely appreciated because
  43. if its simplicity, cleanness and consistency. We should try
  44. hard to preserve this and I would like to ask everyone to
  45. keep this in mind when developing changes.
  46. * The CONTRIB directory
  47. The git repository contains a CONTRIB directory. This directory
  48. is the playing field for any developer, also people who have not
  49. (yet) signed the papers with the FSF. You are free to add files
  50. to this directory, implementing extensions, new link types etc.
  51. Also non-Lisp extensions like scripts to process Org-mode files
  52. in different ways are welcome in this directory. You should
  53. provide documentation with your extensions, at least in the form
  54. of commentary in the file. Please discuss your extensions on
  55. emacs-orgmode@gnu.org.
  56. The CONTRIB directory will be part of the Org-mode distribution
  57. starting with version 5.21. When that happens, people who want
  58. to use extensions will have to make sure their search path
  59. (executable or Lisp) includes the relevant directories.
  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 CVS tree. The final decision about this rests with the
  65. maintainer.