README_GIT 3.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485
  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. This file explains the rules for participating in Org-mode
  5. development.
  6. * Main rules
  7. 1. The git repository is hosted publicly at repo.or.cs. 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 be 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. Any interested developer can request push access to the
  18. repository by sending their repo.or.cz user information to the
  19. maintainer of Org-mode. By requesting push access, you
  20. acknowledge that you have read and agreed with the following
  21. rules:
  22. - Org-mode is part of Emacs. Therefore we need to be very
  23. conscious that any changes moving into the Org-mode core are
  24. done only by people who have signed the appropriate papers
  25. with the free software foundation. The files to which this
  26. applies are:
  27. - all *.el files in the root directory of the repository
  28. - org.texi, orgcard.tex, and ChangeLog.
  29. - Before making any significant changes, please explain and
  30. discuss them on the mailing list emacs-orgmode@gnu.org.
  31. This does obviously not apply to people like Bastien Guerry,
  32. David O'Toole, Piotr Zielinski, or anyone else who has
  33. contributed and still maintains a file that is part of
  34. Org-mode. Please, just use the new mechanism to make sure
  35. all changes end in the right place.
  36. - Making and pushing a change to the Org-mode core requires
  37. you also to provide ChangeLog entries. Just press `C-x 4 a'
  38. in each function or variable you have modified and describe
  39. the change you made in the ChangeLog buffer/file. This is
  40. important, because these entries will be required when
  41. uploading any new version into the Emacs CVS tree.
  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 6.0 (the first release after 5.20). When
  58. that happens, people who want to use extensions will have to make
  59. sure their search path (executable or Lisp) includes the relevant
  60. directories.
  61. After files have been tested in CONTRIB and found to be generally
  62. useful, we may decide to clarify copyright questions and then
  63. move the file into the Org-mode core. This means they will be
  64. moved up to the root directory and will also eventually be added
  65. to Emacs CVS tree. The final decision about this rests with the
  66. maintainer.