Add January 12 weekly #12
+47
−0
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,42 @@ | ||
| # IPFS Weekly #2 | ||
|
|
||
| [IPFS](//ipfs.io/) is a new hypermedia distribution protocol, addressed by content and identities, aiming to make the web faster, safer, and more open. In these posts, we will try to highlight some of the development that happened in the past week. For anyone looking to get involved, follow the embedded hyperlinks, search the wealth of information on [github](//github.com/ipfs) or join us on [IRC](//webchat.freenode.net/?channels=ipfs) (#ipfs on the Freenode network). | ||
|
|
||
| ## Updates | ||
|
|
||
| * [**(specs)**](//github.com/ipfs/specs) There was much debate in the [IPLD spec](https://github.com/ipfs/specs/pull/37) about pathing notation. [@mildred](//github.com/mildred) in particular did a lot of good work. | ||
| * [**(go-ipfs)**](//github.com/ipfs/go-ipfs) The IPFS Docker image is now tested automatically on Travis, thanks to [@ChristianKniep](//github.com/ChristianKniep) and [@whyrusleeping](//github.com/whyrusleeping). For more, see the [go-ipfs#2064](//github.com/ipfs/go-ipfs/pull/2064) pull request. | ||
|
There was a problem hiding this comment. maybe add @chriscool to this thanks too-- he did most of the work i think? |
||
| * [**(js-ipfs)**](//github.com/ipfs/js-ipfs) Now you can do `npm i -g js-ipfs` and use jsipfs bootstrap + id + version commands, fully compatible with the go-ipfs repo, thanks to [@diasdavid](//github.com/diasdavid)! | ||
|
There was a problem hiding this comment. Maybe add |
||
| * [**(community)**](//github.com/ipfs/community) [@RichardLitt](//github.com/RichardLitt) merged the PR for [JavaScript guidelines](//github.com/ipfs/community/blob/master/js-contribution-guidelines.md) for IPFS repos. | ||
|
|
||
| ## Work in Progress | ||
|
|
||
| * [**(distributions)**](//github.com/distributions) [@Dignifiedquire](//github.com/Dignifiedquire) further developed the distributions page. | ||
|
There was a problem hiding this comment. unless @dignifiedquire objects, can we include a link to http://v04x.ipfs.io/ipfs/QmZyvWokPYGg6DrjE6o2V7qhThzZQZ8QCWqdd2U3S75HXC/index.html it's so pretty! |
||
| * [**(go-ipfs)**](//github.com/ipfs/go-ipfs) [@lgierth](//github.com/lgierth) continued the work towards the dev040 migration. | ||
|
|
||
| ## Contributors | ||
|
|
||
| Across the entire IPFS GitHub organization, the following people have committed code since January 4th. (We're autogenerating this list using [this tool](//github.com/ipfs/weekly/blob/master/tools/get_commits.py), so please let us know if your name isn't here.) In the future, we will also include people who comment, as they are also super important; bear with us while we develop that technology. | ||
|
|
||
| * [@chriscool](//github.com/chriscool) (Christian Couder) | ||
| * [@ChristianKniep](//github.com/ChristianKniep) (Christian Kniep) | ||
| * [@diasdavid](//github.com/diasdavid) (David Dias) | ||
| * [@Dignifiedquire](//github.com/Dignifiedquire) (Friedel Ziegelmayer) | ||
| * [@eminence](//github.com/eminence) (Andrew Chin) | ||
| * [@greenkeeperio-bot](//github.com/greenkeeperio-bot) | ||
| * [@ianopolous](//github.com/ianopolous) (Ian Preston) | ||
| * [@jbenet](//github.com/jbenet) (Juan Benet) | ||
| * [@Kubuxu](//github.com/Kubuxu) (Jakub Sztandera) | ||
| * [@lgierth](//github.com/lgierth) (Lars Gierth) | ||
| * [@noffle](//github.com/noffle) (Stephen Whitmore) | ||
| * [@ralphtheninja](//github.com/ralphtheninja) (Lars-Magnus Skog) | ||
| * [@ReadmeCritic](//github.com/ReadmeCritic) | ||
| * [@RichardLitt](//github.com/RichardLitt) (Richard Littauer) | ||
| * [@whyrusleeping](//github.com/whyrusleeping) (Jeromy Johnson) | ||
| * [@yuvallanger](//github.com/yuvallanger) (Yuval Langer) | ||
|
|
||
| Thanks, and see you next week! | ||
|
|
||
| - Richard Littauer and Andrew Chin | ||
|
|
||
| [_Send us feedback about the Weekly_](//github.com/ipfs/weekly/issues/7) | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add:
Here are some of the highlights for the January 5th Sprint
(this follows the model we set up for the first Weekly, and provides a link for others to get more info)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good to me. Want to test your powers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Push successful! I didn't rebase/squash, though. Do you care?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't. Do you know how? Good to know, because in the future makes more sense to do so, I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I do know how, but I don't often to do (since it'll erase history, and erasing history is permanent!) It's generally up to each project to come up with a policy about rebasing PRs (so I guess we should decide what we want)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. I am rebase and force push trigger happy, and I know it. So, I don't mind.