ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Carlos via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Carlos <linguafalsa@gmail.com>
Subject: Re: [NTG-context] Software upgrade for ntg and contextgarden server 6 April
Date: Sun, 16 Apr 2023 09:54:41 -0400	[thread overview]
Message-ID: <segibkz5y6bqa4hbxhni7wnww6i3bjvpziympeufhbtyqe5l4z@6nxppwnmiplj> (raw)
In-Reply-To: <979f4aaa-c488-06b8-df74-9fd0914248a4@xs4all.nl>

On Sat, Apr 15, 2023 at 10:57:15AM +0200, Hans Hagen via ntg-context wrote:
> On 4/15/2023 3:23 AM, Carlos via ntg-context wrote:
> 
> > thank you Taco, Hans, and Aditya, Mikael, et
> > 
> > Hans, I was just curious about your git strategy and wanted to ask you about something.
> 
> I have no strategy. I see it as just an offline repository and archive.

It's a strategy. It may not be the fanciest  but you wrote earlier:

>it's sort of the original git archive and our backup plan.                    
>                                                                                              
>  https://github.com/contextgarden/context 

‹backup plan› has the same meaning there than a master plan (no pun
intended with git) hence the association with a strategy. 

But when I wrote ‹strategy› it was not written with the intention
to convey a message of exhaustive calculations to get or divise the
plan of plans.  NO. Rather more like what the definition says about it

a plan of action or policy designed to achieve a major or overall aim.

what is the backup plan of git as an archive but just a backup
strategy. 
> 
> The luametatex repos sort of resembles what I have on my machine but even
> then I always use intermediate 'compare before merge' steps that predate
> git. Git (or svn) is nice for seeing changes but I admit that I never
> roll-back using git. When I have to integrate something in e.g. luametatex
> that comes from git I always diff (winmerge) and "manually merge". So much
> for stragety: not that fancy.

I agree 
> 
> The context updates are assembled from a completely different dev structure
> (think also of temporary files, runtime files for manuals etc that don't
> belong in something git) and turning that modus operandi into something git
> would make my way of doing things pretty inefficient, so unless very little
> changes etc happen i won't change that.
> 

But it's good for the memory Hans. It's good for us. Studies on humans
have revealed that learning or adapting  to new methods might prove
beneficial in the long run.

> All the git magic is maintained by Mojca and occassionally we discuss how to
> move on (we have some pending install-from-git stuff but that might take a
> while before being promoted).

> 
> I'm not really interested in al the additional stuff like chats, pull
> requests, keeping track of comments in git, all these (for me useless)
> statistics. I don't want to end up in an endless 'check this or that' noose,
> so for me email and communicating (could be visual) with some involved does
> it well; more fun too.

I agree with you there. But who said anything about messages, chats, and
the interactive social gitclub as gitlab, github and its ilk have
suddenly become part of 

> 
> For some other projects git(hub|lab) is a communication method, basically an
> on-line storage.
> 
> > Did you guys ever consider having a cgit interface and hosting it.
> > 
> > A bunch of projects have done it
> > 
> > heck. Even git, which is where everything solely depends on in the end, is running it.
> > 
> > https://git.kernel.org/pub/scm/git/git.git/
> > 
> > https://git.zx2c4.com/cgit/about/
> There is not much to gain with adding yet another interface to what we have
> now. It only works if one or more people commit (no git pun intended)
> themselves long-term to it which relates to ie beging used.
> 

It's just an interface much more simpler than what the git archive
backup interface currently in use presumably undergoes. Git is sort
of big as-is and that's not even counting all its remote helpers
by which all those places depend on (gitlab, github, bitbucket),
which makes it even bigger. 

I've just seen that interface in a few projects and thought it was nice
that the devs have somehow implemented it. 



> (Keep in mind that it's all volunteer work.)
> 
> Hans
> 
> 
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : https://contextgarden.net
> ___________________________________________________________________________________
> 

-- 
You can be replaced by this computer.

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-04-16 13:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 11:25 Taco Hoekwater via ntg-context
2023-04-06 16:20 ` Taco Hoekwater via ntg-context
2023-04-11 20:42   ` Taco Hoekwater via ntg-context
2023-04-11 21:07     ` Hans Hagen via ntg-context
2023-04-12  7:36     ` Werner Hennrich via ntg-context
2023-04-12 13:29     ` [NTG-context] " Willi Egger via ntg-context
2023-04-14 13:50     ` mf via ntg-context
2023-04-14 22:13       ` Hans Hagen via ntg-context
2023-04-15  1:23         ` Carlos via ntg-context
2023-04-15  8:57           ` Hans Hagen via ntg-context
2023-04-16 13:54             ` Carlos via ntg-context [this message]
2023-04-16 15:09               ` Hans Hagen via ntg-context

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=segibkz5y6bqa4hbxhni7wnww6i3bjvpziympeufhbtyqe5l4z@6nxppwnmiplj \
    --to=ntg-context@ntg.nl \
    --cc=linguafalsa@gmail.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).