From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/10839 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: musl new-year's infrastructure resolutions Date: Sat, 31 Dec 2016 18:37:47 -0500 Message-ID: <20161231233747.GV1555@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1483227488 21031 195.159.176.226 (31 Dec 2016 23:38:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 31 Dec 2016 23:38:08 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-10852-gllmg-musl=m.gmane.org@lists.openwall.com Sun Jan 01 00:38:04 2017 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1cNTDu-0004aY-4u for gllmg-musl@m.gmane.org; Sun, 01 Jan 2017 00:38:02 +0100 Original-Received: (qmail 3334 invoked by uid 550); 31 Dec 2016 23:38:01 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 3299 invoked from network); 31 Dec 2016 23:38:00 -0000 Content-Disposition: inline Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:10839 Archived-At: 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.