From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Sync up the org in emacs master to org maint branch? Date: Thu, 02 Feb 2017 09:57:36 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87inosr673.fsf@flea> References: <87k29d7zvw.fsf@engster.org> <87fuk08i01.fsf@engster.org> <87d1f36xnc.fsf@engster.org> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1486051347 25711 195.159.176.226 (2 Feb 2017 16:02:27 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 2 Feb 2017 16:02:27 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 02 17:02:18 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 1cZJpx-0006Mm-N5 for ged-emacs-devel@m.gmane.org; Thu, 02 Feb 2017 17:02:17 +0100 Original-Received: from localhost ([::1]:57471 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZJq3-0004AS-5F for ged-emacs-devel@m.gmane.org; Thu, 02 Feb 2017 11:02:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40999) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZIpZ-0001P1-PM for emacs-devel@gnu.org; Thu, 02 Feb 2017 09:57:53 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZIpV-00076N-Hw for emacs-devel@gnu.org; Thu, 02 Feb 2017 09:57:49 -0500 Original-Received: from [195.159.176.226] (port=58860 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cZIpV-00075r-CQ for emacs-devel@gnu.org; Thu, 02 Feb 2017 09:57:45 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cZIpN-0005Wb-Vx for emacs-devel@gnu.org; Thu, 02 Feb 2017 15:57:37 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 28 Original-X-Complaints-To: usenet@blaine.gmane.org X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never Cancel-Lock: sha1:I8xrR6JUImCJJICHJ0OwBxguH6g= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 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:211877 Archived-At: On Thu, 02 Feb 2017 09:09:54 -0500 John Wiegley wrote: >>>>>> "LI" == Lars Ingebrigtsen writes: LI> If Django had traditionally always been distributed along with Python, and LI> maintained in the Python repo, and the suggestion now would be to move LI> Django to a part of the Python repo that very few developers look at, but LI> Django would continue to be distributed with Python, and all Django bug LI> reports would continue to go to the Python bug repository, and Python LI> developers would continue to be responsible for QA and bug fixing of LI> Django. JW> OK, to continue the analogy, what is the right answer? Technically it doesn't JW> seem as though Django belongs there, even if culturally it sounds hard to JW> separate. Should it stay indefinitely, or should the development model change? Packages which require tight integration with the core should stay. Technically, I think at least these factors matter: * high degree of overlap in developer community * high degree of overlap in user community * high degree of internal coupling with core, especially on new features * many components and libraries shared with core * bug reports against the package often are actually against the core, or require core changes to be resolved I think Gnus matches those. Ted