emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Akira Kyle <akira@akirakyle.com>
To: Bastien Guerry <bzg@gnu.org>
Cc: Ihor Radchenko <yantar92@posteo.net>,
	Ihor Radchenko <yantar92@gmail.com>,
	emacs-orgmode@gnu.org
Subject: Re: svg file from tikz picture
Date: Sat, 05 Aug 2023 12:38:20 -0600	[thread overview]
Message-ID: <m2jzu9xr4s.fsf@akirakyle.com> (raw)
In-Reply-To: <87pm41cs9l.fsf@bzg.fr>


On Sat, Aug 05, 2023 at 07:29 PM, Bastien Guerry <bzg@gnu.org> 
wrote:

> Ihor Radchenko <yantar92@posteo.net> writes:
>
>> Akira, may I know if you managed to clear the FSF paperwork?
>
> I've just checked and Akira's is a registered FSF contributor 
> since
> last may.

Unfortunately I was informed that I am only allowed to make 
"small" contributions. I wasn't given any explicit metric of what 
qualifies as a "small" contribution, but was informed that patches 
such as this one are okay for me to contribute.

This is due to my university being unwilling to sign the FSF 
copyright disclaimer without involvement from their legal team 
(although they did sign a standard letter they have saying the 
would never claim copyright over emacs, but that disclaimer does 
not name me personally). I have been informed that this document 
my university has provided is queued with the FSF legal team for 
eventual review.

It's been five years since I initially wrote this patch and two 
years since I started my assignment processes so I haven't really 
had the time or motivation to get this patch into a merge-able 
state. I still use this code quite regularly myself so I'll 
probably get around to working on it again and some point in the 
future.

Akira


  reply	other threads:[~2023-08-05 18:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3bc47afb-0bac-f6e8-1097-13dcb6f2be1f@housseini.me>
2022-08-15 18:50 ` svg file from tikz picture reza
2022-08-16  9:42   ` Ihor Radchenko
     [not found]     ` <964a4117-ef6c-8d41-a25d-00e61c0c93d8@housseini.me>
2022-08-16 10:00       ` reza
2022-08-16 10:13         ` Ihor Radchenko
     [not found]           ` <0931497c-9075-c214-c7f2-6507340a6d74@housseini.me>
2022-08-16 10:19             ` reza
2022-08-16 10:31               ` Ihor Radchenko
     [not found]                 ` <6daeb56b-163c-f862-5866-da624b43edd9@housseini.me>
2022-08-16 11:06                   ` reza
2022-08-16 11:22                     ` Ihor Radchenko
     [not found]                       ` <7dcd1348-6faf-8464-38b5-8efac7c69250@housseini.me>
2022-08-16 11:25                         ` reza
     [not found]                           ` <be3e5412-37ff-c1c7-7a27-3793d72842d4@housseini.me>
2022-09-20  9:55                             ` reza
2022-09-20 20:53                               ` Edouard Debry
2022-09-21  9:32                               ` Ihor Radchenko
2022-09-23  2:28                                 ` Akira Kyle
2022-09-25  7:52                                   ` Ihor Radchenko
2022-11-14  5:52                                     ` Ihor Radchenko
2023-03-24 23:22                                       ` Akira Kyle
2023-03-25 18:13                                         ` Ihor Radchenko
2023-03-25 18:14                                           ` Akira Kyle
2023-03-25 18:25                                             ` Ihor Radchenko
2023-04-19  9:57                                               ` Bastien Guerry
2023-08-05  9:34                                                 ` Ihor Radchenko
2023-08-05 17:29                                                   ` Bastien Guerry
2023-08-05 18:38                                                     ` Akira Kyle [this message]
2023-08-06  5:37                                                       ` Bastien Guerry
2023-08-06  5:40                                                       ` Bastien Guerry
2023-10-19  9:51                                                       ` Ihor Radchenko

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=m2jzu9xr4s.fsf@akirakyle.com \
    --to=akira@akirakyle.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    --cc=yantar92@posteo.net \
    /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).