Re: Is Dillo development still active?

Andreas Kemnade <[email protected]>
Newsgroups gmane.comp.web.dillo.devel
Message-ID <20211129195712.5db154f8@aktux>
Hi,

On Mon, 29 Nov 2021 07:30:01 -0500
John DiMarco <[email protected]> wrote:

> In message <20211128211824.7c4afab8@aktux>you write:
> >On Sun, 28 Nov 2021 11:19:33 -0500
> >John DiMarco <[email protected]> wrote:
> >  
> >> I'm not sure there is anyone minding the store re: dillo.org and the
> >> mercurial repo, at least based on what I saw in May. Perhaps we should
> >> work with your git fork instead?
> >>   
> >
> >generally it is a good idea. Since there is no development here, I
> >would think that I could shut down the mercurial repo. There are enough
> >places to set up a git repo and you can have repos at several place if
> >you do not want to be dependant on one service.  
> 
> Could leave it up (to retain the snapshotted state of the code plus its
> history) but mark it as inactive, and point people to an active git repo
> instead. I don't know if we want multiple repos: if we can manage one
> where active development is occuring, that'd be a good accomplishment.
> 
yes, one public repo is good, but if github becomes somehow evil, it is
easy to move to something else.

marking the hg repo somehow as inactive: Well, technically I could
change contents of dillo.org, but I hesitate there, I am not a
maintainer, so I rather would shut down the stuff with some warning
before. It just does not make sense anymore so much.
I cannot change the dns entry of dillo.org to have some redirect to
something. I am not aware that anybody else than Jorge has access to
dillo.org nameserver entries.

I think the github repo contains the full history of the mercurial
repo, so nothing is lost.

Regards,
Andreas

_______________________________________________
Dillo-dev mailing list
[email protected]
http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev
http://www.dillo.org/
You get this email because your address [email protected] is in the
mailing list dillo-dev.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.