~bzg/worg

2680e65db5703efa1c1ffb17b353859034d92ba4 — Adam Porter 2 months ago 5e414cf
* org-maintenance.org (Copyright assignments): Minor improvements
1 files changed, 23 insertions(+), 19 deletions(-)

M org-maintenance.org
M org-maintenance.org => org-maintenance.org +23 -19
@@ 450,34 450,38 @@ Then commit and push the change on the =worg.git= repository.
:CUSTOM_ID: copyright
:END:

Maintainers need to keep track of copyright assignments.  Even better,
find a volunteer to do this.
*** Assignment and verification

You can point to [[https://orgmode.org/request-assign-future.txt][orgmode.org/request-assign-future.txt]] or get the form
from within the [[https://git.sr.ht/~bzg/orgweb/][orgweb]] repository.
Maintainers need to keep track of copyright assignments.  A [[https://orgmode.org/worg/org-contribute.html][list of
contributors who have assigned copyright to the FSF]] is available so
that committers can confirm whether a patch can be installed.

The list of all contributors from who we have the papers is kept on
[[https://orgmode.org/worg/org-contribute.html][this Worg page]], so that committers can check if a patch can go into
the core.
#+begin_center
TODO: Even better, find a volunteer to maintain this information!
#+end_center

The assignment process does not always go smoothly, and it has
happened several times that it gets stuck or forgotten at the FSF.
The contact at the FSF for this is: =copyright-clerk AT fsf DOT org=
New contributors need to submit the [[https://orgmode.org/request-assign-future.txt][form]] to the FSF.

Emails from the paper submitter have been ignored in the past, but an
email from the maintainers of Org mode has usually fixed such cases
within a few days.
#+begin_center
TODO: Get updated version of form from Emacs maintainers that includes the line asking the secretary to send confirmation to interested parties (i.e. the Org maintainers).
#+end_center

When submitting a change on someone's behalf, it's important that the
author field of the commit contains the name and email of the person
who authored the change.
The assignment process does not always go quickly; occasionally it may
get stuck or overlooked at the FSF.  The contact at the FSF for this
is: =copyright-clerk AT fsf DOT org=.  In rare cases, an inquiry from an
Org maintainer gets the process moving again.

*** Authorship information

This may be done with the ~--author~ option:
When submitting a change on someone's behalf, it's important that the
~author~ field of the commit has the correct name and email address of
the person who authored the change.  This may be done with the
~--author~ option:

#+begin_src sh :eval never
git commit --author "Arthur D. Author <arthur's-email>"
git commit --author "Arthur D. Author <author@example.com>"
#+end_src

Making sure the author field corresponds to the contributor, and not
the committor, helps us track the number changed lines for
the committer, helps us track the number of changed lines for
contributors without FSF copyright assignment.