CONTRIBUTE 3.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384
  1. -*- mode: org; fill-column:70 -*-
  2. The text below explains the rules for participating in Org mode
  3. development.
  4. * Main contribution rules
  5. 1. The master git repository is hosted publicly on [[https://savannah.gnu.org][savannah.gnu.org]].
  6. : git clone https://git.savannah.gnu.org/git/emacs/org-mode.git
  7. This is sufficient to start hacking and to produce patches that can
  8. easily and consistently be applied to the main repository.
  9. 2. People who want to participate to the Org mode development can send
  10. patches to this address:
  11. : emacs-orgmode@gnu.org
  12. 3. If you are a regular contributor, you can request push access to
  13. the repository by creating an account on [[https://savannah.gnu.org/account/register.php][savannah.gnu.org]] and by
  14. [[https://savannah.gnu.org/git/?group=emacs][joining the Emacs group]].
  15. After you have been added as a user with push privileges, you can
  16. clone the repository like this:
  17. : git clone USERNAME@git.savannah.gnu.org:/srv/git/emacs/org-mode.git
  18. Replace =USERNAME= with your Savannah username.
  19. 4. By requesting push access, you acknowledge that you have read and
  20. agreed with the following rules:
  21. - Org mode is part of GNU Emacs. Therefore, we need to be very
  22. conscious about changes moving into the Org mode core. These can
  23. originate only from people who have signed the appropriate papers
  24. with the Free Software Foundation. The files to which this
  25. applies are:
  26. - all *.el files in the lisp directory of the repository
  27. - org.texi, orgcard.tex in the doc/ directory
  28. - Before making any significant changes, please explain and discuss
  29. them on the mailing list [[mailto:emacs-orgmode@gnu.org][emacs-orgmode@gnu.org]].
  30. This does obviously not apply to people who are maintaining their
  31. own contributions to Org mode. Please just use the new mechanism
  32. to make sure all changes end up in the right place.
  33. We value a nice tone in our discussions: please check and respect
  34. the [[https://www.gnu.org/philosophy/kind-communication.en.html][GNU Kind Communications Guidelines]].
  35. - Org mode no longer uses ChangeLog entries to document changes.
  36. Instead, special commit messages are used, as described in the
  37. `CONTRIBUTE' file in the main Emacs repository.
  38. - Among other things, Org mode is widely appreciated because of its
  39. simplicity, cleanness and consistency. We should try to preserve
  40. them and ask everyone to keep this in mind when posting changes.
  41. See [[https://orgmode.org/worg/org-contribute.html][worg/org-contribute]] for guidance on how to contribute effectively.
  42. * The contrib/ directory
  43. The git repository contains a =contrib/= directory. This directory is
  44. the playing field for any developer, also people who have not (yet)
  45. signed the papers with the FSF. You are free to add files to this
  46. directory, implementing extensions, new link types etc.
  47. Also non-Lisp extensions like scripts to process Org files in
  48. different ways are welcome in this directory. You should provide
  49. documentation with your extensions, at least in the form of commentary
  50. in the file, better on worg. Please discuss your extensions on
  51. [[mailto:emacs-orgmode@gnu.org][emacs-orgmode@gnu.org]].
  52. After files have been tested in =contrib/= and found to be generally
  53. useful, we may decide to clarify copyright questions and then move the
  54. file into the Org mode core. This means they will be moved up to the
  55. root directory and will also eventually be added to GNU Emacs git
  56. repository. The final decision about this rests with the maintainer.
  57. * Org maintenance
  58. Org maintenance is explained on Worg: see [[https://orgmode.org/worg/org-maintenance.html][org-maintenance]].