From 6d151aa9b311fd5683abd2e8b6d5501c2d636e15 Mon Sep 17 00:00:00 2001 From: Manil Chowdhury Date: Thu, 30 Jan 2020 23:30:53 -0800 Subject: [PATCH 1/2] Create 2020-01-30.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Thank you for taking notes, @jonchurch and @SMotaal 👍🏽 --- meetings/2020-01-30.md | 51 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) create mode 100644 meetings/2020-01-30.md diff --git a/meetings/2020-01-30.md b/meetings/2020-01-30.md new file mode 100644 index 0000000000..6ab82edba4 --- /dev/null +++ b/meetings/2020-01-30.md @@ -0,0 +1,51 @@ +# Node.js Foundation Website Redesign Strategic Initiative Meeting 2020-01-30 + +## Links + +* **Recording**: +* **GitHub Issue**: https://github.com/nodejs/nodejs.dev/issues/390 +* **Minutes Google Doc**: https://docs.google.com/document/d/17IuIy9Ir7SHSq7O7UwOsnsoI3vRGL4z1XH-tUeClgMw/edit + +## Present + +* Saleh (@SMotaal) +* Jon (@jonchurch) +* Manil (@keywordnew) + + +## Agenda + +## Announcements + +*Extracted from **wr-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. + +### nodejs/nodejs.dev + +* Resolve meeting Zoom URL being expired +* Defining Website Redesign OKRs + * CommComm is looking at things in terms of OKRs to track long-term progress across projects + * What are OKRs we can create for website-redesign? + * Example: https://github.com/nodejs/community-committee/pull/569/files + * Continuity of process + * Documenting hows of technical administration: how to stage, how to CI, + * Identify areas of progress and future goals + * Create a feature roadmap + * Make available the top two features in nodejs.org: 1. Download Node.js and 2. Docs + * List the priorities for features + * Make explicit the channels of interfacing internally and with larger org + * Write down implicit team norms + * How do we propose and review non-feature changes in PRs? + +Manil made the point of making functional beta versions available so that folks can dogfood (try it out themselves) and give us feedback. We can tell if it is fulfilling the original usecases, by trying to get folks to switch to using our beta version. This could include making sure the core uses (Docs, Downloads) are functional. So we can then iterate on it and eventually supplant people’s needs from the original with our beta version. + +We’ve had issues with previews and /gcbrun, where the previews dont always run, or the preview link goes dead after a while. + +Saleh brought up wanting to have clarity around how/where to raise issues and ask questions in the project + +## Q&A, Other + +## Upcoming Meetings + +* **Node.js Foundation Calendar**: https://nodejs.org/calendar + +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. From 0ea5c830e6a41b3de656346a3e4541b737e27a5c Mon Sep 17 00:00:00 2001 From: Jon Church Date: Fri, 31 Jan 2020 13:49:50 -0500 Subject: [PATCH 2/2] fix: Tweak meeting minutes to fix md linting errors --- meetings/2020-01-30.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/meetings/2020-01-30.md b/meetings/2020-01-30.md index 6ab82edba4..ac58565b7d 100644 --- a/meetings/2020-01-30.md +++ b/meetings/2020-01-30.md @@ -12,7 +12,6 @@ * Jon (@jonchurch) * Manil (@keywordnew) - ## Agenda ## Announcements @@ -24,10 +23,10 @@ * Resolve meeting Zoom URL being expired * Defining Website Redesign OKRs * CommComm is looking at things in terms of OKRs to track long-term progress across projects - * What are OKRs we can create for website-redesign? + * What are OKRs we can create for website-redesign? * Example: https://github.com/nodejs/community-committee/pull/569/files * Continuity of process - * Documenting hows of technical administration: how to stage, how to CI, + * Documenting hows of technical administration: how to stage, how to CI, * Identify areas of progress and future goals * Create a feature roadmap * Make available the top two features in nodejs.org: 1. Download Node.js and 2. Docs