This repository has been archived by the owner on Aug 1, 2019. It is now read-only.
Weekly update for 2015-08-14 #137
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you !!!! |
|
Done. 👍 |
| * As mentioned up top, io.js v4.x will be Node.js v4.x. Or as [Mikeal Rogers](http://twitter.com/mikeal) said, [4.0 is the new 1.0](https://medium.com/node-js-javascript/4-0-is-the-new-1-0-386597a3436d). | ||
| * The Node.js Collaborator Summit was hosted on 6th – 7th August in San Fransisco. You can see the notes in the [nodejs/summit](https://github.com/nodejs/summit) repository, [the GitHub issue](https://github.com/nodejs/summit/issues/11), or on [the Google Docs folder](https://drive.google.com/folderview?id=0B4tYrG9tjAW0fk9VOG52R2VQMmZHNWdpYnpqWU5MYUlfamNycktmeEl3UkNhdk1PS1Rid3c&usp=sharing). | ||
| * [nodejs/collaboration](https://github.com/nodejs/collaboration) was made along with [the team](https://github.com/orgs/nodejs/teams/collaboration) to help with communication between Working Groups, as well as getting better ways to have evangelism, website, documentation and the 30+ i18n groups work together. | ||
| * The new [Intl WG](https://github.com/nodejs/Intl) had [a meeting](https://github.com/nodejs/Intl/issues/8/?utm_source=io.js+and+Node.js+News&utm_medium=article) on August 11th. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
|
LGTM, without tiny nits. |
|
Alright, fixed. GitHub Desktop is surprisingly usable on mobile. |
yosuke-furukawa
added a commit
that referenced
this pull request
Aug 21, 2015
Weekly update for 2015-08-14
|
@yosuke-furukawa Seems like the Medium counterpart is missing a space, in "You can see the notes in thenodejs/summit repository" between the "the" and the "nodejs/summit" link. |
|
thx |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In hopes of publishing this on time.
Key highlights:
Still waiting for Collaboration Summit's summary per Summary article(s) on (Aug 2015) summit? openjs-foundation/summit#13. Probably do not merge yet until a summary is available to post as a separate section or a decision is made to post a mention in the Community Updates section.Solved per Mikeal's guidance, added a section on Community Updates with links to docs.Once the summit concerns has been addressed, one LGTM is enough for me to immediately submit a PR to new.nodejs.org.