From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: Moving http://zsh.sourceforge.io/ to https://www.zsh.org/
Date: Sat, 12 Feb 2022 13:22:02 +0000 [thread overview]
Message-ID: <50221ca5-6cfd-483d-a74b-3528b5b9768f@www.fastmail.com> (raw)
In-Reply-To: <8c94371c-f71c-4042-be95-44ac7f0fa835@www.fastmail.com>
Daniel Shahaf wrote on Tue, 01 Feb 2022 07:40 +00:00:
> I think we have consensus that the Web site should move to zsh.org.
>
> Seems to me like there isn't much work left to do:
>
> 1. Move the list of "Distribution sites" on zsh.org to the "Mirrors"
> page on zsh.sf.io
>
> 2. Update any self-links on zsh.sf.io to say "zsh.org" (e.g., the search box)
>
> 3. Serve the contents of zsh-web.git from the zsh.org webroot
>
> 4. Have zsh.sf.io redirect to zsh.org
>
One more step:
5 (alt 1). Set up SSH accounts for committers who'd like to be able to
deploy updates to the Web site, so they'll be able to deploy by rsync-over-
ssh to zsh.org (rather than to sf.net as today)
OR
5 (alt 2). Set up zsh.org to automatically deploy changes pushed to to zsh-web.git
Without this step, only the handful of people with SSH access will be
able to deploy updates, whereas today all committers can deploy updates.
Cheers,
Daniel
> Step #3 is the only one that requires special privileges. Anyone wants
> to jump in and make patches for the first two steps?
>
> % git clone https://git.code.sf.net/p/zsh/web zsh-web.git
>
> Cheers,
>
> Daniel
prev parent reply other threads:[~2022-02-12 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 7:40 Daniel Shahaf
2022-02-02 0:49 ` Bart Schaefer
2022-02-02 18:28 ` Daniel Shahaf
2022-02-12 13:22 ` Daniel Shahaf [this message]
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=50221ca5-6cfd-483d-a74b-3528b5b9768f@www.fastmail.com \
--to=d.s@daniel.shahaf.name \
--cc=zsh-workers@zsh.org \
/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 public inbox
https://git.vuxu.org/mirror/zsh/
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).