public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Julian Seward <sewardj42@gmail.com>
Subject: Hosting www.valgrind.org on sourceware
Date: Wed, 22 Sep 2021 14:15:39 +0200	[thread overview]
Message-ID: <0075c3ee018be22b506fc0469b0cf07f2c7150f9.camel@klomp.org> (raw)

Hi Sourceware Overseers,

Would it be possible to host https://www.valgrind.org/ on sourceware?
valgrind already uses the sourceware git infrastructure and publishes
releases on sourceware.

Currently the website is maintained in a remote svn repository with
only a few developers having access to update it. We would like to move
that repository to git on sourceware so that any valgrind developer can
update the website. Since the files are already on sourceware it would
be convenient if sourceware could also host the website itself.

The website is mainly plain (html/image) files with a few php files for
the header, footer and side-menu. But we could rewrite those if that
would be an issue.

Would it be OK for me to set this up? I can create the valgrind-
htdoc.git and hooks myself. Julian can update DNS to make valgrind.org
and www.valgrind.org a CNAME for sourceware.org. I might need some help
with apache vhost and the Let's Encrypt for https setup.

Thanks,

Mark

             reply	other threads:[~2021-09-22 12:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 12:15 Mark Wielaard [this message]
2021-09-22 12:27 ` Frank Ch. Eigler
2021-10-17 13:28   ` Mark Wielaard
2021-10-17 14:33     ` Frank Ch. Eigler
2021-10-17 19:30       ` Christopher Faylor

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=0075c3ee018be22b506fc0469b0cf07f2c7150f9.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=overseers@sourceware.org \
    --cc=sewardj42@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 read-only IMAP folder(s) and NNTP newsgroup(s).