public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Mohammad-Reza Nabipoor <mnabipoor@gnu.org>
Subject: Re: Request of new project: pacme
Date: Tue, 20 Sep 2022 23:54:10 +0200	[thread overview]
Message-ID: <Yyo2gjRe5JcBxyBN@wildebeest.org> (raw)
In-Reply-To: <Yyh/JiysP2D7By6n@schwinger>

Hi Mohammad-Reza,

On Mon, Sep 19, 2022 at 07:09:34PM +0430, Mohammad-Reza Nabipoor via Overseers wrote:
> I'm Mohammad-Reza Nabipoor and a GNU poke contributor and I'd like to host
> a project of mine called "pacme" (An acme-like interface to GNU poke) in
> sourceware.  See below for details on the project.
> 
> The code is licensed under GPLv3+, and we plan to eventually apply to make
> pacme an official GNU program, so we are following all the GNU standards and
> conventions.
> 
> I'd need the following project resources if possible:
> 
>   - An empty git repository called pacme.git
>   - A homepage in sourceware.org/pacme
>   - A way to distribute released tarballs like a FTP
> 
> We'll be using the GNU poke development list for discussion, and the poke bugzilla
> that is already in sourceware.  So we don't need any additional things.

Sourceware does host some GNU projects, but I assume you want to be as
close to poke as possible.

GNU poke uses savannah for git and ftp.gnu.org for releases.  Do you
intend to move over to savannah and ftp.gnu.org once you are a GNU
package?

If so, would starting out on savannah.non-gnu be an option to make
migration simpler?

Cheers,

Mark

  reply	other threads:[~2022-09-20 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 14:39 Mohammad-Reza Nabipoor
2022-09-20 21:54 ` Mark Wielaard [this message]
2022-09-21 10:42   ` Mohammad-Reza Nabipoor
2022-09-23 13:28 ` Frank Ch. Eigler
2022-09-23 14:15   ` Mohammad-Reza Nabipoor

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yyo2gjRe5JcBxyBN@wildebeest.org \
    --to=mark@klomp.org \
    --cc=mnabipoor@gnu.org \
    --cc=overseers@sourceware.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.
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).