public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: killing mediawiki
Date: Wed, 4 Jul 2018 06:00:34 -0700	[thread overview]
Message-ID: <20180704060034.261bdbfa@professor-x> (raw)
In-Reply-To: <20180704192153.3c581352@katipo2.lan>

[-- Attachment #1: Type: text/plain, Size: 1928 bytes --]

On Wed, 4 Jul 2018 19:21:53 +1200
Kent Fredric <kentnl@gentoo.org> wrote:

> On Tue, 3 Jul 2018 12:39:43 -0500
> William Hubbs <williamh@gentoo.org> wrote:
> 
> > I don't care that we have a wiki, but can we please look into
> > killing mediawiki and look at something with a git backend? It
> > would be very nice to be able to edit wiki pages in markdown or
> > another similar format and use git to control the changes instead
> > of editing in a browser.  
> 
> 1. Who are the primary beneficiaries of this suggestion?:
> 
>   a. People with expert knowledge of development systems and people
>      with Gentoo Privileges
>  
>   b. End users who may not be experts, in all things development, but
>      may be able to contribute and consume content.
> 
> 2. What compromises in flexibility does this create? Eg: Do suggested
>    replacements have capacity to have arbitrary HTML and templating?
> Or are they restricted to the terribly narrow featureset of Markdown?
> 
> 
> If you're optimising for 1-a and your choice of compromise results in
> a reduction in functionality with regards to clear, flexible, and
> expressive content, it will be hard to sell me on the idea.
> 

3)  The ability of someone with a sight disability, the actual ability
to contribute to the project.  We as a project should try make our
documentation accessible to as broad an audience as possible.


I know from personal experience and having worked with such a person,
to make it possible to work with cli tools to be able to interact with
normally browser only visual interfaces which are extremely poor to
work with using a screen reader.  At my work, I personally made a github
python library and cli interface for github, and worked to create
templates for a go-jira command line interface so a visually impaired
co-worker could interact with those systems.


-- 
Brian Dolbec <dolsen>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  reply	other threads:[~2018-07-04 13:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 17:39 [gentoo-dev] rfc: killing mediawiki William Hubbs
2018-07-03 17:47 ` Brian Evans
2018-07-03 18:23   ` William Hubbs
2018-07-03 19:20 ` Jonas Stein
2018-07-03 20:01   ` William Hubbs
2018-07-03 20:09     ` M. J. Everitt
2018-07-03 20:31       ` William Hubbs
2018-07-04  2:31 ` Matt Turner
2018-07-04 17:49   ` William Hubbs
2018-07-05  1:23   ` Jonas Stein
2018-07-04  7:21 ` Kent Fredric
2018-07-04 13:00   ` Brian Dolbec [this message]
2018-07-04 17:44   ` William Hubbs
2018-07-05  1:26     ` Kent Fredric
2018-07-05 17:44       ` William Hubbs
2018-07-06  0:25         ` Kent Fredric
2018-07-05  9:08 ` Nils Freydank
2018-07-05 17:32   ` William Hubbs
2018-07-06  0:34     ` Kent Fredric
2018-07-06 16:07       ` William Hubbs
2018-07-06 16:52       ` Ulrich Mueller

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=20180704060034.261bdbfa@professor-x \
    --to=dolsen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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