From: Aaron Ecay <aaronecay@gmail.com>
To: "Łukasz Gruner" <lukasz@gruner.lu>, emacs-orgmode@gnu.org
Subject: Re: Contribution to org-mode, Eldoc support
Date: Sun, 02 Nov 2014 18:05:50 +0000 [thread overview]
Message-ID: <87vbmxmq9t.fsf@gmail.com> (raw)
In-Reply-To: <1414854809.2065381.185865461.013CDA28@webmail.messagingengine.com>
Hi Lukasz,
Thanks for your contribution.
2014ko azaroak 1an, Łukasz Gruner-ek idatzi zuen:
>
> Hi
>
> I would like to contribute Eldoc support.
> I've already changed license, but dont quite get that pgp part, I have
> generated my pgp and now what?
There’s a couple of issues.
1. Write access to the org repository. For that you need an SSH (not
PGP) key. This tutorial from GitHub
<https://help.github.com/articles/generating-ssh-keys/> goes over
what is needed. When you get to step 3, instead of entering the key
file in GitHub’s website, you email it to Jason Dunsmore or Bastien
Guerry.
2. Copyright assignment. For code in org’s core, you need to have a
copyright assignment on file with the FSF (because any code in org
will eventually become part of emacs). The process is documented
here: <http://orgmode.org/worg/org-contribute.html#unnumbered-2>.
The org mode repo has a contrib directory, where it is OK to put code
without a copyright assignment. This is bundled into
org-plus-contrib packages that many people install, but cannot be put
into emacs releases.
So org-eldoc can be added to contrib immediately, and then moved to
the core (i.e. out of contrib) when the copyright assignment is
complete (if you decide that copyright assignment is something you
want to do, and also subject to the judgment of the org maintainers).
Does that make sense?
Thanks again,
--
Aaron Ecay
next prev parent reply other threads:[~2014-11-02 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 15:13 Contribution to org-mode, Eldoc support Łukasz Gruner
2014-11-02 18:05 ` Aaron Ecay [this message]
2014-11-02 19:28 ` Rasmus
2014-11-07 17:04 ` Łukasz Gruner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbmxmq9t.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=lukasz@gruner.lu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).