From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 661F93B25E for ; Mon, 13 Jun 2016 09:25:12 -0400 (EDT) Received: by mail-qt0-x230.google.com with SMTP id c34so34229475qte.0 for ; Mon, 13 Jun 2016 06:25:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zuu5tGmDwKrSYA82CUJG8AIi5/eFL6d+poLGk0oFjgU=; b=gyrj/i5QhS9AcTocokJpE9TkLSY2uvoc18Mc29U8NA0P4segal3otk6xwNvNq/ttZH evtidg75LK25iS6vYDDRsErdvpBJ7FGo2ZKTtRtRbtwjyBfeaUHieSXRE2ViBeWNWKE5 WXJ5qiAvSLGDffc+y3B7/DIvGbzIWxnKpKoXDXtUJj+u5gIBX36QszCUjDtEpcfZa42b gsDL1eDXbSejxNRswpYDHVgoL8kJWPve6TgKywqKWVOJikwCk8XoXwA4qR9PmYsD/ZHB o+BnZMa4VAjHjRutPBLU6ZcPdRpVWZUeSfRYjrQ0tSA4SErBsGn97f5NCUTi9Swu2Em1 U+vA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zuu5tGmDwKrSYA82CUJG8AIi5/eFL6d+poLGk0oFjgU=; b=bEde4xUz4LA8EDl7Ato+JVPnDFqRIFB57ICO91xQv/JrBZJUsfwKVhWMMusEMOBkMS 3CLB5OKhp7Xh3GYNU1tICuQ1yqKvalkF7q5CWfsLSAvqof0U2Wi9NK9ILAHYNgRdbicQ 0rdVqdaGHlFnnH+BvwH9ef2y1rRzc+IIA/F5T5ZLmq3K7g980k5eqDvZ9oovyCBqqFcc sYj3MJAeWgpZEz6/SVPPmvP9O807/2xr9ScnB1/QRc4ndLzOeGXRxHjkKG8bT0nDU5Rx 9cdJcQi6Wpxtzn5lN1P4BwAS4UBfB6sthzsISW//mYdu5X3rbvcIgivwLlSV5y0zEP5Y BWUQ== X-Gm-Message-State: ALyK8tI+KubQaKlkaRuVU09OwHrrY1wfJsSwz03unvGHqjNlqz8KV8o108sdqSQy81/5ZA== X-Received: by 10.237.35.92 with SMTP id i28mr1716841qtc.85.1465824311463; Mon, 13 Jun 2016 06:25:11 -0700 (PDT) Received: from [192.168.253.145] ([68.238.49.248]) by smtp.gmail.com with ESMTPSA id o34sm6872819qte.48.2016.06.13.06.25.10 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 13 Jun 2016 06:25:10 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: Rich Brown In-Reply-To: <87k2hui8uj.fsf@toke.dk> Date: Mon, 13 Jun 2016 09:25:08 -0400 Cc: Dave Taht , bloat Content-Transfer-Encoding: quoted-printable Message-Id: <49626645-6EF1-46B2-80CC-AA8F5A10FF15@gmail.com> References: <86DAC1A9-D218-40A4-AD48-D9C0B4B01103@gmail.com> <87twh0j5dg.fsf@toke.dk> <87inxfk28r.fsf@toke.dk> <87wplvij9r.fsf@toke.dk> <2BB7767C-F58D-4A91-9EDF-03C9DD31D882@gmail.com> <87k2hui8uj.fsf@toke.dk> To: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= X-Mailer: Apple Mail (2.2104) Subject: Re: [Bloat] Bufferbloat.net - Organizing, curating, and workflow X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 13:25:12 -0000 Good comments all... Let me preface these responses by saying that I'm = willing to help out, but don't want to get in the way of the rapid = progress being made.=20 Toke: Let us know when you think you're done with major = reorganizations... I also want to see if there's consensus about when and how to make = updates, so that we're not stepping on toes. TL;DR questions: - Do we only want to use pull requests, or should core authors have edit = access to github? - Or do we use the 'draft' facility? (How?) >> - Is there a way to display newest entries? I'd like to see a >> sidebar element showing the 5 newest posts >=20 > Yes, certainly. Was thinking of putting a list of newest news items on > the front page. However, for the wiki pages it is not necessarily > obvious that having a notion of 'newest' is useful. I see the (new) News column on the home page. The content is right, but = it takes too much space on the page. Maybe there could be a box above = the "Find us elsewhere" panel that just had news article titles... Random updates to the wiki pages wouldn't need to be mentioned. But if = there's a new topic added, maybe we should publish a corresponding News = item to call it out. >> - Can an RSS feed be generated automatically? >=20 > Yes, but see above. I wonder whether an RSS icon could go in the heading of the News = panel... >> Curating: The current site makes it seem as if all pages are equally = important. I feel the urge to do the following: >> - Categorizing the "List of Wiki Pages" for a project (e.g., = http://bufferbloat.net/projects/cerowrt/ )=20 >> so there's a sense of their importance >=20 > A way to do this would be to update the 'index' wiki pages to be more > useful (e.g. https://www.bufferbloat.net/projects/cerowrt/wiki/) and > keep the overview pages as a 'complete' list. However, it's certainly > also possible to mark some of the pages as 'important' and have those > show up on top of the list. >=20 >=20 >> - Discard old/outdated/useless articles >=20 > Yes, this is probably needed. And also fixing broken links (see the > issue I opened for this on github). I figure that members of this group can take on sections as the spirit = moves them. >> Workflow: >> - Rules for making posts: Who can make them? How do they get >> published? >=20 > Well, it's a git repo. I figure anyone can do pull requests. Certainly. This is one of the items that I wanted to be sure we = discussed. Dave also mentioned that we might be comfortable giving core = authors permission to edit. That would give more direct access for = making small tweaks/corrections. I suspect bigger experiments should be done as PR's (especially if we = figure out how to use github.io pages to display the new form of the = site from our own repos...) >> - Auto-publish - if it's not already happening, could we >> re-render and publish after a commit? >=20 > Yes, that is certainly possible. For now I figure I'll do it manually > (it's just re-running a script), but if we get enough activity that = that > becomes a bottleneck, I can certainly set up something automated. Cool! It looks as if you added code to do that. Is it operational? >> - I see the 404 handler in place, but it doesn't seem to show a >> link to archive.org >=20 > It includes a javascript from archive.org which *should* show a link = if > (and only if) an archived version exists. Haven't verified that it > actually works. Ahah! I think this is going to be hard to test - Toke has done too good = a job of matching Hugo URLs to the old Redmine URLs... :-) I did fire up LinkChecker on the site, and it found a few bad URLs. I'll = send a separate message about it. >> - Is there a way to do page redirection? It looks as if Toke has = done a great job of replicating >> URLs in the new site, but if we see frequent broken >> links, is there a way to redirect a page to its >> equivalent on the new site? >=20 > Yes. This is already used for news items and issues. >=20 >> - Should we add a Google search box on 404 page? On every page? >=20 > Not sure what it takes to do this properly, and if it's worth the > hassle. >=20 >> - Would it make sense to review error logs from time to time? >=20 > Possible. Split out the logs to a separate file; can provide it if > someone wants to go digging. Or I can just parse out a list of 404 > errors from time to time. I know how to add Google Search, and can take it on after other stuff = has settled. Given the good match between new and old URLs, we might only need a = one-time survey of error.log files to see if there's major traffic to a = particular "lost" page. Thanks all! Rich=