Re: Open RFS lacking (further) response
- To: firstname.lastname@example.org
- Subject: Re: Open RFS lacking (further) response
- From: Asheesh Laroia <email@example.com>
- Date: Mon, 1 Nov 2010 23:00:23 -0400 (EDT)
- Message-id: <alpine.DEB.firstname.lastname@example.org>
- In-reply-to: <20101031083042.GB11320@merveille.plessy.net>
- References: <20101029072237.GB85092@l04.local> <AANLkTin=_qYKzeC+bYtpn_NZuhM5A91JRiUnOw_nqNRz@mail.gmail.com> <email@example.com> <20101030065957.GA5882@l04.lan> <4CCBD80D.firstname.lastname@example.org> <20101030195945.GE6538@l04.lan> <20101031083042.GB11320@merveille.plessy.net>
On Sun, 31 Oct 2010, Charles Plessy wrote:
Le Sat, Oct 30, 2010 at 09:59:45PM +0200, Michael Tautschnig a écrit :
I think this is a superb step in the right direction; while clearly the list on
mentors.debian.net, as suggested in another email in this thread, is the more
comprehensive list of packages in need of sponsorship, this web page is a proper
list of RFS needing attention.
I just read a post on Planet Debian about pull requests:
RFS has something similar in concept to pull requests. How about including in
the RFS emails a link to the most relevant diff in the web interface of the VCS
where the package is stored ? This will help to have the changes seen by many
I think that is a great idea, so long as it's an "updated package" RFS.
Do you see a way to make the idea work for all RFSs? (Honest question;
trying to get a sense of what you mean.)
Q: What is the sound of one cat napping?