From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: musl new-year's infrastructure resolutions
Date: Sat, 31 Dec 2016 18:37:47 -0500 [thread overview]
Message-ID: <20161231233747.GV1555@brightrain.aerifal.cx> (raw)
Here are some things I've really been wanting to get done for a while,
that I/we should try to make happen in the coming months:
Switching over wiki. The current wiki is essentially unmaintained.
Kylie McClain (Somasis) has setup a clone of the content on a new
git-based wiki that looks good. I still want to understand the
intended workflow for getting changes published, but it's got to be
better than the status quo where account creation doesn't even work.
Adopting an issue tracker. This requires actually selecting one and
setting up the infrastructure for it. The wiki could possibly be moved
to the same infrastructure. (I want to keep webapp-ish stuff like
wiki, issue tracker etc. off the server that hosts git and release
downloads because anything interactive is a significant attack
surface that puts integrity of code as risk.)
Enabling git-over-https. This may require switching to a more-capable
httpd or other infrastructure changes on the server.
Website redesign and move to musl.libc.org. I don't have any concrete
ideas for this yet, but I don't think the current website is at all in
line with musl's maturity, current adoption/deployment, etc.
Documentation. Existing manual should probably become a public git
repo that contributors can submit patches/PRs for. Putting together
lists of (1) what's outdated in the current one, and (2) what new
content would be most valuable, might be a good place to start and one
that could benefit from community involvement.
next reply other threads:[~2016-12-31 23:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 23:37 Rich Felker [this message]
2017-01-01 22:37 ` A. Wilcox
2017-01-02 2:31 ` Rich Felker
2017-01-02 2:33 ` Rich Felker
2017-01-02 5:32 ` A. Wilcox
2017-01-02 5:40 ` Rich Felker
2017-01-02 6:39 ` Khem Raj
2017-01-02 16:58 ` Rich Felker
2017-01-02 18:11 ` Alexander Monakov
2017-01-02 18:23 ` Rich Felker
2017-01-02 18:15 ` Solar Designer
2017-01-02 18:25 ` Rich Felker
2017-01-02 18:27 ` Kurt H Maier
2017-01-02 18:36 ` Rich Felker
2017-01-02 18:52 ` Kurt H Maier
2017-01-02 19:16 ` Rich Felker
2017-01-02 20:06 ` Kurt H Maier
2017-01-02 22:59 ` A. Wilcox
2017-01-02 23:09 ` Kurt H Maier
2017-01-02 19:10 ` Matias A. Fonzo
2017-01-02 19:18 ` Rich Felker
2017-01-02 19:28 ` Matias A. Fonzo
2017-01-03 1:20 ` Laurent Bercot
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=20161231233747.GV1555@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).