From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 0FC153858402 for ; Sun, 28 Nov 2021 21:22:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0FC153858402 Received: from reform (deer0x08.wildebeest.org [172.31.17.138]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 2506230006B1; Sun, 28 Nov 2021 22:22:43 +0100 (CET) Received: by reform (Postfix, from userid 1000) id 6B1A92E80151; Sun, 28 Nov 2021 22:22:43 +0100 (CET) Date: Sun, 28 Nov 2021 22:22:43 +0100 From: Mark Wielaard To: Joel Brobecker Cc: Pedro Alves , Overseers mailing list , simon.marchi@polymtl.ca, eliz@gnu.org, Mike Frysinger Subject: Re: setting up sim project web space Message-ID: References: <6a72ecd6-1480-1cb8-c223-c6c9d991be2e@palves.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00, CONTENT_AFTER_HTML, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2021 21:22:48 -0000 Hi Joel, On Thu, Nov 25, 2021 at 06:00:47AM +0400, Joel Brobecker wrote: > > For savannah you are unfortunately stuck with CVS for webpages. But you > > can just install a redirect to https://sourceware.org/gdb/ so you don't > > need to keep mirroring it in two places. > > Sounds like an interesting idea. > > One of the things I'm concerned about is perhaps people having > bookmarks of old pages. Or perhaps have every one of the current > pages be a redirect to the corresponding page? > > Something like this? > > > > > Redirecting to > > > >

Redirecting to sourceware.org

> > That should work for html pages. It is what e.g. gnutls uses. They keep the page itself in place (so if there is any delay in the redirection the user at least sees the old contents), and they just add the meta http-equiv tag right after the head tag with a content="0; (to make the redirect instantanious). This requires a little scripting to update all pages (let me know if you can use help with that). Alternatively (this is what e.g. guix uses) you can request an .htaccess file be installed that does the redirects. You can contact webmasters@gnu.org for that. > > > - One is hosted on sourceware.org > > > CVS/Root: sourceware.org:/cvs/gdb > > > CVS/Repository: htdocs > > > > > > This repository is the source of the copy on sourceware.org: > > > https://www.sourceware.org/gdb/ > > > > > > I don't know why we have two copies of the website, unfortunately. > > > > > > It would be nice if we could transition the sources to Git. > > > I haven't done it, because I don't know how the automatic-update-after-push > > > is set up, so I'm concerned about breaking the website update if I do. > > > > Sadly my knowledge of CVS is fairly minimal at this point, so I don't > > really understand fully how it is setup now. But I can see that it > > involves getting a checkout under > > /sourceware/www/sourceware/htdocs/gdb/ > > I can convert the CVS repo to git and then setup the git hooks to do > > the same. > > Combined with the redirect, I think this would be great. OK, if you can look into the the redirect I can look into converting the cvs repo to git and setup the automatic website updating. > > That does leave the question of who should be in the gdb group (and is > > allowed to push) and how the onlinedocs are updated, those under: > > https://sourceware.org/gdb/current/onlinedocs/ > > Which seems to be done by some script and you need to be in the > > "shared" group to be able to put files there. > > For the onlinedocs part, it's user "gdbadmin" who does those updates. > It does so nightly via crontab. I found /home/gdbadmin/ss/update-web-docs which seems to be the script responsible. I think this should work as is for the git gdb-htdocs setup just have to adjust the repo/web dir name, which are arguments to how the script is called. To get back to the original request for updating the sim documentation on the website. Can we tweak this script to include sim? I don't see a doc subdir under sim though, so I am not sure how the sim documentation is generated. > For the permissions to push to the new htdocs, I can ask the question > to the GDB Global Maintainers. Perhaps they'll agree that anyone allowed > to push to GDB can also push to GDB's htdocs, particularly if we set the > git-hooks up so as to have commit emails sent to gdb-cvs. I think it would be best/easiest to let everybody in the gdb group able to push commits to gdb-htdocs. If you trust people to commit code, you really should trust them to commit documentation, imho. Speaking of groups. There are actually two, src and gdb. src is used for enabling git commit access, because that group is shared with binutils. I looks like gdb is a proper subset of src. Cheers, Mark