From: Marcin Borkowski <mbork@mbork.pl>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: A problem with old bugs
Date: Tue, 07 Mar 2017 07:17:33 +0100 [thread overview]
Message-ID: <87h935626a.fsf@jane> (raw)
In-Reply-To: <CAM-tV-9-e01zL0SQUUFg_AQDZvATom-SNHeXCfNUGKyKNrrmtQ@mail.gmail.com>
On 2017-03-02, at 13:33, Noam Postavsky <npostavs@users.sourceforge.net> wrote:
> On Thu, Mar 2, 2017 at 2:38 AM, Thien-Thi Nguyen <ttn@gnu.org> wrote:
>>
>> I'm not familiar w/ full details these days, but i think
>> generally you need to ask the maintainer for them, in the
>> process making some convincing arguments that you will not
>> besmirch Emacs and GNU (by introducing or advocating non-Free
>> software, for example), and that your interaction w/ the project
>> will be a net positive. Once swayed, the maintainer starts the
>> paperwork process (which might involve snail mail), and If All
>> Goes Well, you will be notified one day.
>
> Paper is only needed for copyright assignment, to get write access you
> just make a request here: https://savannah.nongnu.org/my/groups.php
I have had my papers signed for some time now, this is not a problem.
Best,
--
Marcin Borkowski
next prev parent reply other threads:[~2017-03-07 6:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 8:22 A problem with old bugs Marcin Borkowski
2017-03-01 10:26 ` Thien-Thi Nguyen
2017-03-01 13:28 ` Marcin Borkowski
2017-03-02 7:38 ` Thien-Thi Nguyen
2017-03-02 12:33 ` Noam Postavsky
2017-03-02 16:53 ` Richard Stallman
2017-03-07 6:17 ` Marcin Borkowski [this message]
2017-03-06 13:19 ` Phillip Lord
2017-03-07 6:16 ` Marcin Borkowski
2017-03-07 12:24 ` Phillip Lord
2017-03-01 16:16 ` Eli Zaretskii
2017-03-07 6:15 ` Marcin Borkowski
2017-03-07 16:51 ` Eli Zaretskii
2017-03-08 7:01 ` Marcin Borkowski
2017-03-08 16:08 ` Eli Zaretskii
2017-05-21 16:00 ` John Wiegley
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h935626a.fsf@jane \
--to=mbork@mbork.pl \
--cc=emacs-devel@gnu.org \
--cc=npostavs@users.sourceforge.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.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).