Skip to content
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.

Evangelism: Weekly Update Feb 13th #122

Closed
mikeal opened this issue Feb 6, 2015 · 56 comments
Closed

Evangelism: Weekly Update Feb 13th #122

mikeal opened this issue Feb 6, 2015 · 56 comments

Comments

@mikeal
Copy link
Contributor

mikeal commented Feb 6, 2015

io.js support added by...

io.js breaks 10,000 stars on GitHub

On Feb. 13, io.js reached the goal of 10,000 stars on GitHub. We couldn't have done it without the support of the amazing community behind JavaScript. Thank you alll!

io.js 1.2.0 released

  • stream: Simpler stream construction ([readable-stream/issues#102[(https://github.com/Simpler stream creation readable-stream#102))
  • dns: lookup() now supports an 'all' boolean option, default to false but when turned on will cause the method to return an array of all resolved names for an address, see, (iojs/pull#744)
  • assert: Remove prototype property comparison in deepEqual() (iojs/issues#636); introduce a deepStrictEqual() method to mirror deepEqual() but performs strict equality checks on primitives (iojs/issues#639).
  • tracing: Add LTTng (Linux Trace Toolkit Next Generation) when compiled with the --with-lttng option. Trace points match those available for DTrace and ETW. (iojs/issues#702)
  • docs: Lots of doc updates, see individual commits; new Errors page discussing JavaScript errors, V8 specifics, and io.js specific error details.
  • npm upgrade to 2.5.1
  • libuv upgrade to 1.4.0, see libuv ChangeLog
  • Add new collaborators:

Opened our doors to the international community

View the original article on Medium.

  • Added interested contributors to teams for their language.
  • Teams registered Twitter accounts for their teams and other relevant social media accounts.
  • Teams came up with their own ways of working together, and they became more of "community organizers," as opposed to just "translators"

Stats for Localizations:

  • 146 people signed up to help with the localizations the first day (over 160 signed up now)
  • 27 languages communities created the first day (already up to 29)

Language Communities

io.js and Node.js

View the original article on Medium.

  • Scott Hammond, CEO of Joyent, expressed his desire to bring io.js back to the node.js.

In only a few months io.js...

  • Has grown to 23 active core team members
  • Has several working groups
  • Has 29 language localization teams,
  • Has drawn more contributors to the project than we’ve ever had in the history of node.js, and
  • Has been able to release quality software at a good pace with the support of an exceptional community.

We are eager to put this all behind us but we can’t sacrifice the progress we’ve made or the principles and open governance that got us here.

The Future

  • Talks with the node.js foundation are ongoing.
  • Once the foundation has a technical governance model you will see an issue on io.js’ GitHub about whether io.js should join.
    • This will be discussed and voted on openly in a public TC meeting following the governance rules we’ve already built.

For the community, nothing has changed.

What to do right now

## io.js support added by... 
* [Postmark](http://blog.postmarkapp.com/post/110829734198/its-official-were-getting-cozy-with-node-js) 
* [node-serialport](https://github.com/voodootikigod/node-serialport/issues/439)
* [Microsoft Azure](http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-iojs/)

## io.js breaks 10,000 stars on GitHub
On Feb. 13, io.js reached the goal of 10,000 stars on GitHub. We couldn't have done it without the support of the amazing community behind JavaScript. Thank you alll!

## io.js 1.2.0 released
* **stream**: Simpler stream construction ([readable-stream/issues#102[(https://github.com/iojs/readable-stream/issues/102))
* **dns**: `lookup()` now supports an `'all'` boolean option, default to `false` but when turned on will cause the method to return an array of all resolved names for an address, see, ([iojs/pull#744](https://github.com/iojs/io.js/pull/744))
* **assert**: Remove `prototype` property comparison in `deepEqual()` ([iojs/issues#636](https://github.com/iojs/io.js/pull/636)); introduce a `deepStrictEqual()` method to mirror `deepEqual()` but performs strict equality checks on primitives ([iojs/issues#639](https://github.com/iojs/io.js/pull/639)).
* **tracing**: Add [LTTng](http://lttng.org/) (Linux Trace Toolkit Next Generation) when compiled with the `--with-lttng option`. Trace points match those available for DTrace and ETW. ([iojs/issues#702](https://github.com/iojs/io.js/pull/702))
* **docs**: Lots of doc updates, see individual commits; new Errors page discussing JavaScript errors, V8 specifics, and io.js specific error details.
* **npm** upgrade to 2.5.1
* **libuv** upgrade to 1.4.0, see libuv [ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog)
* Add new collaborators: 
  * Aleksey Smolenchuk (@lxe)
  * Shigeki Ohtsu (@shigeki)

## Opened our doors to the international community
View the [original article](https://medium.com/@mikeal/how-io-js-built-a-146-person-27-language-localization-effort-in-one-day-65e5b1c49a62) on Medium.
* Added interested contributors to teams for their language.
* Teams registered Twitter accounts for their teams and other relevant social media accounts.
* Teams came up with their own ways of working together, and they became more of "community organizers," as opposed to just "translators"

### Stats for Localizations: 

* 146 people signed up to help with the localizations the first day (over 160 signed up now)
* 27 languages communities created the first day (already up to 29)

### Language Communities

* [`iojs-bn`](https://github.com/iojs/iojs-bn) Bengali Community
* [`iojs-cn`](https://github.com/iojs/iojs-cn) Chinese Community 
* [`iojs-cs`](https://github.com/iojs/iojs-cs) Czech Community 
* [`iojs-da`](https://github.com/iojs/iojs-da) Danish Community 
* [`iojs-de`](https://github.com/iojs/iojs-de) German Community
* [`iojs-el`](https://github.com/iojs/iojs-el) Greek Community
* [`iojs-es`](https://github.com/iojs/iojs-es) Spanish Community
* [`iojs-fa`](https://github.com/iojs/iojs-fa) Persian Community 
* [`iojs-fi`](https://github.com/iojs/iojs-fi) Finnish Community
* [`iojs-fr`](https://github.com/iojs/iojs-fr) French Community
* [`iojs-he`](https://github.com/iojs/iojs-he) Hebrew Community
* [`iojs-hi`](https://github.com/iojs/iojs-hi) Hindi Community 
* [`iojs-hu`](https://github.com/iojs/iojs-hu) Hungarian Community
* [`iojs-id`](https://github.com/iojs/iojs-id) Indonesian Community
* [`iojs-it`](https://github.com/iojs/iojs-it) Italian Community
* [`iojs-ja`](https://github.com/iojs/iojs-ja) Japanese Community
* [`iojs-ka`](https://github.com/iojs/iojs-ka) Georgian Community
* [`iojs-kr`](https://github.com/iojs/iojs-kr) Korean Community
* [`iojs-mk`](https://github.com/iojs/iojs-mk) Macedonian Community
* [`iojs-nl`](https://github.com/iojs/iojs-nl) Dutch Community
* [`iojs-no`](https://github.com/iojs/iojs-no) Norwegian Community
* [`iojs-pl`](https://github.com/iojs/iojs-pl) Polish Community
* [`iojs-pt`](https://github.com/iojs/iojs-pt) Portuguese Community
* [`iojs-ro`](https://github.com/iojs/iojs-ro) Romanian Community
* [`iojs-ru`](https://github.com/iojs/iojs-ru) Russian Community
* [`iojs-sv`](https://github.com/iojs/iojs-sv) Swedish Community
* [`iojs-tr`](https://github.com/iojs/iojs-tr) Turkish Community
* [`iojs-tw`](https://github.com/iojs/iojs-tw) Taiwan Community
* [`iojs-uk`](https://github.com/iojs/iojs-uk) Ukranian Community

## io.js and Node.js
View the [original article](https://medium.com/@iojs/io-js-and-a-node-js-foundation-4e14699fb7be) on Medium.
* Scott Hammond, CEO of Joyent, expressed his desire to bring io.js back to the node.js.

#### In only a few months io.js... 
* Has grown to 23 active core team members
* Has several working groups
* Has 29 language localization teams,
* Has drawn more contributors to the project than we’ve ever had in the history of node.js, and
* Has been able to release quality software at a good pace with the support of an exceptional community.

> We are eager to put this all behind us but we can’t sacrifice the progress we’ve made or the principles and open governance that got us here.

### The Future
* Talks with the node.js foundation are ongoing.
* Once the foundation has a technical governance model you will see an issue on io.js’ GitHub about whether io.js should join.

  * This will be discussed and voted on openly in a public TC meeting following the governance rules we’ve already built.

> For the community, nothing has changed.

### What to do right now
* Continue to send your pull requests to io.js
* Join one of the 27 [language localization teams](https://github.com/iojs/website/issues/125)
* Contribute to io.js’ working groups ([streams](https://github.com/iojs/readable-stream), [website](https://github.com/iojs/website), [evangelism](https://github.com/iojs/website/labels/evangelism), [tracing](https://github.com/iojs/tracing-wg), [build](https://github.com/iojs/build), [roadmap](https://github.com/iojs/roadmap)) and
* Continue to adopt io.js in your applications.
@yosuke-furukawa
Copy link
Member

landed lttng support for linux nodejs/node#702

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

the state of reconciliation with node.js https://medium.com/@iojs/io-js-and-a-node-js-foundation-4e14699fb7be

@bnb
Copy link

bnb commented Feb 12, 2015

Hey @mikeal: Where can I start working on collaborating with you on the evangelism front/weekly updates?

@bnb
Copy link

bnb commented Feb 12, 2015

@mikeal Did you mean 1.2.0 in your release statement? Am I missing something?

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

@bnb yes, I meant 1.2 :)

We need to start writing the copy for this weeks update, laying out some of the work that has happened in i18n and in the 1.2 release. Basically just pulling good bits from the blog posts and changelog.

You can contribute the copy just by commenting in Markdown :)

@bnb
Copy link

bnb commented Feb 12, 2015

Okay, sounds good. Working on it now.

@bnb
Copy link

bnb commented Feb 12, 2015

Opened our doors to the international community

View the original article on Medium.

  • Added interested contributors to teams for their language

  • Instructed teams to get a Twitter account for their team, and to register any other relevant social media accounts

  • Teams came up with their own ways of working together, and they became more of "community organizers," as opposed to "translators"

  • The international community went above and beyond and started taking complete charge of their teams, and started working on other translations without being asked, trying to find still more efficient ways to collaborate, and trusting each other and sharing team accounts
    .

    Stats for Localizations:

  • 146 people signed up to help with the localization process

  • 27 languages were represented by the new teams

## Opened our doors to the international community
* Added interested contributors to teams for their language 
* Instructed teams to get a Twitter account for their team, and to register any other relevant social media accounts
* Teams came up with their own ways of working together, and they became more of "community organizers," as opposed to "translators"
* The international community went above and beyond and started taking complete charge of their teams, and started working on other translations without being asked, trying to find still more efficient ways to collaborate, and trusting each other and sharing team accounts
.
### Stats for Localizations: 

* 146 people signed up to help with the localization process
* 27 languages were represented by the new teams

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

I think we can cut ", using official repos for internationalization" it makes the "Opened our doors" language stand out better :)

@bnb
Copy link

bnb commented Feb 12, 2015

Sounds good! Updated.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

postmark supports io.js http://blog.postmarkapp.com/

@bnb
Copy link

bnb commented Feb 12, 2015

Just a comment: Most of this was pretty much already in the perfect writing style, I just did formatting on it. It's written pretty well.


io.js and Node.js

View the original article on Medium.

  • Scott Hammond, CEO of Joyent, expressed his desire to bring io.js back to the Node.js project to the io.js TC in a private meeting

In only a few months io.js...

  • Has grown to 23 active core team members
  • Has several working groups
  • Has 27 language localization teams,
  • Has drawn more contributors to the project than we’ve ever had in the history of Node.js, and
  • Has been able to release quality software at a good pace with the support of an exceptional community.

We are eager to put this all behind us but we can’t sacrifice the progress we’ve made or the principles and open governance that got us here.

The Future

  • Talks with Joyent are ongoing
  • Once the foundation has a technical governance model you will see an issue on io.js’ GitHub about whether io.js should join
    • This will be discussed and voted on openly in a public TC meeting following the governance rules we’ve already built

For the community, nothing has changed.

What to do right now

## io.js and Node.js
View the [original article](https://medium.com/@iojs/io-js-and-a-node-js-foundation-4e14699fb7be) on Medium.
* Scott Hammond, CEO of Joyent, expressed his desire to bring io.js back to the Node.js project to the io.js TC in a private meeting

#### In only a few months io.js... 
* Has grown to 23 active core team members
* Has several working groups
* Has 27 language localization teams,
* Has drawn more contributors to the project than we’ve ever had in the history of Node.js, and
* Has been able to release quality software at a good pace with the support of an exceptional community.

> We are eager to put this all behind us but we can’t sacrifice the progress we’ve made or the principles and open governance that got us here.

### The Future
* Talks with Joyent are ongoing
* Once the foundation has a technical governance model you will see an issue on io.js’ GitHub about whether io.js should join

  * This will be discussed and voted on openly in a public TC meeting following the governance rules we’ve already built

> For the community, nothing has changed.

### What to do right now
* Continue to send your pull requests to io.js
* Join one of the 27 [language localization teams](https://github.com/iojs/website/issues/125)
* Contribute to io.js’ working groups ([streams](https://github.com/iojs/readable-stream), [website](https://github.com/iojs/website), [evangelism](https://github.com/iojs/website/labels/evangelism), [tracing](https://github.com/iojs/tracing-wg), [build](https://github.com/iojs/build), [roadmap](https://github.com/iojs/roadmap)) and
* Continue to adopt io.js in your applications.

@bnb
Copy link

bnb commented Feb 12, 2015

Is that too verbose?

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

@bnb I think it is fine but I'd like to find a way to link to the original at the top and then just provide this as a TLDR :)

@bnb
Copy link

bnb commented Feb 12, 2015

io.js support added by...

## io.js support added by... 
* [Postmark](http://blog.postmarkapp.com/post/110829734198/its-official-were-getting-cozy-with-node-js) 
* [node-serialport](https://github.com/voodootikigod/node-serialport/issues/439)
* [Microsoft Azure](http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-iojs/)

@bnb
Copy link

bnb commented Feb 12, 2015

@mikeal Okay, I'll do that.

@bnb
Copy link

bnb commented Feb 12, 2015

Updated both previous. Do you want me to tackle the 1.2.0 release as well? If so, what do you want included? The "Notable changes" section? Or a subset of that? Or content under other conditions?

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

Yea, a bullet point per notable change would be enough, and without the sub-bullet thing the changelog is doing :)

@bnb
Copy link

bnb commented Feb 12, 2015

io.js ChangeLog

  • stream: Simpler stream construction ([readable-stream/issues#102[(https://github.com/Simpler stream creation readable-stream#102))
  • dns: lookup() now supports an 'all' boolean option, default to false but when turned on will cause the method to return an array of all resolved names for an address, see, (iojs/pull#744)
  • assert: Remove prototype property comparison in deepEqual() (iojs/issues#636); introduce a deepStrictEqual() method to mirror deepEqual() but performs strict equality checks on primitives (iojs/issues#639).
  • tracing: Add LTTng (Linux Trace Toolkit Next Generation) when compiled with the --with-lttng option. Trace points match those available for DTrace and ETW. (iojs/issues#702)
  • docs: Lots of doc updates, see individual commits; new Errors page discussing JavaScript errors, V8 specifics, and io.js specific error details.
  • npm upgrade to 2.5.1
  • libuv upgrade to 1.4.0, see libuv ChangeLog
  • Add new collaborators:
## io.js ChangeLog
* **stream**: Simpler stream construction ([readable-stream/issues#102[(https://github.com/iojs/readable-stream/issues/102))
* **dns**: `lookup()` now supports an `'all'` boolean option, default to `false` but when turned on will cause the method to return an array of all resolved names for an address, see, ([iojs/pull#744](https://github.com/iojs/io.js/pull/744))
* **assert**: Remove `prototype` property comparison in `deepEqual()` ([iojs/issues#636](https://github.com/iojs/io.js/pull/636)); introduce a `deepStrictEqual()` method to mirror `deepEqual()` but performs strict equality checks on primitives ([iojs/issues#639](https://github.com/iojs/io.js/pull/639)).
* **tracing**: Add [LTTng](http://lttng.org/) (Linux Trace Toolkit Next Generation) when compiled with the `--with-lttng option`. Trace points match those available for DTrace and ETW. ([iojs/issues#702](https://github.com/iojs/io.js/pull/702))
* **docs**: Lots of doc updates, see individual commits; new Errors page discussing JavaScript errors, V8 specifics, and io.js specific error details.
* **npm** upgrade to 2.5.1
* **libuv** upgrade to 1.4.0, see libuv [ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog)
* Add new collaborators: 
  * Aleksey Smolenchuk (@lxe)
  * Shigeki Ohtsu (@shigeki)

@bnb
Copy link

bnb commented Feb 12, 2015

Hold on, let me bold the api names.

Edit: Done.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

support for io.js in serial-port serialport/node-serialport#439 which means that all the robotics libraries should work now :)

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

fixed.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

@bnb
Copy link

bnb commented Feb 13, 2015

Added to "io.js support added by..." Do you want something more lengthy for Azure?

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

@bnb that works

@bnb
Copy link

bnb commented Feb 13, 2015

@mikeal Just curious, are you going to compile all the bits of Markdown throughout this issue into the original comment at the top, or create a new issue?

@bnb
Copy link

bnb commented Feb 13, 2015

This type of content is also another reason why I think a self-hosted blog would be good--it seems to put a post containing what's been written in this Issue on Medium, but it would be a perfect weekly summary for activities on an official on-site io.js blog.

@Fishrock123
Copy link
Contributor

io.js broke 10k stars on github today: https://twitter.com/Fishrock123/status/566287341011369984

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

@bnb yup, I'll compile it all together and update the description in the ticket.

The reason we write all this is so that people will read it. More people will read it on Medium than a brand new blog we just did :)

@bnb
Copy link

bnb commented Feb 13, 2015

Standard version:


io.js breaks 10,000 stars on GitHub

On Feb. 13, io.js reached the goal of 10,000 stars on GitHub. {{insert inspirational thank you to the community}}

## io.js breaks 10,000 stars on GitHub
On Feb. 13, io.js reached the goal of 10,000 stars on GitHub. {{insert inspirational thank you to the community}}

Filled out version:


io.js breaks 10,000 stars on GitHub

On Feb. 13, io.js reached the goal of 10,000 stars on GitHub. We couldn't have done it without the support of the amazing community behind JavaScript. Thank you!

## io.js breaks 10,000 stars on GitHub
On Feb. 13, io.js reached the goal of 10,000 stars on GitHub. We couldn't have done it without the support of the amazing community behind JavaScript. Thank you!

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

Ok, I made some final copy edit tweaks and updated the Issue description.

Now it's time to reformat for Medium :(

@bnb
Copy link

bnb commented Feb 13, 2015

Is Medium's markdown different?

@bnb
Copy link

bnb commented Feb 13, 2015

I'd be totally willing to help with that.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

@bnb Medium doesn't support markdown but it mostly handles the formatting if you copy/paste the rendered text in, it just requires a little bit of cleanup :)

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

@Fishrock123
Copy link
Contributor

@mikeal can you make new Errors page link to https://iojs.org/api/errors.html ?

@Fishrock123
Copy link
Contributor

i ntroduce --> and introduced under the assert part of 1.2.0

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

@Fishrock123 fixed on Medium, thanks!

@kosamari
Copy link

Japanese already translated ;) thanks for the markdown ! much faster to work.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

@kosamari awesome! is there a link?

@kosamari
Copy link

In review on this PR nodejs/nodejs-ja#26 waiting for team to wake up ;) (I'm only one in US)

@mikeal mikeal closed this as completed Feb 13, 2015
@e-jigsaw
Copy link
Contributor

iojs-uk Ukranian Community

is typo. Ukrainian

@mikeal
Copy link
Contributor Author

mikeal commented Feb 14, 2015

@e-jigsaw fixed on Medium, thanks!

@e-jigsaw
Copy link
Contributor

👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants