From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: phillip.lord@russet.org.uk (Phillip Lord) Newsgroups: gmane.emacs.devel Subject: Re: In support of Jonas Bernoulli's Magit Date: Mon, 10 Jul 2017 13:47:41 +0100 Message-ID: <87k23g1ms2.fsf@russet.org.uk> References: <8737aac0rb.fsf@wanadoo.es> <7s37aapc4g.fsf@fencepost.gnu.org> <87fue7c32j.fsf@russet.org.uk> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1499690952 16545 195.159.176.226 (10 Jul 2017 12:49:12 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 10 Jul 2017 12:49:12 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2.50 (gnu/linux) Cc: ofv@wanadoo.es, rgm@gnu.org, ken.manheimer@gmail.com, emacs-devel@gnu.org To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 10 14:49:08 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dUY7c-0003rN-ED for ged-emacs-devel@m.gmane.org; Mon, 10 Jul 2017 14:49:05 +0200 Original-Received: from localhost ([::1]:40599 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dUY7h-0001n5-SK for ged-emacs-devel@m.gmane.org; Mon, 10 Jul 2017 08:49:09 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33760) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dUY74-0001mW-UO for emacs-devel@gnu.org; Mon, 10 Jul 2017 08:48:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dUY73-0005ec-Sa for emacs-devel@gnu.org; Mon, 10 Jul 2017 08:48:31 -0400 Original-Received: from cloud103.planethippo.com ([78.129.138.110]:42695) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dUY6y-0005Ek-6h; Mon, 10 Jul 2017 08:48:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=russet.org.uk; s=default; h=Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=P01nT7AubUADccpz4utFR8EYDYDQiqTLQL/G46NwoN0=; b=rkg6G/3hT8uchEsaF5siGOdqo tBA8iUX6fiwHqb/y3An9/Wm/KWnoN1SPDLDB80nQkOsThuFFZS+NvYcrqo6d0mzIJPA+yZ1cvFV9J xsf79/v05RV06h0V7qWCgk+33gzlzo2M38GpZEKkl8z8LjFSyUmn2Yrl0dnJKJlv105lDfzbCGjqE YbSQD0mK4i7TqHIkzYx9e0QvKYiMW2WNCdPCm3jAi7fwiaSqDhxXBNdpyjgC1MlmZPP4/lwORt55Y VQ43N9KEaPTOyxEUDyA840pN9ziEjiJEgibPvSqHg5U9DjUwd33jDOorCjGO26daR9vZP5FVLmk0P itmLU4mrQ==; Original-Received: from janus-nat-128-240-225-75.ncl.ac.uk ([128.240.225.75]:40921 helo=russet.org.uk) by cloud103.planethippo.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1dUY6H-001DHF-GQ; Mon, 10 Jul 2017 12:47:41 +0000 In-Reply-To: (Richard Stallman's message of "Mon, 10 Jul 2017 05:26:30 -0400") X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cloud103.planethippo.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - russet.org.uk X-Get-Message-Sender-Via: cloud103.planethippo.com: authenticated_id: phillip.lord@russet.org.uk X-Authenticated-Sender: cloud103.planethippo.com: phillip.lord@russet.org.uk X-Source: X-Source-Args: X-Source-Dir: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 78.129.138.110 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:216406 Archived-At: Richard Stallman writes: > [[[ To any NSA and FBI agents reading my email: please consider ]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > > 1) Get list of all contributors > > 2) Email them all, recording the date > > 3) Email those who respond instructions > > 4) Email assign@fsf to find out current status > > 5) Email those who havent again > > 6) Reply to people who say "haven't heard anything" > > 7) Repeat some variation of 4,5, and 6 > > > 8) Work out how many are left > > 9) Once n < 3 or 4 check how big their contributions are > > 10) Write them out > > Step 4 is due to FSF procedures, so I will try to change them to > eliminate it. I hope the clerk will directly notify the person > managing this process when each package contributor's papers arrive. That will be an excellent addition. Also, it would be good to know when the FSF forms have gone to the contributor -- assuming assignment is still a two step process. The reason for this is that people will say "sent it off, not heard anything back yet". I don't know how long the assignment process spends at the FSF end; this could all be postage. > The rest, however, has nothing to do with how the FSF operates. At > least, not that I can see. It is rather the nature of persuading many > individuals to do something, independent of what the something is. > > Do you have any suggestions for how to simplify parts other than step > 4? Having a way to track emails going out on a specific topic would be helpful; this would make it easier to track when you last emailed some one about assignment. > Step 8 is easy if you make a list of all the contributors, one per > line, and add a * once a contributors's papers are done. I think that > will be faster and easier than using RT to keep track of them. I used org-mode to achieve this, and yes it does help. If we wish to turn this into a bit more of a factory, though, we might have a contributor who contributes to more than one package, so getting a single set of papers might have implications for more than one project. This is where some sort of tracker might help. Still, it's a smaller issue than notifications. > We don't have to wait till there are only 4 nonsigning contributors to > start steps 9 and 10. It would be feasible to do with 10 or 20 or 50 > contributors left out, if their code is small. Thus, I suggest > identifying after a few months those whose code is not too hard to > replace. Actually, I do this at the beginning. Not all contributors actually have code in the current version, so it's good to know this from the start. For dash, I just asked everybody, though, on the basis that if they had code in before, they might do in the future. Phil