public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: Re: Choice of distribution for new sourceware.org server?
Date: Thu, 06 Feb 2020 16:36:00 -0000	[thread overview]
Message-ID: <89f0e5ec-2b85-5ae8-3bed-efc812b2b9e1@redhat.com> (raw)
In-Reply-To: <20200206151900.GA24071@elastic.org>

On 2/6/20 10:19 AM, Frank Ch. Eigler wrote:
> Hi -
> 
>> Awesome. Do you need any help with regular evaluations? Is there a meeting
>> for that? Or is this tactically driven when something can't be upgraded?
> 
> We evaluate when people want to evaluate, as we are doing right now.

Understood.

>> I'm surprised the wiki is non-distro software. I recently setup a dokuwiki
>> backed by git, and it was all distro-software with just configuration data.
> 
> What's a "dokuwiki"?  Yum list doesn't know it.  We use ikiwiki (a
> git-backed wiki system) for one of the wikis on sourceware, and I like
> it a lot.  ikiwiki is not a RHEL product either.

It's in Fedora, I had not checked for availability in RHEL 8 AppStream or EPEL.

dnf search dokuwiki
Last metadata expiration check: 1:36:11 ago on Thu 06 Feb 2020 08:46:10 AM EST.
=========================== Name Exactly Matched: dokuwiki ===========================
dokuwiki.noarch : Standards compliant simple to use wiki
========================== Name & Summary Matched: dokuwiki ==========================
dokuwiki-selinux.noarch : SELinux support for dokuwiki

Dokuwiki is an actively maintained wiki with plugins and good internationalization.
https://www.dokuwiki.org/dokuwiki

ikiwiki doesn't seem as feature rich as dokuwiki, nor does it seem to have as active
a development community, or wide usage? The plugins for dokuwiki are quite useful
and the community has support for git, markdown, captchas, etc.
 
>> Moinmoin is basically dead upstream.
>> Dokuwiki is actively maintained and there are migration paths from moinmoin
>> to dokuwiki.
>> And I would switch to gitolite [...]
> 
> The way that we can make use of ideas like this is for someone to go
> beyond suggest them to actually try things out, consult with the
> respective user base, install, popularize, transition, watch over it
> all, and ideally help shut it down when that time comes.  IOW, there
> is no shortage of other tools we -could- run.  What is short is
> interest & commitment in doing all that work.

Understood.

>> This would also allow us to restrict shell access to only those that
>> ask for it and thus limit our security exposure (best practice).
> 
> Our shell access is already restricted.

Can non-administrators login to the system via ssh? Why?
 
>> [RHEL8 vs CentOS]
> 
> Luckily, we have until 2029 to work through the details either way.

I don't follow. Could you expand on this please?

-- 
Cheers,
Carlos.

  reply	other threads:[~2020-02-06 16:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  1:05 Carlos O'Donell
2020-02-06  1:30 ` Christopher Faylor
2020-02-06  1:34   ` Frank Ch. Eigler
2020-02-06  1:51     ` Carlos O'Donell
2020-02-06  2:02       ` Frank Ch. Eigler
2020-02-06  2:16         ` Carlos O'Donell
2020-02-06 14:49           ` Frank Ch. Eigler
2020-02-06 15:10             ` Carlos O'Donell
2020-02-06 15:19               ` Frank Ch. Eigler
2020-02-06 16:36                 ` Carlos O'Donell [this message]
2020-02-06 16:46                   ` Christopher Faylor
2020-02-06 16:49                   ` Frank Ch. Eigler
2020-02-06  1:45   ` Carlos O'Donell
2020-02-06  6:05     ` Christopher Faylor
2020-02-06 14:50       ` Carlos O'Donell
2020-02-06 15:11         ` Lukas Berk
2020-02-06 15:22           ` Carlos O'Donell
2020-02-06 15:20         ` Christopher Faylor
2020-02-06 17:05           ` Carlos O'Donell
2020-02-06 18:28       ` Joseph Myers

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=89f0e5ec-2b85-5ae8-3bed-efc812b2b9e1@redhat.com \
    --to=carlos@redhat.com \
    --cc=fche@elastic.org \
    --cc=fweimer@redhat.com \
    --cc=overseers@sourceware.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.
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).