Re: [Revampers] www.ietf.org website revamp community review committee - 20170627 - notes

Robert Sparks <rjsparks@nostrum.com> Tue, 27 June 2017 21:04 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: revampers@ietfa.amsl.com
Delivered-To: revampers@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6070012EB20 for <revampers@ietfa.amsl.com>; Tue, 27 Jun 2017 14:04:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kz_M_J1IDO5U for <revampers@ietfa.amsl.com>; Tue, 27 Jun 2017 14:04:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0BF612706D for <revampers@ietf.org>; Tue, 27 Jun 2017 14:03:59 -0700 (PDT)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v5RL3wai049832 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <revampers@ietf.org>; Tue, 27 Jun 2017 16:03:59 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
To: revampers@ietf.org
References: <4CB144F7-2CA6-4250-A66E-A9A0FE8396E5@isoc.org> <88be80d0-59a0-907b-9b1e-411b4b87dc26@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <0f6187de-1ea8-57b3-b01e-69037bbbe1b4@nostrum.com>
Date: Tue, 27 Jun 2017 16:03:58 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <88be80d0-59a0-907b-9b1e-411b4b87dc26@nostrum.com>
Content-Type: multipart/alternative; boundary="------------60AF0F9D5CE90E9202BBD691"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/revampers/t0HRNx0JzkP67Q0XxBH_w33603w>
Subject: Re: [Revampers] www.ietf.org website revamp community review committee - 20170627 - notes
X-BeenThere: revampers@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "A discussion list for the IETF community review committee for the public-facing IETF website revamp project." <revampers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/revampers>, <mailto:revampers-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/revampers/>
List-Post: <mailto:revampers@ietf.org>
List-Help: <mailto:revampers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/revampers>, <mailto:revampers-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jun 2017 21:04:06 -0000

Other small content things (is it time to critique content things?)

There are two pages named WG pages, one under "Groups" and one under 
"How we work". Should probably reconcile that to one page.

On the upcoming/99 page, there's a link labelled "Reporting Problems" 
that goes to the "Reporting Potential Harassment" page (which has its 
own link on the upcoming/99 page). That should probably go to a page 
about how to report bugs or meeting trouble or something else.

RjS


On 6/27/17 3:48 PM, Robert Sparks wrote:
>
> I'm listening to the recording and playing with the site in parallel.
>
> One thing I noticed right away on the home page is that the "What's 
> new" section is showing very old articles from the blog - it looks 
> like its sorting things in oldest to newest and showing the oldest 
> perhaps? Newest to oldest would work better.
>
> Similarly, it's making IETF100 more important than IETF99 - I suspect 
> it should make the next upcoming meeting more prominent.
>
> RjS
>
>
>
> On 6/27/17 2:35 PM, Greg Wood wrote:
>> Hi,
>>
>> Here is a link to folder with the recording (MP4 of the video) from the conversation last week:
>>
>> https://isoc.box.com/v/IETF-Website-CRC-201706
>>
>> Notes are also below. Please let me know if I have missed anything or there are any questions.
>>
>> Here are a few highlights:
>>
>> • Send notes from the call around (and the recording) to spark input/questions <—THIS NOTE
>> • Suggestions about specific individuals to review the beta site<—ENCOURAGED!
>> • Plan to release beta.ietf.org ~8 July (before IETF 99)
>> • Check-in with Revampers after IETF 99/before production <—LIKELY FIRST WEEK OF AUGUST
>>
>> Thanks!
>>
>> -Greg
>>
>> NOTES
>>
>> 0. Agenda bash
>>
>> 1. Introduction
>> Community Review Committee == Revampers
>>
>> 2. Review of project process and progress
>> 	• So far...
>> 	• SOW development
>> 	• Input from interviews with audiences (participants, potential participants, non-participants)
>> 	• Review by CRC and community
>> 	• Preview for community at IETF 98 (including update at the WG Chairs meeting)
>>
>>       b) Currently.
>> 	• finishing content, working with content review groups (EMO Directorate (nee EDU-Team), IESG, Secretariat
>> 	• Fixing bugs and implementing features with Torchbox
>> 	• Testing with groups (non-participants, potential participants)
>>
>>      c) Upcoming
>> 	• Review by IESG and IAB
>> 	• Planning for community “beta” preview to be released around 8 July--in advance of IETF99
>> 	• “Office hours” to be held at IETF 99 (similar to IETF 98) and update at the WG Chairs meeting
>> 	• Public release on the schedule for early August
>>
>> 3. Review/tour of revamped website
>> https://beta.ietf.org  
>> ietfwagtail / ietfshowme
>>
>> 	• Responsive mode
>> 	• Blog posts
>> 	• Meetings
>> 	• Quick links for current IETF participants
>>
>>
>> 4. Discussion
>>
>> Requesting CRC input:
>> 	• How to test/confirm technical requirements from SOW including:
>> 		• HTML/Open standards
>> 		• Plug-ins and Javascript
>> 		• Accessibility
>> 		• Responsive design
>> 		• SOW:https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf  
>>
>> 	• Suggestions about IETF community review process
>> 		• Including suggestions about specific individuals to review
>>
>> 	• Next steps on website review development
>>
>> Comment: Need a new name for the Tools “quick links” tab
>> 	• Suggestion “Popular” instead of “Tools” for the name
>>
>> 5. AOB/Next steps
>> 	• Send notes from the call around (and the recording) to spark further input
>> 	• Check-in with Revampers after IETF 99/before production
>>
>>
>>
>>
>> _______________________________________________
>> Revampers mailing list
>> Revampers@ietf.org
>> https://www.ietf.org/mailman/listinfo/revampers
>
>
>
> _______________________________________________
> Revampers mailing list
> Revampers@ietf.org
> https://www.ietf.org/mailman/listinfo/revampers