emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Brian van den Broek <brian.van.den.broek@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Small grammar tweaks in export sections of org.texi
Date: Wed, 25 Apr 2012 01:01:32 +0200	[thread overview]
Message-ID: <CAF6DajLxCip3UhvgP7p8O=3CL8E1N1mHK30rmzNf3epW3P3EvA@mail.gmail.com> (raw)
In-Reply-To: <87y5pkrexu.fsf@gnu.org>

On 24 April 2012 23:35, Bastien <bzg@gnu.org> wrote:
> Hi Brian,

<snip>

> Applied, thanks.
>
>> I've labelled it a TINYCHANGE. I am not sure of the exact bounds of what
>> can count as a tiny change, but all this does is insert `a', `an' and `in'
>> in a number of places in the docs.
>
> A "tiny change" is a change that modifies <= than 20 lines.

Hi Bastien,

Thanks for the reply.

I ought to have been more clear; I'd seen the >20 lines standard
before, but wasn't sure if 1) it was per patch or cumulative over all
patches and 2) if things like fixing a spelling mistake in a variable
name over many lines counted. I've read around some more and learned
(from <http://www.gnu.org/prep/maintain/maintain.html#Legally-Significant>)
that by the gnu projects standards, a) the limit is cumulative over
all patches, b) trivial changes like replacing many instances of a
name do not count, but multiple such sorts of changes "can" and c) the
standard they presently endorse is >15 lines. (Sadly, the document I
linked to is a model of neither clarity nor precision.)

>> I've quite a few other typo corrections / phrasing improvements I could
>> make to the docs, but I cannot presently sign the FSF papers. (I am on
>> leave, living abroad for the year, and won't be able to get my employer's
>> sign-off until I return home.) I'd appreciate being told if further
>> documentation patches can be accepted in these circumstances. If they
>> cannot, I will have to wait until I can address the FSF papers issue with
>> my employer.
>
> I suggest this:
>
> 1. try to figure out what really prevents you from assigning your
>   copyright to FSF (unless your job contract says "everything you write
>   in your free time belongs to us", I don't see a real problem here, but
>   of course I don't have all the cards in hands to judge appropriately.)

I don't think my employer (I teach Philosophy at the College-level)
has a basis to claim ownership of copyright on my work product, but I
also seem to have misplaced my law degree :-) I thus cannot
confidently say that it is false that I "have an employer who *might*
have a basis" to claim ownership of my changes.

I've written the relevant gnu.org address seeking clarification as to
whether my good faith belief suffices in my circumstances.

Thanks for the guidance. Best,

Brian

  reply	other threads:[~2012-04-24 23:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 16:10 Small grammar tweaks in export sections of org.texi Brian van den Broek
2012-04-24 21:35 ` Bastien
2012-04-24 23:01   ` Brian van den Broek [this message]
2012-04-26 13:54     ` Bastien
2012-04-30 16:45       ` Brian van den Broek
2012-04-30 23:46         ` Bastien

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='CAF6DajLxCip3UhvgP7p8O=3CL8E1N1mHK30rmzNf3epW3P3EvA@mail.gmail.com' \
    --to=brian.van.den.broek@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    /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).