Evangelism: Weekly Update March 27th

[julianduque]

Let's begin!

[yosuke-furukawa]

Node.js Technical Governance Draft is proposed.
joyent/nodejs-advisory-board#30

[yosuke-furukawa]

[event] nodeschool tokyo is held in 4/12.
http://nodejs.connpass.com/event/13182/

[yosuke-furukawa]

node/io.js meets visual studio. http://blogs.msdn.com/b/visualstudio/archive/2015/03/25/node-js-tools-1-0-for-visual-studio.aspx

[mikeal]

it has been a light week, let's put together some good issues we'd like to see people engaged in and link to them here :)

[megastef]

When is this going out? We will make an announcement next Monday on blog.sematext.com supporting io.js in Sematext products - this would be something for 'Community Update' next week, right?

[mikeal]

@megastef this week's update will go out today so we can get the Sematext stuff in next weeks.

[megastef]

FYI. Community Update:
http://blog.sematext.com/2015/03/30/nodejs-iojs-monitoring/

[Fishrock123]

Did this end up going out?

[yosuke-furukawa]

#50 here.

[mikeal]

We had a lack of activity last week but this week will end up with a lot. Maybe we should just re-title this update to be for Friday and combine last weeks update with this one.

[rosskukulinski]

I think this did get published: https://medium.com/node-js-javascript/io-js-week-of-march-27th-9555f36bbb9a

[julianduque]

Just published it, thanks to @yosuke-furukawa and @Gioyik

[julianduque]

@mikeal better to have a weekly update, even if it's a light one.

Moving to next week, thanks everybody! #51

[diagramatics]

Just keeping the consistency, should the title formatting on Medium be H2 instead of H1? It seems to be the default styling for article titles across Medium.

[dotproto]

FWIW I agree with @julianduque; I'd much rather have regular updates than skip a week to make for a larger single push. Trains!

[mikeal]

my bad, nevermind :)

[subfuzion]

Related to the weekly update is how long it can take for the PR to get accepted on iojs/website. I commented on last week's PR (which subsequently ended up being closed as invalid), and on the related issue for making the update dynamic.

[julianduque]

@diagramatics changed titles to H2, thanks!

[mikeal]

we should stop pointing to the "last weekly update" and simply point to "weekly updates from io.js on medium"

[subfuzion]

I like the suggestion. Currently the link is to a specific medium page for that week. I hate to ask the question at the risk of having missed something totally obvious, but why are we publishing to medium instead of using github pages?

[subfuzion]

Since we go through a PR process before signing off on the update, why not just have the PR get merged into a gh-pages branch for this repo? I don't mean to hijack this issue; is this worth opening up a new issue for discussion?

[diagramatics]

I kinda like the way how it is right now, except that the "Weekly Update" should link to the latest update (which is correct) but the second link at "Medium" should link to the io.js Medium page. It would help for further discussions over there.

And @tonypujals is right, it seems using GitHub Pages and any sort of CMSes made for blogging in there are better at formatting, such as the -- flag which are converted as an em dash — at Medium automatically and straight quotes being converted as curly quotes (“ and ”). Not to mention the lack of <code></code> formatting.

Nitpicks about typography, really.