From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/10847 Path: news.gmane.org!.POSTED!not-for-mail From: Khem Raj Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl new-year's infrastructure resolutions Date: Mon, 02 Jan 2017 06:39:37 +0000 Message-ID: References: <20161231233747.GV1555@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113cfa70627baf054516d141 X-Trace: blaine.gmane.org 1483339208 6585 195.159.176.226 (2 Jan 2017 06:40:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 2 Jan 2017 06:40:08 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-10860-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jan 02 07:40:02 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 1cNwHm-0000YU-Q6 for gllmg-musl@m.gmane.org; Mon, 02 Jan 2017 07:39:58 +0100 Original-Received: (qmail 11745 invoked by uid 550); 2 Jan 2017 06:40: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 11726 invoked from network); 2 Jan 2017 06:40:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ooS7To+A8Q4tHmFlk/8h3rmd3r3gi+TonoEx7cbfiOo=; b=TypgjRoQHzp6ZTl/5BAIRKgpJd7ZPdBRZUSZtvOw1kCn3km9a4JYqMyD2zfjoV92fz KjW2cNs86TEZNTKL3VTVa6LV+TrKyISiZIqUT8Tt/XWgOGBmGoPD9erwz4d6eqbd1W0d 6uybw/y6eoj3xec+qC7rdFWG501mvP91Bk4Kvd2u+pPhR7PMKWhKF301JBg/IYqhtCtF fJ5+ZdVQB/46JgABCTYlVtd01RWyZvq4EQ1HJm8ImLqFh9owNM8wAdYxx09uCShoYplY stfWLUJJF/bEYDqKy4itov9c7dFl4N83QaChEzy+1OxaON/7Tw3Muk9IyJbCBkXMBLfi rVSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ooS7To+A8Q4tHmFlk/8h3rmd3r3gi+TonoEx7cbfiOo=; b=PFepS19F2NWtjKKvpiqlor8m5gcz++5jSP2NgCNc4plbZfUMNPvxXXMNnpJ+YJqWym ULahsgNMwJQwiAOIlglKO7qcVuvXTA8VJlGmhKclJF2LYwl7Xo+KkjHnEUz+5989oK/K j6LM9PS6QuoUNf6OjXSE+EAMlCohUFRVD1zwkMf7RY78numH8a3kWht7Pn/N91NhieCX KEuiNhQsll6CCxDVhJhxpKc+3F0KnsvE52cnWUgrJSyi55EY4zx7MQFPqzi0h3IqWlrk gYLN2mYRX1lXMfp4BkhBcUktO3Lui5kqMCRT/eL+Sj10gmBFI/TurMBEF0oHH0DVhiHL 30cA== X-Gm-Message-State: AIkVDXKCq1+nKW3QdewptNAE4QGlVREDRS7khb3Ri4MtXanWH/02oz157xMHQvSN+LRbMwrnUo8E1qFcmvxBYw== X-Received: by 10.176.1.17 with SMTP id 17mr35062325uak.143.1483339188041; Sun, 01 Jan 2017 22:39:48 -0800 (PST) In-Reply-To: <20161231233747.GV1555@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:10847 Archived-At: --001a113cfa70627baf054516d141 Content-Type: text/plain; charset=UTF-8 Have you considered github On Sat, Dec 31, 2016 at 3:38 PM Rich Felker wrote: > 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. > > --001a113cfa70627baf054516d141 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Have you considered github

On Sat, Dec 31, 2016 at 3:38 PM Rich Felker <dalias@libc.org> wrote:
Here are some things I've really been wanting to get done for a = while,

that I/we should try to make happen in th= e coming months:



Swi= tching 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 w= ant to understand the

intended workflow for gett= ing changes published, but it's got to be

be= tter than the status quo where account creation doesn't even work.



Adopting an issue tracke= r. This requires actually selecting one and

sett= ing up the infrastructure for it. The wiki could possibly be moved

to the same infrastructure. (I want to keep webapp-ish s= tuff like

wiki, issue tracker etc. off the serve= r that hosts git and release

downloads because a= nything interactive is a significant attack

surf= ace that puts integrity of code as risk.)



Enabling git-over-https. This may require switching t= o a more-capable

httpd or other infrastructure c= hanges on the server.


Website redesign and move to musl.libc.org. I don'= t have any concrete

ideas for this yet, but I do= n't think the current website is at all in

l= ine with musl's maturity, current adoption/deployment, etc.



Documentation. Existing manual = should probably become a public git

repo that co= ntributors can submit patches/PRs for. Putting together

lists of (1) what's outdated in the current one, and (2) what n= ew

content would be most valuable, might be a go= od place to start and one

that could benefit fro= m community involvement.

--001a113cfa70627baf054516d141--