From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [RFE] Migration to gitlab Date: Wed, 24 Apr 2019 10:06:58 +0300 Message-ID: <83pnpb3mr1.fsf@gnu.org> References: <1552789070.5272.1@yandex.ru> <1552791707.5272.2@yandex.ru> <1552793646.5272.3@yandex.ru> <1552821396.21432.0@yandex.ru> <83imwhwf4x.fsf@gnu.org> <837ecvux2q.fsf@gnu.org> <9c7cf558-a2d3-951e-d6e1-31b3ad5900cf@yandex.ru> <1553064994.13109.0@yandex.ru> <831s32t3fn.fsf@gnu.org> <83pnqkt5ht.fsf@gnu.org> <87lg001kty.fsf@iotcl.com> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="206755"; mail-complaints-to="usenet@blaine.gmane.org" Cc: hi-angel@yandex.ru, theophilusx@gmail.com, emacs-devel@gnu.org, philippe.vaucher@gmail.com, dgutov@yandex.ru, tadeus.prastowo@unitn.it To: Toon Claes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 24 09:12:05 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hJC4a-000rdK-BW for ged-emacs-devel@m.gmane.org; Wed, 24 Apr 2019 09:12:04 +0200 Original-Received: from localhost ([127.0.0.1]:37084 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hJC4Z-0001zW-5N for ged-emacs-devel@m.gmane.org; Wed, 24 Apr 2019 03:12:03 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:43234) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hJC4Q-0001sb-0k for emacs-devel@gnu.org; Wed, 24 Apr 2019 03:11:55 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51761) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hJBzs-0001mq-6b; Wed, 24 Apr 2019 03:07:12 -0400 Original-Received: from [176.228.60.248] (port=2891 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hJBzi-0002hx-Lk; Wed, 24 Apr 2019 03:07:11 -0400 In-reply-to: <87lg001kty.fsf@iotcl.com> (message from Toon Claes on Tue, 23 Apr 2019 23:19:05 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:235847 Archived-At: > From: Toon Claes > Gcc-Self: nnimap+soverin:Sent > Date: Tue, 23 Apr 2019 23:19:05 +0200 > Cc: hi-angel@yandex.ru, theophilusx@gmail.com, emacs-devel@gnu.org, > Philippe Vaucher , dgutov@yandex.ru, > tadeus.prastowo@unitn.it > > > So if someone wants to make this happen, I urge you to come on board, > > get involved in maintenance, collect some real-life experience in > > routine development and maintenance tasks, and then lead the change, > > doing most of the work yourself. And yes, Savannah will most probably > > be a large part of the equation, so you will need their cooperation as > > well. > > TBH, I've tried this. For years I've been following the mailing list, > and I want to get involved in Emacs development. But I've found it hard > to get around in the codebase. Feel free to ask questions and seek guidance here. "Getting involved" doesn't mean you need to discover everything on your own, there are enough knowledgeable and helpful people here who will gladly assist. > I'm not sure, but it might be a chicken-and-egg problem. If the tools > are not convenient *for me* to follow-up bugs, review patches, etc., it > will also not help me familiarize with the codebase and > vice-versa. It is possible that you aren't familiar enough with the existing tools, or haven't set them up optimally. Once again, feel free to describe your difficulties here and ask for advice. It could be that eventually all the advice you get still falls short of what you want/need, but that kind of conclusion should not be made before exhausting the existing capabilities. Familiarity with the existing tools will also provide better perspective on the relative importance of improving/changing specific aspects of our process. > If the Emacs community, and their maintainers, are open to adding > such workflow TBH, I don't think I personally understand what "adding such a workflow" entails. Maybe I just wasn't following the related discussions (sorry), or maybe no one described the workflow in enough detail yet.