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: Sat, 08 Jul 2017 21:52:15 +0100 Message-ID: <87o9su8xds.fsf@russet.org.uk> References: <8737aac0rb.fsf@wanadoo.es> <7s37aapc4g.fsf@fencepost.gnu.org> <87fue7c32j.fsf@russet.org.uk> <83r2xrl8kp.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1499547192 24487 195.159.176.226 (8 Jul 2017 20:53:12 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 8 Jul 2017 20:53:12 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2.50 (gnu/linux) Cc: ofv@wanadoo.es, rgm@gnu.org, eliz@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 Sat Jul 08 22:53:07 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 1dTwir-0005nY-7U for ged-emacs-devel@m.gmane.org; Sat, 08 Jul 2017 22:53:01 +0200 Original-Received: from localhost ([::1]:34028 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dTwiw-0007GO-Mz for ged-emacs-devel@m.gmane.org; Sat, 08 Jul 2017 16:53:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60013) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dTwiI-0007GJ-PQ for emacs-devel@gnu.org; Sat, 08 Jul 2017 16:52:27 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dTwiH-0002ic-U7 for emacs-devel@gnu.org; Sat, 08 Jul 2017 16:52:26 -0400 Original-Received: from cloud103.planethippo.com ([78.129.138.110]:41454) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dTwiA-0002hC-Ss; Sat, 08 Jul 2017 16:52:19 -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=w9PaKEsBtRW5LoKcO79XZymjHYooD5mtHhqiC+ibVco=; b=mVxCSmqV/Kz4/rA3IpB6L4T+5 9yeKYqWS1rNKGDmqjd0kpCUwxwezEBk8zx3+ClZ0lWMAC2Pk7YPIoxjzSwY1rEqUKNduFTTrP2Wm6 NkfwQcC2kWrfN5nx1Ve+p6iSLTXVpdd79tLGx/wKShA7LfAVhk6erSU1AsbyljiCimpVH5dmJRrIT M4lb7zeK7bEfCTVblDQyah9b/LHH17+HSVLaeeWPb/sfBp6P9Y6orF1O5y509iMe4IP9JZcFWTYJR IVdWldSfLZlEPFrECcAPMZqzHcrkg14nqrO7trWlL4FPXM3JB1Oh52XqPV0B3BLCuPODne5dj8yYr KzVjfp8JA==; Original-Received: from cpc8-benw10-2-0-cust100.16-2.cable.virginm.net ([92.233.204.101]:55322 helo=russet.org.uk) by cloud103.planethippo.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from ) id 1dTwi9-00060R-Gr; Sat, 08 Jul 2017 20:52:17 +0000 In-Reply-To: (Richard Stallman's message of "Sat, 08 Jul 2017 13:04:11 -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:216339 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. ]]] > > > No this is no good. If I am going to do this, I want notifications -- push > > not pull. So, there needs to be a way to open this up beyond maintainers. > > I am working on getting this set up. Good. From what Stefan says, if there is already a ticket system involved in copyright assignment, this might be as simple as enabling a non-maintainer to start a ticket when they email someone a request. > > Having a system to maintain links to the package we are trying to get > > assignment for would be good. > > I am not sure what that means -- could you say it more concretely? Yes. The copyright assignment process says "I assign copyright for Emacs"; obviously this makes sense, but if someone is doing this so that we can get magit into Emacs or ELPA, then we need to know that also, so we can work out when a new assignment happens which package (i.e. magit) it has implications for. > > Having something which handles something like blocking would be nice also. > > i.e. we start a bug wrt to magit for assignment, then all the assignment > > requests would be blockers. Then we would know when we are finished. > > How would this be more convenient > than putting a list of the contributors in a file > and making a note when each one comes in? Say we have 200 contributors for magit, and 500 people with copyright assignment for Emacs. New assignment comes in for Emacs, I now have to check 200 magit contributors to see whether its one of them. To do magit, we also need to do 5 dependencies, so we need to check against those lists as well. It's scaling something like quadratically. It's also worth remembering here: copyright assignment works based on peoples names, while the list of contributors for magit that I have is based on their github names, or the email(s) that they used for their git commits. So making sure that any data that is stored, also includes peoples aliases. To re-iterate, this is just my ideas based on my last experience; it's going to take several attempts and refinements to get the process working well. Phil