summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBastien <bzg@gnu.org>2017-12-29 18:58:14 +0100
committerBastien <bzg@gnu.org>2017-12-29 18:58:14 +0100
commita4d4f9701c2f3e9b16b49d286f8b560423fd6eab (patch)
tree4ff3b5addf33a1be11ed157b33157062cc3a0596
parentd792b57ffc4e1672b92aaf2f67aac44f6aa6c217 (diff)
downloadorg-mode-a4d4f9701c2f3e9b16b49d286f8b560423fd6eab.tar.gz
README_contribute: Update instructions
-rw-r--r--README_contribute31
1 files changed, 16 insertions, 15 deletions
diff --git a/README_contribute b/README_contribute
index bc1324c..69d4e36 100644
--- a/README_contribute
+++ b/README_contribute
@@ -12,7 +12,7 @@ development.
Anyone can get a clone of the current repository state using
the command
- git clone git://orgmode.org/org-mode.git
+ git clone https://code.orgmode.org/bzg/org-mode.git
Having a clone is sufficient to start hacking and to produce
patches that can easily and consistently be applied to the
@@ -23,19 +23,19 @@ development.
git clone git://repo.or.cz/org-mode.git
-3. People who are interested to participate in the Org mode
+3. People who are interested in participating to the Org mode
development can do so by sending patches to this address:
[[mailto:emacs-orgmode@gnu.org][emacs-orgmode@gnu.org]]
4. An interested developer can also request push access to the
- central repository by sending her/his user-info to the
- maintainer of Org mode or the webmaster of orgmode.org.
+ central repository by creating an account on code.orgmode.org
+ and by sending her/his user info to the maintainer.
After you have been added as a user with push privileges,
clone the repository through ssh using
- git clone orgmode@orgmode.org:org-mode.git
+ git clone git@code.orgmode.org:bzg/org-mode.git
By requesting push access, you acknowledge that you have read
and agreed with the following rules:
@@ -65,24 +65,25 @@ development.
- Among other things, Org mode is widely appreciated because
of its simplicity, cleanness and consistency. We should try
- hard to preserve this and I would like to ask everyone to
- keep this in mind when developing changes.
+ hard to preserve this and ask everyone to keep this in mind
+ when developing changes.
-* The contrib directory
+* The contrib/ directory
-The git repository contains a contrib directory. This directory
+The git repository contains a =contrib/= directory. This directory
is the playing field for any developer, also people who have not
(yet) signed the papers with the FSF. You are free to add files
to this directory, implementing extensions, new link types etc.
+
Also non-Lisp extensions like scripts to process Org files in
different ways are welcome in this directory. You should provide
documentation with your extensions, at least in the form of
commentary in the file, better on worg. Please discuss your
extensions on [[mailto:emacs-orgmode@gnu.org][emacs-orgmode@gnu.org]].
-After files have been tested in contrib and found to be generally
-useful, we may decide to clarify copyright questions and then
-move the file into the Org mode core. This means they will be
-moved up to the root directory and will also eventually be added
-to GNU Emacs bzr repository. The final decision about this rests
-with the maintainer.
+After files have been tested in =contrib/= and found to be
+generally useful, we may decide to clarify copyright questions
+and then move the file into the Org mode core. This means they
+will be moved up to the root directory and will also eventually
+be added to GNU Emacs git repository. The final decision about
+this rests with the maintainer.