all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: op@omarpolo.com, emacs-devel@gnu.org, timo.myyra@bittivirhe.fi,
	Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: [elpa] New package: vc-got
Date: Sun, 17 Oct 2021 07:57:42 +0300	[thread overview]
Message-ID: <YWutRgEiMFXQgxKr@protected.localdomain> (raw)
In-Reply-To: <83r1e9soh8.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [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/



  parent reply	other threads:[~2021-10-17  4:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 10:17 [elpa] New package: vc-got Omar Polo
2021-08-31 13:10 ` Eli Zaretskii
2021-08-31 13:31   ` Dmitry Gutov
2021-08-31 13:41     ` Eli Zaretskii
2021-08-31 13:46       ` Dmitry Gutov
2021-08-31 13:47         ` Eli Zaretskii
2021-08-31 13:55           ` Dmitry Gutov
2021-08-31 14:00             ` Eli Zaretskii
2021-08-31 14:02               ` Dmitry Gutov
2021-08-31 14:07                 ` Eli Zaretskii
2021-08-31 14:08                 ` Eli Zaretskii
2021-08-31 14:21                   ` Stefan Kangas
2021-08-31 15:37                     ` Eli Zaretskii
2021-10-17  4:57               ` Jean Louis [this message]
2021-10-17  6:21                 ` Eli Zaretskii
2021-10-17  7:33                   ` Jean Louis
2021-10-17 10:02                     ` Eli Zaretskii
2021-10-17 10:13                     ` Omar Polo
2021-08-31 14:00     ` Omar Polo
2021-08-31 14:34       ` Dmitry Gutov
2021-08-31 14:38         ` Omar Polo
2021-08-31 15:38       ` Eli Zaretskii
2021-08-31 14:44   ` Dmitry Gutov
2021-08-31 15:40     ` Eli Zaretskii
2021-08-31 13:32 ` Philip Kaludercic
2021-08-31 13:59   ` Omar Polo
2021-08-31 16:54     ` Philip Kaludercic
2021-09-09 15:50     ` Philip Kaludercic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YWutRgEiMFXQgxKr@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=op@omarpolo.com \
    --cc=timo.myyra@bittivirhe.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.