From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: [elpa] New package: vc-got Date: Sun, 17 Oct 2021 07:57:42 +0300 Message-ID: References: <87zgsx7v08.fsf@omarpolo.com> <83y28hsqtg.fsf@gnu.org> <83tuj5spdi.fsf@gnu.org> <5f99f3b1-b1b9-20fa-df12-52eed3fedd3a@yandex.ru> <83sfypsp34.fsf@gnu.org> <83r1e9soh8.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8664"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0.7+183 (3d24855) (2021-05-28) Cc: op@omarpolo.com, emacs-devel@gnu.org, timo.myyra@bittivirhe.fi, Dmitry Gutov To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 17 06:59:33 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 1mbyGi-000279-U7 for ged-emacs-devel@m.gmane-mx.org; Sun, 17 Oct 2021 06:59:32 +0200 Original-Received: from localhost ([::1]:48864 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mbyGh-0001Ww-QL for ged-emacs-devel@m.gmane-mx.org; Sun, 17 Oct 2021 00:59:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47394) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mbyFx-0000qr-IO for emacs-devel@gnu.org; Sun, 17 Oct 2021 00:58:45 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:53737) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mbyFq-0003Qv-Tz; Sun, 17 Oct 2021 00:58:45 -0400 Original-Received: from localhost ([::ffff:41.75.191.219]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 0000000000065D9A.00000000616BAD7B.00000CB1; Sat, 16 Oct 2021 21:58:34 -0700 Mail-Followup-To: Eli Zaretskii , Dmitry Gutov , timo.myyra@bittivirhe.fi, op@omarpolo.com, emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: <83r1e9soh8.fsf@gnu.org> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-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:277201 Archived-At: * Eli Zaretskii [2021-08-31 17:06]: > How about keeping it out of vc-handled-backends, so that people who > want could replace Git with Got? Git and Got are different VCS systems. Once can understand its goals by reading the reference: Reference: https://gameoftrees.org/goals.html Project guidelines - Follow OpenBSD's security practices and coding style. - Use a development process based on code review in email. - Consistently use pledge(2) and unveil(2) across the code base. - Use privilege-separation when parsing repository data from network or disk. - Keep the entire code base BSD-licenced. Long-term goals Remain on-disk compatible with bare Git repositories. Don't insist on Git-compatibility beyond this requirement. Provide a complete version control tool suite for OpenBSD. Intuitive command line interface for required version control operations (got). Interactive repository browser for history analysis and review of committed changes (tog). CGI repository browser for web servers (gotweb). Repository administration tooling with a strong focus on backup and recovery (gotadmin). Repository server for hosting a central repository and synchronizing changes to a cascade of public and private mirrors. Consider workflow requirements of OpenBSD developers. Strong built-in support for a centralized repository model (ideas about pull/push). Keep things easy for developers who don't need branches. Support local branches for developers who need them. Support "-stable" release branches. Support features required by the OpenBSD project's build infrastructure. Implement authenticated and encrypted network communications. Provide SSH and optional TLS support for cloning repositories and pulling changes. Exclusively rely on SSH for pushing changes. Do not implement server-side support for plaintext network communications. Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/