From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Wiegley Subject: Re: Sync up the org in emacs master to org maint branch? Date: Thu, 02 Feb 2017 09:09:54 -0500 Message-ID: References: <87k29d7zvw.fsf@engster.org> <87fuk08i01.fsf@engster.org> <87d1f36xnc.fsf@engster.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: (Lars Ingebrigtsen's message of "Thu, 02 Feb 2017 13:10:07 +0100") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sender: "Emacs-devel" To: Lars Ingebrigtsen Cc: David Engster , Emacs developers , Bastien Guerry , emacs-org list , Kaushal Modi , Phillip Lord List-Id: emacs-orgmode.gnu.org >>>>> "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. OK, to continue the analogy, what is the right answer? Technically it doesn't seem as though Django belongs there, even if culturally it sounds hard to separate. Should it stay indefinitely, or should the development model change? -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2