From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Theodor Thornhill Newsgroups: gmane.emacs.devel Subject: Re: Gitlab Migration Date: Fri, 27 Aug 2021 23:04:55 +0200 Message-ID: References: <87h7fcnmq0.fsf@posteo.net> <83tujbqg4j.fsf@gnu.org> <874kbbosht.fsf@gnus.org> <8335qur9h7.fsf@gnu.org> <831r6er6rz.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35947"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, larsi@gnus.org, monnier@iro.umontreal.ca, danflscr@gmail.com, philipk@posteo.net, sir@cmpwn.com To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 27 23:06:03 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mJj33-00090B-OM for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Aug 2021 23:06:03 +0200 Original-Received: from localhost ([::1]:40310 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJj31-0005mz-TY for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Aug 2021 17:05:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59256) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJj2A-00055k-8a for emacs-devel@gnu.org; Fri, 27 Aug 2021 17:05:06 -0400 Original-Received: from out2.migadu.com ([2001:41d0:2:aacc::]:50312) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJj26-0002IJ-45; Fri, 27 Aug 2021 17:05:06 -0400 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=key1; t=1630098297; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rKoNCi4SZJyjtzO6/QEJFuHfYAiVZo7XtEHHzJ1lc2k=; b=iiLbDswBDsOqz7LQxMH/XLapOXJMUCOsn/687FkcCb5+yb7iRyI5vdowbLt2i0H/t3nrlK sjEuPcZqNA8roR/mFmmATutBlo/MWWe72xTxLWk4OZ0H+bg2L8iSuSb3qap31LCK+p3AOb eHCwTVnlPg2fPams4nHy27rYf4RZBK4JQhwzRso6dHCOQHBqNTio0bp2VZ9Priovv8IBxW mML0+jk/5NDtvkR+0aZIMGXxRak5B3wvk54yqymTNlXusIck89V9uoSH6VQy0V7Jw4zTie uc+WTHD3wtQ952V0/I+GHzNRlOI5v6jqA453oEN9PcOKhFL9c/ar4Y0Z47+WhQ== In-Reply-To: <831r6er6rz.fsf@gnu.org> X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: theo@thornhill.no Received-SPF: pass client-ip=2001:41d0:2:aacc::; envelope-from=theo@thornhill.no; helo=out2.migadu.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:273182 Archived-At: Eli Zaretskii writes: [...] > > Would it be possible to have a more detailed review, like short > description of what is available for each of the requirements in the > GitLab issue? That should give us a good idea of how close we are to > the goal. > Sure, I can try. At the minimum, it can serve as a starting point from which Drew can correct all my mistakes when he chimes in. Firstly, I'll say that it in general offers a similar workflow to what emacs developers already use. It also has an explicit goal of not being too GitHub/GitLab-like, where pull requests are the default way to contribute. However, there are some key differences. You don't need a user account to use it, though that gives you some benefits like cloning repos etc. It is and always will be (I think) emailbased rather than forms on the web. That means using `git am` and friends to push and pull the code. About payment - all users should be able to report bugs when it hits beta. The paid features is for the cloning and personal repo hosting, I think. Also not sure if this applies when sourcehut is self hosted. As for the specific points in the gitlab issue, let me make an effort: * Email workflow This is a given. Patches and discussions are all first class citizens, meaning that it is all backed by email. You can open, close, adjust and respond to issues using email. ** Submitting patches by email. It is possible to send patches using a web interface. It works by using the `prepare a patchset` button on your own clone. So the process is usually: - clone the repo - pull it locally - do the work - push the work - use the `prepare a patchset` button or `git format-patch` It is then sent to the respective mailing list ** Offline review An issue (if not already subscribed to all) can be subscribed to your own email and be sent to you. The whole thing or parts of it can be downloaded as an mbox. ** Reviewing by email You can use inline comments [1] ** Merge request creation Honestly I don't really understand this one... * Code should be accompanied by documentation This seems trivial, and can be done using the CI on patch submission running a job, if I understand that point correctly? * Formatting code commits Same as above * Diff mailing list This I don't know * Traceability of Merge Requests There is at least a basic web search available on the web client for this, but seeing how the only repo I maintain with actual contributors I maintain is on GitHub I don't have much first hand experience here. * Continuous integration This is one of sourcehuts strong points, as I see it. Jobs can be run on patch submission and on commits, and is also inspectable through ssh should something break. Arbitrary stuff can be done here. * Closely integrated bugtracker automated tasks for patch application and status updates exist here ... There seems to be some more points here that could be covered by CI, so I'll jump a little ... * Licensing No js is needed Captcha is not used GNU criteria for ethics I cannot say anything about. Though it would surprise me if it didn't score well. * Integration with savannah I can't say anything about this * Integration with debbugs Seeing how both use mbox this should be trivial to do * Bug reporting `report-emacs-bug` can still be used, as well as clicking in the web ui. This is where I'm not sure about not using email. I think you still need to mail the bug, opened by a mailto: I hope this helps a little. -- Theodor [1]: https://lists.sr.ht/~technomancy/fennel/patches/24386