From: John Darrington <jmd@gnu.org>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: maintainers@gnu.org, guile-devel@gnu.org
Subject: Re: A request to take charge of guile-zmq
Date: Mon, 12 Sep 2016 14:10:33 -0400 [thread overview]
Message-ID: <20160912181033.GA27007@gnu.org> (raw)
In-Reply-To: <1473692578.16971.14.camel@gmail.com>
Please don't use github for GNU programs (or parts thereof). For ethical reasons
github is unacceptable for us.
See https://www.gnu.org/software/repo-criteria-evaluation.html for a list of what
we can and cannot use.
J'
On Mon, Sep 12, 2016 at 11:02:58PM +0800, Nala Ginrut wrote:
> I plan to use guile-zmq in my work. Also, guile-zmq may play an important role
> in Artanis.??
>
> Thanks Wingo for all previous work. If you don't mind, I would like to take
> charge of guile-zmq for improving and maintaining.
>
> Here's the new repo:
>
> https://github.com/NalaGinrut/guile-zmq
>
>
> Contributions welcome!
> Thanks!
next prev parent reply other threads:[~2016-09-12 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 15:02 A request to take charge of guile-zmq Nala Ginrut
2016-09-12 18:10 ` John Darrington [this message]
2016-09-12 19:04 ` Nala Ginrut
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160912181033.GA27007@gnu.org \
--to=jmd@gnu.org \
--cc=guile-devel@gnu.org \
--cc=maintainers@gnu.org \
--cc=nalaginrut@gmail.com \
/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.
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).