patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Valentin Gagarin <valentin@gagarin.work>
To: Alyssa Ross <hi@alyssa.is>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH] Documentation: remove redundant contributing page
Date: Fri, 10 Jul 2026 17:58:07 +0200	[thread overview]
Message-ID: <10dbb06b-0e8b-4035-b22f-5738cb818522@gagarin.work> (raw)
In-Reply-To: <87o6gf9cex.fsf@alyssa.is>


> I'd prefer to handle the redirects in nginx config if that's okay with
> you, so it's a proper server-side redirect.

The plugin generates a `_site/redirects.json` file that you can already 
feed to the web server.  It's already enough to have to keep track of 
those redirects manually at all.  You shouldn't have another layer of 
manual work on top.

> Are we adopting FileCopyrightText then License-Identifier as the
> official style, then?  I'll do it across the board if so — if it's
> important enough to rearrange, we should be doing it consistently.

I think we should, but we could just do it lazily, when we touch those 
parts.  But if that produces too much diff noise, feel free not to pick 
the reordering and do a separate bulk change.

> 
>> -    <li><a href="contributing.html">Contributing to Spectrum</a>
>> +    <li><a href="doc/contributing/index.html">Contributing to Spectrum</a>
> 
> doc/contributing is nicer, no?

I don't have an opinion there, but if you want that, it should be 
`doc/contributing/` to avoid the permanent redirect on first access.

  reply	other threads:[~2026-07-10 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  8:58 [PATCH] Documentation: remove redundant contributing page Valentin Gagarin
2026-07-10 13:55 ` Alyssa Ross
2026-07-10 15:58   ` Valentin Gagarin [this message]
2026-07-21 15:13     ` Alyssa Ross
2026-07-12 15:08 ` [PATCH v2] " Valentin Gagarin
2026-07-21 15:50   ` Alyssa Ross

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=10dbb06b-0e8b-4035-b22f-5738cb818522@gagarin.work \
    --to=valentin@gagarin.work \
    --cc=devel@spectrum-os.org \
    --cc=hi@alyssa.is \
    /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://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock

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).