Website WG Meeting 2.0 - Feb 2, 2015

[therebelrobot]

MEETING POSTPONED FROM JAN 26th
Monday, Feb 2 at 19:00 UTC - Your time (Wolfram) | Your time (timeanddate.com)

Public YouTube Link: http://www.youtube.com/watch?v=SBJaXUA0lSY

Meeting Minutes Doc (to be added as a PR after the meeting)

Homework:

• select time on the 2nd for meeting
• link to help with timezones
• link to Hangout On Air
• link to committee minutes Google Doc, and volunteer to take minutes

Meeting Agenda

Previous Meeting Agenda

Matching or Diverging from io.js organizationally

Governance #81, Licensing #1, Contributing #69, Team Structure #19, Evangelism Team #82, IRC #65, Closing/Fixing Policy #76, Helping users properly report "website" Bugs/Issues #55

Build & Site Improvements

Pick a build system #22, i18n #33, Downloads, Release page (dynamic) #67, latest / semver links #80, Blog / announcements (page/section) #68, Feed for releases & announcements #79, List of supporting host (article/FAQ) #73

This Week Agenda

• Internationalization (i18n) #33, Choose and implement a simple build/template process? #22 - Status of i18n and build process
• "Share" the Social Love: process for helping to empower 3rd party postings #83, Evangelism: Social Media #109 - Social Media
• README: Add notes about hosting / build project / etc. #84 - Hosting, build process README
• Website WG Meeting 2.0 - Feb 2, 2015 #92, A new way of describing "stability" #108 - Stability / helping users test io.js, describing "unstable"
• Device / Browser Coverage #91 - Device / Browser Coverage
• Documentation Tooling #99 - taking on API documentation
• IRC or Slack? #106 - IRC vs. Gitter vs. Slack = Battle Royale!

After:

• PR a copy of the committee minutes (with a link to hangout) in to the project

[snostorm]

I may be out for this one as I'll be on the road around that time. I'll try to keep an eye on the agenda and pass along any feedback if I'll be missing. (Timezone: PST.)

[indexzero]

I will be out for this one. I have an all day event on the 26th. Will look for the notes.

[therebelrobot]

I got a doodle (https://doodle.com/xkhucvh65qheeuna) set up to see when everyone is available, or we can just do UTC 19:00 again if we want.

[snostorm]

Ticket open for 5 days, only 3 responses (2 people who can attend.) If no critical mass for this one perhaps we should aim for the Monday following? I'll be more available again by then myself.

[therebelrobot]

Yeah, it looks like that may be best. There is definitely no critical mass for this one. All in favor of rescheduling for a week from Monday? @Fishrock123 and I are still working on the build process, though we are getting close to finished.

[mikeal]

maybe add a quick discussion about the Working Groups PR on io.js and another about possibly taking on the project documentation.

[mikeal]

Can you close out the Doodle and pick a time so that it lands on the calendar :)

[therebelrobot]

Are we planning on moving it back a week then? or are we just going to meet without those who can't come tomorrow?

[therebelrobot]

@zeke @Fishrock123 @mikeal , it looks like @indexzero and @snostorm can't make this weeks meeting. @snostorm and I asked earlier about possibly moving this to the following week when more people can attend. Should we move it or still plan on meeting without them? Once there is a consensus on it I'll move to close the doodle and finalize the time.

[zeke]

I would prefer to meet next week, when I expect to have more to contribute to the conversation.

[Fishrock123]

Agreed, next week would probably be better. I wasn't able to get nearly as much done on it as I would've liked last week.

[therebelrobot]

Kk. That's consensus enough for me. I'll change this doc to reflect the new meeting date, and I'll get a new doodle set up to get everyone's times.

Barring, of course, a TC member overriding.

[therebelrobot]

Ok, I've updated this thread to reflect the new date, here's the doodle to collect when everyone will be available next week: https://doodle.com/5h7nv5gnpnnc7rmk