Website WG meeting - 6/18/2015

[bnb]

Checking to see if people can make it to a meeting at 18:00 GMT. We can move the time around if needed.

Edit: Changed title from 6/15 to 6/18

/ping @nodejs/website.

[Fishrock123]

Will be at nodeconf, nada

On Jun 10, 2015, at 8:21 PM, &! (bitandbang) notifications@github.com wrote:

Checking to see if people can make it to a meeting at 18:00 GMT.

/ping @nodejs/website.

—
Reply to this email directly or view it on GitHub.

[bnb]

@Fishrock123 How about the Friday before or the next day (Tues.)?

[bnb]

I now see the Fiday before is tomorrow, so we can probably scratch that. How are Tuesday or Wednesday at 18:00 GMT?

[therebelrobot]

Can't Tuesday at 18:00 GMT, but Wed is free for me.

[bnb]

Doodle for scheduling: http://doodle.com/gxmsagxhbqq7q5tx#table

[snostorm]

Submitted. I wonder if we need to start emailing our WG directly as a secondary ping. (There can be a lot of noise from GitHub.)

[bnb]

@snostorm That wouldn't be a bad idea.

[bnb]

@snostorm @therebelrobot I'm not sure if I set it up correctly. Can you verify that the times you selected are correct for your time zone, not EST? Expand -> Top right hand of grid shows time zone.

[therebelrobot]

@bnb, it says as soon as I get there that it was set in eastern time, but showing in mountain, which is my time zone. 'sall good.

[snostorm]

Are we going ahead today? After posting my "we should email all WG members" suggestion earlier I got a little distracted. I am able to attend but just am thinking we may be partially blocked by the lack of confirmation by our new nodejs.org members. (We've already had one meeting since the merger and were wanting them to join for the next.)

[fhemberger]

Sorry, can't make it today.

[therebelrobot]

The last I heard it was the doodle, but not many people participated in that. We do need to get the nodejs.org members onboard with this next meeting.

[bnb]

We need to come up with a system that alerts everyone and works fast. Not sure how to do that.

[bnb]

How about Thursday at 17:00GMT (1PM EST), since the four people who signed up for it are available.

Doodle link, if it helps: http://doodle.com/gxmsagxhbqq7q5tx#table

//cc @therebelrobot @mikeal @zeke @Fishrock123 @indexzero @snostorm @timaschew @robertkowalski @mkdolan @geek

[Fishrock123]

I should be able to make that.

[bnb]

@Fishrock123 Since we have you in addition to the rest of the previous core Website maintainers, I think we can call it a date.

[indexzero]

Will definitely be listening in, but I had a work meeting come up at this time slot in-between the time I RSVP'ed for it.

[bnb]

As-per nodejs/nodejs.org#360 (comment), we should discuss moving all efforts on a new official nodejs.org website to a repo such as nodejs/nodejs.org or nodejs/new.nodejs.org to focus input.

[therebelrobot]

So are we officially on for today at 17:00 GMT?

[bnb]

@therebelrobot Yes! How do you invite people? Want to know so I don't miss it. We also need to invite @misterdjules and anyone else from @Joyent/node-website. This has Julien's email/Google account: nodejs/nodejs.org-archive#137

[therebelrobot]

I have access to the io.js google plus page, I'll set up a hangouts on air if that's the time we want. I'll post a public join link here once I have one.

[bnb]

Yes, that seems to be the best time right now. Hangouts On Air is what people are familiar with, so we can just use that again.

[therebelrobot]

Kk. 17:00 GMT it is. I'll be online about 5 minutes before to help cat wrangle. I can only stay for about a half hour today though, we have a major launch brewing at work and a lot of work to get done for it. I probably shouldn't lead the meeting because of that too. https://plus.google.com/hangouts/_/hoaevent/AP36tYc4OMJQg9R0e-ZGM_rf3qzCVaa6XSOwSm7KE_PlNrBmvDhG5g

[snostorm]

I'm glad you guys were chatting about it. Saw the email notifications just now but missed the ones 3 days ago setting the time :) I'll be able to join.

[bnb]

Action items from this meeting:

• Move @nodejs/website to nodejs/iojs.org (or nodejs/iojs.org-website, whichever was previously decided)
• Move @Joyent/node-website to nodejs/nodejs.org
• Create a new central repository for new website developments, nodejs/new.nodejs.org
• Create a new issue on nodejs/new.nodejs.org prompting the community for a website design.
• Get structure of new.nodejs.org done, via PRs in feature branches

Evangelism WG

• Write a blog post, published to Medium or Node's blog, to raise awareness of the search for a new website design.

[rvagg]

are you bringing on additional members from joyent/node-website too or are they already all represented here?

[bnb]

@rvagg: @misterdjules attended the meeting today, but expressed that he would not be able to attend other Website WG meeting unless expressly requested by the Website WG team. He told us that we can go ahead with moving the Joyent/node-website to nodejs/nodejs.org without any problem on their end. It'd probably be best to get permission expressly from an authority before we go ahead and do it. I'll create an issue right now asking about it on Joyent/node-website.

[snostorm]

Heads up the https://github.com/nodejs/new.nodejs.org repo is now live.

[indexzero]

Sorry I missed this, but I couldn't duck out of the meeting I was in. Look forward to contributing to efforts going forward.