Re: Representing Debian Metadata in Git

From: Chris Hofstaedtler <zeha@debian.org>
Date: Aug 21, 2024, 23:51 UTC
Message-ID: <z574b3k5mld3oshnlwho5jlpvgagkra6p2kmy2fe6urfhvtjeq@fivivkehco4o>
In-Reply-To: <029801daf41f$7e994b70$7bcbe250$@nexbridge.com>

* rsbecker@nexbridge.com <rsbecker@nexbridge.com> [240822 01:21]:

Show 9 quoted lines

> >> Any feelings/objections/missed requirements?
> >
> >In the current DEP14/DEP18 discussions a lot of discussion was had about how we
> >should represent Debian things in git; your mail also goes into this direction.
> >
> >My *feeling* is we should do the opposite - that is, represent less Debian stuff in git,
> >and especially do it in less Debian-specific ways. IOW, no git extensions, no setup
> >with multiple branches that contain more or less unrelated things, etc.
>[..]

> On the other side (perhaps), git is increasingly being used in the Ops setting for
> DevOps and DevSecOps. Production configurations for high-value applications are
> moving to storing those configurations into git for tracing and audit. Git is an
> enabler for good production operations practices.

Don't get me wrong. Yes, we should use git to do what git is good for (tracking changes, etc).

We should not invent new ways of using git that no one else uses. I'd like to reduce the delta of "how Debian uses git" to "how everyone else uses git" to, hopefully, zero.

Chris