All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <dominick.grift@defensec.nl>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: SElinux list <selinux@vger.kernel.org>
Subject: Re: selinux userspace wiki
Date: Fri, 06 Jun 2025 22:09:44 +0200	[thread overview]
Message-ID: <87zfeky6lz.fsf@defensec.nl> (raw)
In-Reply-To: <CAEjxPJ5PHAU-_ru9=zN_iuvLGEGDxL_T50-fW4XecnZ6p2ww8A@mail.gmail.com> (Stephen Smalley's message of "Fri, 6 Jun 2025 15:39:21 -0400")

Stephen Smalley <stephen.smalley.work@gmail.com> writes:

> On Thu, Jun 5, 2025 at 3:05 PM Stephen Smalley
> <stephen.smalley.work@gmail.com> wrote:
>>
>> On Thu, Jun 5, 2025 at 3:03 PM Stephen Smalley
>> <stephen.smalley.work@gmail.com> wrote:
>> >
>> > Since I created a Getting Started guide under the selinux-kernel wiki
>> > [1], I also did some refreshing of the selinux userspace wiki [2],
>> > moved the Presentations and Papers sections from the kernel wiki to
>> > the latter, and cross-linked them for easy discovery. However, I had a
>> > few questions about the selinux userspace wiki:
>> >
>> > 1. The Home page and the Userspace Packages page are at least partly
>> > redundant in their content, and the actual list of userspace packages
>> > modified for SELinux was very out of date (I added a note to that
>> > effect and how to query for a more current/accurate set). Should we
>> > drop one or the other or somehow combine them?
>> >
>> > 2. The Tools page is likewise quite out of date. Do we want to refresh
>> > it (and if so, does anyone want to do so), or drop it?
>>
>> Sorry, forgot to include the links:
>>
>> [1] https://github.com/selinuxproject/selinux-kernel/wiki
>> [2] https://github.com/SELinuxProject/selinux/wiki
>
> I refreshed the Tools page, deleted the custom sidebar that was
> (presumably unintentionally) hiding several child pages, and moved the
> Other Resources section to its own sub-page,
> https://github.com/SELinuxProject/selinux/wiki/Other-Resources
> and made further additions to the Presentations and Papers sub-page,
> https://github.com/SELinuxProject/selinux/wiki/Presentations-and-Papers
>
> Feel free to suggest others that should be added or if you are a
> maintainer, to add them yourself.
>
> Another question about the old content: the Contributing page lists an
> IRC channel. Is it still correct and used by maintainers? If not,
> should remove or update appropriately.
>

Yes #selinux on libera.chat is still correct and used by maintainers.

-- 
gpg --locate-keys dominick.grift@defensec.nl (wkd)
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6  E0FF DA7E 521F 10F6 4098
Dominick Grift
Mastodon: @kcinimod@defensec.nl

  reply	other threads:[~2025-06-06 20:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 19:03 selinux userspace wiki Stephen Smalley
2025-06-05 19:05 ` Stephen Smalley
2025-06-06 19:39   ` Stephen Smalley
2025-06-06 20:09     ` Dominick Grift [this message]
2025-06-07  2:13       ` Paul Moore
2025-06-07  7:08         ` Dominick Grift
2025-06-20 18:48           ` Stephen Smalley

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=87zfeky6lz.fsf@defensec.nl \
    --to=dominick.grift@defensec.nl \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.