From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] alure 1.2
Date: Sat, 15 Oct 2016 09:29:00 -0000 [thread overview]
Message-ID: <554d3c2d-fcc6-9de7-8d70-4ef487ce311f@tiscali.co.uk> (raw)
In-Reply-To: <CAK8TuTryK2NkZt8Bb0GO=Nc7q1-K86SJr+GxLEcP9VbyyD4ctw@mail.gmail.com>
On 13/10/16 18:05, Bastian Germann wrote:
> it's almost 4 weeks since I submitted the package. Is there something
> wrong with my email to not be answered? I think, I followed the
> Contributor's Guide pretty close.
>
> Is someone willing to review the package?
It's probably only polite for /someone/ on the list to reply, although
in fairness I'm probably not the most qualified person to do so. You may
be aware that Cygwin package maintainers are mostly volunteers who have
to juggle real life (jobs, families, etc.) with Open Source work. The
bulk of Cygwin packages are maintained by a surprisingly small number of
individuals, and sometimes real life demands mean that there is little
time to review new contributions. That's not to say that new packages
aren't wanted (they are), it's just that occasionally there is no-one
with sufficient time to undertake a review. 'alure' isn't too big, but
any package the size of 'gambas3' is going to take quite some time to
pick through.
The other problem with 'alure' is one of scope: I'm not sure how many
maintainers are interested or familiar with sound on Cygwin. Yaakov or
Marco would probably have the best knowledge to perform a review, but it
depends on their availability. It's certainly a couple of years since I
last dabbled with sound on Cygwin.
Dave.
next prev parent reply other threads:[~2016-10-15 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 10:32 Bastian Germann
2016-10-13 17:05 ` Bastian Germann
2016-10-15 9:29 ` David Stacey [this message]
2016-10-16 21:30 ` Marco Atzeri
2016-10-17 13:46 ` Bastian Germann
2016-10-17 19:38 ` Ken Brown
2016-10-17 21:46 ` Bastian Germann
2016-10-18 0:06 ` Bastian Germann
2016-10-24 12:37 ` Jon Turney
2016-10-24 17:21 ` SSH key for upload access Bastian Germann
2016-10-28 16:47 ` Yaakov Selkowitz
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=554d3c2d-fcc6-9de7-8d70-4ef487ce311f@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--cc=cygwin-apps@cygwin.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).