From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id E8AEA3B2B0 for ; Sun, 12 Jun 2016 14:02:31 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Filter: OpenDKIM Filter v2.10.3 mail2.tohojo.dk 95F8140B3C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1465754549; bh=2UuEJp1U1c9bMWvDDe1BehGgesDIoKF577GUISe/UAs=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=GGI0SbPLltU0XgM8wEmLEHMMqcIxgTYWUEtCqyRBKzQjWe6eekMEMXrostzchQhsg G8C+PwS5dM1ekuABCe+zhwAsI6jCW+a5n59WghHX11mJR1jRPhlxfYVkToTV94vlOr bJTOfABYYCOsN6zPYkb0DP9orG5WNgWGbTq7Meu0= Sender: toke@toke.dk Received: by alrua-karlstad.karlstad.toke.dk (Postfix, from userid 1000) id 2DCE2773693; Sun, 12 Jun 2016 20:02:28 +0200 (CEST) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Rich Brown Cc: Dave Taht , bloat 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> Date: Sun, 12 Jun 2016 20:02:28 +0200 In-Reply-To: <2BB7767C-F58D-4A91-9EDF-03C9DD31D882@gmail.com> (Rich Brown's message of "Sun, 12 Jun 2016 13:49:00 -0400") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87k2hui8uj.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain 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: Sun, 12 Jun 2016 18:02:32 -0000 Rich Brown writes: > Thanks again to Toke for all this good work. It's terrific to see the > pages resurrected, and to have the www.bufferbloat.net site living > again. You're welcome! Just glad it's being appreciated ;) > I've been thinking of the next steps - to make all this work really useful. I see there are three important issues: > > Organizing: Thinking about the best way to display the current information: > - Should Cake be listed as a top-level project? No opinion. > - Is there a way to display newest entries? I'd like to see a > sidebar element showing the 5 newest posts 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. > - Can an RSS feed be generated automatically? Yes, but see above. > 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/ ) > so there's a sense of their importance 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. > - Discard old/outdated/useless articles Yes, this is probably needed. And also fixing broken links (see the issue I opened for this on github). > Workflow: > - Rules for making posts: Who can make them? How do they get > published? Well, it's a git repo. I figure anyone can do pull requests. > - Auto-publish - if it's not already happening, could we > re-render and publish after a commit? 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. > - I see the 404 handler in place, but it doesn't seem to show a > link to archive.org 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. > - 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? Yes. This is already used for news items and issues. > - Should we add a Google search box on 404 page? On every page? Not sure what it takes to do this properly, and if it's worth the hassle. > - Would it make sense to review error logs from time to time? 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. -Toke