> David Engster <deng@...> writes:
>> - I think the FSF only has papers from you for past changes, not for
>> future ones.
> I tried to sign papers, but FSF is not willing to let me sign papers,
> because I am unable to get my employer to also sign papers. I am
> willing to sign all necessary papers for contributing emacs related work
> to FSF, but apparently that is not sufficient without my employers
If the employer "might have a basis to claim to own your changes" then
yes, the FSF will require papers from it.
> It is my understanding that I can still make "small constributions"
> without signing papers where "small" is loosely defined as about 50
> lines of change according to Yidong.
The limit is only at ~15 lines. Also, those so called 'tiny changes' can
add up to a legally significant contribution, meaning that two patches
with 10 lines each would already require papers:
> My current contribution is certainly less than 50 lines all of which
> is a trivial tweak of existing code.
If you contribute actual code, it is non-trivial. Only stuff like
renames, indentation/whitespace changes or simple typo fixes are seen as
> So I'm in a very frustrating situation where I am willing to contribute,
> but FSF won't accept my work in general, so I have to limit my
> contributions to only "small" ones.
I understand your frustration, but there's not much we can do about
that. You can contribute as much as you like as long as that code
doesn't get merged into Emacs (this stuff usually lands in
/contrib). However, this would only make sense for separate packages.
Would it be possible for you to get papers for past changes? Maybe we
could figure something out, then.
> Please let me know if the following is sufficient.
Yes, that's fine.