-
Notifications
You must be signed in to change notification settings - Fork 130
Evangelism: Weekly Update Feb 20th #188
Comments
wow :) |
Just curious--where do you guys usually find the kind of news that should go here? |
Another official support of io.js : https://twitter.com/catberryjs/status/567317962013827073 |
https://twitter.com/christkv/status/567323539637039104
|
these people added support https://www.clever-cloud.com/blog/features/2015/01/23/introducing-io.js/ |
So did these people: https://twitter.com/thenativeweb/status/566690590348546048 |
And these guys: https://twitter.com/DNSChain/status/567487579159678976 |
Don't know if those two are relevant enough to be added. Are we only doing big names, or anybody who adds support? I'm a fan of the latter--it will recognize people taking the step to use io.js, and will share them with the community. |
They don't need to be huge, anyone who's supporting the project is great :) |
Official (?) mongodb node module supports io.js "2.0.16 2015-02-16": https://github.com/mongodb/node-mongodb-native/blob/2.0/HISTORY.md |
TDPAH adds io.js support: https://twitter.com/tdp_org/status/567442395974103040 |
Don't think this was in last week's roundup, but node-sass added support in 2.0.1 recently (can't find exact date): sass/node-sass#655 |
total.js framework - io.js support - https://github.com/totaljs/framework/releases/tag/v1.7.1 |
|
this happened and blew up my twitter feed :) http://nodegovernance.io/ |
roadmap slides are up :) http://roadmap.iojs.org/ |
roadmap PR in final edits https://github.com/iojs/io.js/pull/886/files |
@bnb did you want to do the copy this time or should I do it? |
@mikeal I'd be happy to. Do you just want me to do little snippets for each item in this issue? If so, do you want like things grouped together? I'm guessing you do, but just want to make sure. |
@mikeal Also, should I include the WG meetings on YouTube and SoundCloud? |
Maybe the format should be:
|
@mikeal Okay, working on it! |
New Website Localizations Landed:
|
Edited Spanish in the prior localizations comment to reflect the latest merge. |
Okay, no problem! I was just vamping in the roadmap part. Something I noticed during retreving the YouTube links is that there's not a consistent naming strategy for the meetings. Would it be possible to get all the facilitators of the meetings to follow a consistent naming convention? I know you probably know 10x as much about SEO as I do, but I think it's worth being consistent for the sake of people looking for the meetings as a whole and specific meetings individually. For example:
would be the convention, and
would be an example of it implemented. Here's templates for all the titles in that style, which I can edit if you'd like: Technical Committee:
Tracing WG:
Build WG:
Website WG:
|
It’s actually quite hard to figure out the hangouts stuff so I doubt we’ll get anything like consistent naming to work across facilitators :) But, we can change the titles on youtube quite easily after the fact. I can add you to the G+ page so that you can edit the titles on youtube if you tell me your G+ email addy.
|
My Gmail address is tieliaco@gmail.com. I'd be happy to go in and change them. |
@bnb you're added, when you login to youtube click on the account icon on the top right to switch to iojs. |
There's nothing on YouTube, Google+, or Gmail (confirmation email, maybe) that indicate I've been added. Did the system screw up somewhere, or am I not seeing it? I click the icon of my avatar on YouTube, and there's only two pages I created years ago. If it's too much trouble, don't worry about it. |
@bnb does anything pop up when you go to https://plus.google.com/b/101986715696875566237/ ? It says you're invited |
Got it. Had to sign out of my college Google account, as it wouldn't let me open the io.js page with my normal account. Working on changing titles now. |
Updated all the YouTube titles to follow a consistent pattern and added a few tags to each video. Tags are a huge way to get visibility, so it's 100% worth tagging every video. I'll be happy to do this, and if you think of more, I'll add them. |
@julianduque Also saw this, but decided against posting it here as it makes us seem like we're fighting Node to me. Anyone else's thoughts? |
@bnb @julianduque yeah it would seem a little combative if we included side-by-side comparisons. Though I'm not sure how the TC would feel. Might be a good question for @mikeal ? |
I'd like to include the performance post but we do need to be careful about the copy. How about something like "Raygun did a performance analysis of different versions of node.js and io.js. Both are improving performance each release!" |
we'll need to include this as well https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#2015-02-20-version-130-rvagg |
LTTng w/ io.js basics screencast https://asciinema.org/a/16785 |
@mikeal Good wording on the performance test. I'll add it. Also adding the release and screencast. |
io.js Releases 1.3.0Notable changes include:
Notable Events in the Community
io.js Support Added
io.js Working Group Meetings
|
@bnb great job! I updated the main Issue body. I'll go ahead and post on Medium now as well. Do you want to log the issue for next weeks so that you can continue to edit the main issue body next time? |
@mikeal this is ready to translate? |
@julianduque yup! :) |
should
be linked to somewhere ? |
@mikeal Logging issue now. |
I noticed we had a nice list of new translations above which didn't make the cut for the article. Maybe for next week we can do another update on these efforts? Also, can we close this now that we're post-publish? |
io.js Releases 1.3.0
Notable changes include:
url.resolve('/path/to/file', '.')
now returns/path/to/
with the trailing slash,url.resolve('/', '.')
returns/
#278 (Amir Saboury)tls
andhttps
has been changed to one that achieves Perfect Forward Secrecy with all modern browsers. Additionally, insecure RC4 ciphers have been excluded. If you absolutely require RC4, please specify your own cipher suites. #826 (Roman Reiss)Notable Events in the Community
io.js Support Added
io.js Working Group Meetings
The text was updated successfully, but these errors were encountered: