Added IPFS #3 #14

Merged
merged 21 commits into from Feb 1, 2016

Conversation

Projects
None yet
8 participants
@RichardLitt
Member

RichardLitt commented Jan 22, 2016

This is a bit late because I was hoping to have name-your-contributors done, but I didn't manage to do it, and now I need to add a timespan.

@eminence, can you add the contribs for last week?

Review period open for this Friday.

published/003-2016-Jan-12.md
+
+## Updates
+
+* [go-ipfs](//github.com/ipfs/go-ipfs) 0.3.11 is shipped! Also, we merged 0.4.0 into master. This is huge news that we've been waiting for for a long time. Also, [@jbenet](//github.com/jbenet), [@Dignifiedquire](//github.com/Dignifiedquire) and others [fixed appveyor](//github.com/ipfs/go-ipfs/pull/2137). The latest webui by [@Dignifiedquire](//github.com/Dignifiedquire) was also pushed in 0.3.11.

This comment has been minimized.

@dignifiedquire

dignifiedquire Jan 22, 2016

Member

repetition of also in the beginning of a sentance

@dignifiedquire

dignifiedquire Jan 22, 2016

Member

repetition of also in the beginning of a sentance

This comment has been minimized.

@dignifiedquire

dignifiedquire Jan 22, 2016

Member

This is huge news that we've been waiting for for a long time. This sentence sounds strange :/ (sorry for not being more helpful)

@dignifiedquire

dignifiedquire Jan 22, 2016

Member

This is huge news that we've been waiting for for a long time. This sentence sounds strange :/ (sorry for not being more helpful)

published/003-2016-Jan-12.md
+
+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.
+
+// TODO Add this

This comment has been minimized.

@dignifiedquire

dignifiedquire Jan 22, 2016

Member

This is not rendering properly

@dignifiedquire

dignifiedquire Jan 22, 2016

Member

This is not rendering properly

This comment has been minimized.

@RichardLitt

RichardLitt Jan 22, 2016

Member

Needs to be fixed before shipping. We need to add contribs. Working on it.

@RichardLitt

RichardLitt Jan 22, 2016

Member

Needs to be fixed before shipping. We need to add contribs. Working on it.

published/003-2016-Jan-12.md
+* [ipfs-merkle-dag](//github.com/vijayee/ipfs-merkle-dag) [@daviddias](//github.com/daviddias) worked on the js ipfs merkle-dag implementation, as well as putting in a lot of work in general on js-ipfs.
+
+## Work in Progress
+* [weekly](//github.com/ipfs/weekly) [@RichardLitt](//github.com/RichardLitt) put a lot of work in getting various sorts of attribution for contributors to IPFS, currently available as [name-your-contributors](//github.com/RichardLitt/name-your-contributors). This is almost done, but there's a few tweaks left to do.

This comment has been minimized.

@dignifiedquire

dignifiedquire Jan 22, 2016

Member

there are a few tweaks

@dignifiedquire

dignifiedquire Jan 22, 2016

Member

there are a few tweaks

@jbenet

This comment has been minimized.

Show comment
Hide comment
@jbenet

jbenet Jan 22, 2016

Member

There's likely more stuff that got done last week that needs to be mentioned here.

Look harder in the sprint issues, don't just limit yourself to starred things. And ask people directly if you dont have enough stuff listed, or are not sure whether to highlight something. People are starting to depend on this weekly to measure the heartbeat of the community and it should show accurate progress. Check also IRC logs, sometimes there's stuff posted worth highlighting. (and can also direct those people to post such cool stuff in the sprint issues in the future)

Member

jbenet commented Jan 22, 2016

There's likely more stuff that got done last week that needs to be mentioned here.

Look harder in the sprint issues, don't just limit yourself to starred things. And ask people directly if you dont have enough stuff listed, or are not sure whether to highlight something. People are starting to depend on this weekly to measure the heartbeat of the community and it should show accurate progress. Check also IRC logs, sometimes there's stuff posted worth highlighting. (and can also direct those people to post such cool stuff in the sprint issues in the future)

Add commit contribs
(Mon Jan 11 00:00:00 2016 to Tue Jan 19 00:00:00 2016)

I added 1 day, due to the 1 day delay on monday
@RichardLitt

This comment has been minimized.

Show comment
Hide comment
@RichardLitt

RichardLitt Jan 24, 2016

Member

Thanks @jbenet. It's been difficult to find the time for this over the past few days, with traveling. @whyrusleeping can you show me how I can access the IRC logs? I think the weekly would be better to be a as-we-go thing instead of an end of week summary, will make the process easier.

As it is, I'm not sure how much else there is; I asked @whyrusleeping, @noffle, and @diasdavid directly with little feedback about stuff to add. :/

Member

RichardLitt commented Jan 24, 2016

Thanks @jbenet. It's been difficult to find the time for this over the past few days, with traveling. @whyrusleeping can you show me how I can access the IRC logs? I think the weekly would be better to be a as-we-go thing instead of an end of week summary, will make the process easier.

As it is, I'm not sure how much else there is; I asked @whyrusleeping, @noffle, and @diasdavid directly with little feedback about stuff to add. :/

@whyrusleeping

This comment has been minimized.

Show comment
Hide comment
@whyrusleeping

whyrusleeping Jan 24, 2016

Member

I can send you my irc logs, but its just going to be a static copy of my weechat logs.

I can't really think of anything that happened this last week thats worthy of being put on the weekly... I'll post my sprint update in a little bit if you want to grep that for stuff

Member

whyrusleeping commented Jan 24, 2016

I can send you my irc logs, but its just going to be a static copy of my weechat logs.

I can't really think of anything that happened this last week thats worthy of being put on the weekly... I'll post my sprint update in a little bit if you want to grep that for stuff

@whyrusleeping

This comment has been minimized.

Show comment
Hide comment
@whyrusleeping

whyrusleeping Jan 24, 2016

Member

oh, right this is the previous week. got it.

Member

whyrusleeping commented Jan 24, 2016

oh, right this is the previous week. got it.

@dignifiedquire

This comment has been minimized.

Show comment
Hide comment
@dignifiedquire

dignifiedquire Jan 24, 2016

Member

Here are the logs for ipfs IRC https://botbot.me/freenode/ipfs/

Member

dignifiedquire commented Jan 24, 2016

Here are the logs for ipfs IRC https://botbot.me/freenode/ipfs/

@eminence

This comment has been minimized.

Show comment
Hide comment
@eminence

eminence Jan 25, 2016

Collaborator

I too have been busy with other things, and haven't contributed much to this weeks writeup. I can support @RichardLitt's idea of turning this into a "whenever needed" affair. When I first proposed these weekly writeups, I had hoped that they would be fairly quick to produce. The ones we've produced so far are really great! But I admit that I'm slightly concerned that the multi-hour effort to produce one of these is not sustainable.

Collaborator

eminence commented Jan 25, 2016

I too have been busy with other things, and haven't contributed much to this weeks writeup. I can support @RichardLitt's idea of turning this into a "whenever needed" affair. When I first proposed these weekly writeups, I had hoped that they would be fairly quick to produce. The ones we've produced so far are really great! But I admit that I'm slightly concerned that the multi-hour effort to produce one of these is not sustainable.

@dignifiedquire dignifiedquire referenced this pull request in ipfs/pm Jan 25, 2016

Closed

Sprint January 19th #83

RichardLitt added some commits Jan 29, 2016

published/003-2016-Jan-12.md
+* [**py-ipfs**](//github.com/ipfs/py-ipfs) Thanks to [@candeira](//github.com/candeira) and [@ivilata](//github.com/ivilata), we now have a much more filled out plan for the Python implementation of IPFS. Join in if you are a pythonista.
+* [**js-mafmt**](//github.com/whyrusleeping/js-mafmt) [@whyrusleeping](//github.com/whyrusleeping) is working on a multiaddr validator in js, after his go work in [mafmt](//github.com/whyrusleeping/mafmt)
+* [**archives**](//github.com/ipfs/archive) cdn.media.ccc.de is now being mirrored in the IPFS archives.
+* [**ifps-firefox-addon**](//github.com/lidel/ipfs-firefox-addon/releases/tag/v1.4.2) The Firefox addon that provides transparent access to IPFS resources via local HTTP2IPFS gateway has been updated to release 1.4.2. This is the first time we've mentioned this in this newsletter; go check it out. It also now supports the fs: protocol scheme.

This comment has been minimized.

@diasdavid

diasdavid Jan 29, 2016

Member

ipfs*

published/003-2016-Jan-12.md
+## Updates
+
+* [**ArcticJS**](http://arcticjs.club) [@diasdavid](//github.com/diasdavid), [@whyrusleeping](//github.com/whyrusleeping), [@RichardLitt](//github.com/RichardLitt), and [@noffle](//github.com/noffle) were all able to meet up for the first time as a group and hack together at [ArcticJS](http://arcticjs.club), the first JavaScript conference above the Arctic circle, in Svalbard. Around 15 attended, and there was a lot of hacking, snow, talking about buffers, and swimming in the ocean at midnight underneath the Aurora Borealis (no, really). Most of the work done at the conference was conversations, but included [@diasdavid](//github.com/diasdavid) and [@RichardLitt](//github.com/RichardLitt) working on the API together, [@whyrusleeping](//github.com/whyrusleeping) learning how to javascript, and [@diasdavid](//github.com/diasdavid) and [@xicombd](//github.com/xicombd) working on IPFS together. All in all, it was an incredible trip. The videos for the actual talks (given in the most Northernmost church in the world) are [here](https://www.youtube.com/playlist?list=PL3bvPCw5QCLLJUL2Q_bBI1bi9bYQ-4hci).
+* [**dist.ipfs.io**](https://dist.ipfs.io) A distributions page has been shipped! This was largely spearheaded by [@dignifiedquire](//github.com/dignifiedquire). http://dist.ipfs.io/

This comment has been minimized.

@jbenet

jbenet Jan 29, 2016

Member

expand on this, this is way more important for us than ArticJS. maybe @dignifiedquire can help.

@jbenet

jbenet Jan 29, 2016

Member

expand on this, this is way more important for us than ArticJS. maybe @dignifiedquire can help.

published/003-2016-Jan-12.md
+
+## Updates
+
+* [**ArcticJS**](http://arcticjs.club) [@diasdavid](//github.com/diasdavid), [@whyrusleeping](//github.com/whyrusleeping), [@RichardLitt](//github.com/RichardLitt), and [@noffle](//github.com/noffle) were all able to meet up for the first time as a group and hack together at [ArcticJS](http://arcticjs.club), the first JavaScript conference above the Arctic circle, in Svalbard. Around 15 attended, and there was a lot of hacking, snow, talking about buffers, and swimming in the ocean at midnight underneath the Aurora Borealis (no, really). Most of the work done at the conference was conversations, but included [@diasdavid](//github.com/diasdavid) and [@RichardLitt](//github.com/RichardLitt) working on the API together, [@whyrusleeping](//github.com/whyrusleeping) learning how to javascript, and [@diasdavid](//github.com/diasdavid) and [@xicombd](//github.com/xicombd) working on IPFS together. All in all, it was an incredible trip. The videos for the actual talks (given in the most Northernmost church in the world) are [here](https://www.youtube.com/playlist?list=PL3bvPCw5QCLLJUL2Q_bBI1bi9bYQ-4hci).

This comment has been minimized.

@jbenet

jbenet Jan 29, 2016

Member

this is awesome, maybe put it under it's own heading, like "Conferences" or something.

@jbenet

jbenet Jan 29, 2016

Member

this is awesome, maybe put it under it's own heading, like "Conferences" or something.

This comment has been minimized.

@jbenet

jbenet Jan 29, 2016

Member

Or "Meetups + Conferences" or something

@jbenet

jbenet Jan 29, 2016

Member

Or "Meetups + Conferences" or something

This comment has been minimized.

@RichardLitt

RichardLitt Jan 29, 2016

Member

Moved to it's own section.

@RichardLitt

RichardLitt Jan 29, 2016

Member

Moved to it's own section.

published/003-2016-Jan-12.md
+
+* [**ArcticJS**](http://arcticjs.club) [@diasdavid](//github.com/diasdavid), [@whyrusleeping](//github.com/whyrusleeping), [@RichardLitt](//github.com/RichardLitt), and [@noffle](//github.com/noffle) were all able to meet up for the first time as a group and hack together at [ArcticJS](http://arcticjs.club), the first JavaScript conference above the Arctic circle, in Svalbard. Around 15 attended, and there was a lot of hacking, snow, talking about buffers, and swimming in the ocean at midnight underneath the Aurora Borealis (no, really). Most of the work done at the conference was conversations, but included [@diasdavid](//github.com/diasdavid) and [@RichardLitt](//github.com/RichardLitt) working on the API together, [@whyrusleeping](//github.com/whyrusleeping) learning how to javascript, and [@diasdavid](//github.com/diasdavid) and [@xicombd](//github.com/xicombd) working on IPFS together. All in all, it was an incredible trip. The videos for the actual talks (given in the most Northernmost church in the world) are [here](https://www.youtube.com/playlist?list=PL3bvPCw5QCLLJUL2Q_bBI1bi9bYQ-4hci).
+* [**dist.ipfs.io**](https://dist.ipfs.io) A distributions page has been shipped! This was largely spearheaded by [@dignifiedquire](//github.com/dignifiedquire). http://dist.ipfs.io/
+* [**go-ipfs**](//github.com/ipfs/go-ipfs) 0.3.11 is shipped! Also, we merged 0.4.0 into master. [@jbenet](//github.com/jbenet), [@Dignifiedquire](//github.com/Dignifiedquire) and others [fixed appveyor](//github.com/ipfs/go-ipfs/pull/2137), which means that windows CI now works. And finally the latest webui by [@Dignifiedquire](//github.com/Dignifiedquire) was pushed in 0.3.11. Check out the [changelog](https://github.com/ipfs/go-ipfs/blob/master/CHANGELOG.md).

This comment has been minimized.

@jbenet

jbenet Jan 29, 2016

Member

0.4.0 means much more than "windows CI now works". i'd just remove that part, or attempt at describing 0.4.0's main improvements. (the windows CI things is a tiny factor comparatively)

@jbenet

jbenet Jan 29, 2016

Member

0.4.0 means much more than "windows CI now works". i'd just remove that part, or attempt at describing 0.4.0's main improvements. (the windows CI things is a tiny factor comparatively)

This comment has been minimized.

@RichardLitt

RichardLitt Jan 29, 2016

Member

Removed note.

@RichardLitt

RichardLitt Jan 29, 2016

Member

Removed note.

published/003-2016-Jan-12.md
+* [**ipfs-merkle-dag**](//github.com/vijayee/ipfs-merkle-dag) [@diasdavid](//github.com/diasdavid) worked on the js ipfs merkle-dag implementation, as well as putting in a lot of work in general on js-ipfs.
+* [**py-ipfs**](//github.com/ipfs/py-ipfs) Thanks to [@candeira](//github.com/candeira) and [@ivilata](//github.com/ivilata), we now have a much more filled out plan for the Python implementation of IPFS. Join in if you are a pythonista.
+* [**js-mafmt**](//github.com/whyrusleeping/js-mafmt) [@whyrusleeping](//github.com/whyrusleeping) is working on a multiaddr validator in js, after his go work in [mafmt](//github.com/whyrusleeping/mafmt)
+* [**infrastructure**](//github.com/ipfs/infrastructure) The public gateway at [ipfs.io](https://ipfs.io) is now backed by both v0.4.0-dev and v0.3.11 at the same time. Requests are proxied to both, and the first successful response wins. ipfs.io will be backed by v0.4.x alone eventually. What this means is that if you want to target your requests at one specific version, use v04x.ipfs.io or v03x.ipfs.io, respectively. The latter will stop returning DNS records when v03x isn't supported on the public gateway. Also, while we're releasing v0.4.0 and for a while after, the default bootstrap nodes are divided among v03x and v04x. Most can be used by v04x nodes, and a few by v03x nodes. The latter will be phased out over time.

This comment has been minimized.

@jbenet

jbenet Jan 29, 2016

Member

@lgierth it may be important to write more in an md doc what the the current state / future plans are (maybe as a file in infrastructure repo), and link to it here.

@jbenet

jbenet Jan 29, 2016

Member

@lgierth it may be important to write more in an md doc what the the current state / future plans are (maybe as a file in infrastructure repo), and link to it here.

published/003-2016-Jan-12.md
+* [**py-ipfs**](//github.com/ipfs/py-ipfs) Thanks to [@candeira](//github.com/candeira) and [@ivilata](//github.com/ivilata), we now have a much more filled out plan for the Python implementation of IPFS. Join in if you are a pythonista.
+* [**js-mafmt**](//github.com/whyrusleeping/js-mafmt) [@whyrusleeping](//github.com/whyrusleeping) is working on a multiaddr validator in js, after his go work in [mafmt](//github.com/whyrusleeping/mafmt)
+* [**infrastructure**](//github.com/ipfs/infrastructure) The public gateway at [ipfs.io](https://ipfs.io) is now backed by both v0.4.0-dev and v0.3.11 at the same time. Requests are proxied to both, and the first successful response wins. ipfs.io will be backed by v0.4.x alone eventually. What this means is that if you want to target your requests at one specific version, use v04x.ipfs.io or v03x.ipfs.io, respectively. The latter will stop returning DNS records when v03x isn't supported on the public gateway. Also, while we're releasing v0.4.0 and for a while after, the default bootstrap nodes are divided among v03x and v04x. Most can be used by v04x nodes, and a few by v03x nodes. The latter will be phased out over time.
+* [**ifps-firefox-addon**](//github.com/lidel/ipfs-firefox-addon/releases/tag/v1.4.2) The Firefox addon that provides transparent access to IPFS resources via local HTTP2IPFS gateway has been updated to release 1.4.2. This is the first time we've mentioned this in this newsletter; go check it out. It also now supports the IPFS protocol scheme.

This comment has been minimized.

@jbenet

jbenet Jan 29, 2016

Member

include a sentence or two about what this addon does.

@jbenet

jbenet Jan 29, 2016

Member

include a sentence or two about what this addon does.

This comment has been minimized.

This comment has been minimized.

@lidel

lidel Jan 29, 2016

Release page for 1.4.2 does not tell much :) Perhaps it is a better idea for the name "ipfs-firefox-addon" to be a link to https://github.com/lidel/ipfs-firefox-addon#ipfs-firefox-addon?

Then the phrase "release 1.4.2" could link to https://github.com/lidel/ipfs-firefox-addon/releases/tag/v1.4.2

@lidel

lidel Jan 29, 2016

Release page for 1.4.2 does not tell much :) Perhaps it is a better idea for the name "ipfs-firefox-addon" to be a link to https://github.com/lidel/ipfs-firefox-addon#ipfs-firefox-addon?

Then the phrase "release 1.4.2" could link to https://github.com/lidel/ipfs-firefox-addon/releases/tag/v1.4.2

This comment has been minimized.

@RichardLitt

RichardLitt Jan 29, 2016

Member

Done!

published/003-2016-Jan-12.md
+* [**go-multiaddr**](//github.com/jbenet/go-multiaddr) go-multiaddr now supports the adding of new protocols on the fly. This allows us to build in new protocols without having to force everyone to update the multiaddr library itself.
+* [**community**](//github.com/ipfs/community) The labels 'help wanted' and 'difficulty:easy', ':hard', and ':moderate' have been added to every IPFS repository, to help out contributors know what are some low-hanging fruit they can help with. As well, [@RichardLitt](//github.com/RichardLitt) has created a [Docs Styleguide](https://github.com/ipfs/community/blob/master/docs-styleguide.md) to help standardize how we use English in all of our tools. It'll grow as time goes on.
+* [**ipfs-dht**](//github.com/whyrusleeping/ipfs-dht) [@whyrusleeping](//github.com/whyrusleeping) wrote a 'just a dht' binary. This means you can help out the network without running a full ipfs node. It also takes less memory and bandwidth, and having more dht nodes will speed up lookups.
+* [**js-ipfs-merkle-dag**](//github.com/vijayee/js-ipfs-merkle-dag/) [@diasdavid](//github.com/diasdavid) worked on merkle-dag implementation interoperabolity, by enabling you to successfully read (and write) MerkleDAG nodes that were stored into an IPFS Repo through go-ipfs, [in JavaScript](https://github.com/vijayee/js-ipfs-merkle-dag/pull/6).

This comment has been minimized.

@jbenet

jbenet Jan 29, 2016

Member

i think this is here twice

@jbenet

jbenet Jan 29, 2016

Member

i think this is here twice

This comment has been minimized.

@RichardLitt

RichardLitt Jan 29, 2016

Member

Resolved.

@RichardLitt

RichardLitt Jan 29, 2016

Member

Resolved.

+- [@windemut](//github.com/windemut)
+- [@wking](//github.com/wking) (W. Trevor King)
+- [@xicombd](//github.com/xicombd) (Francisco Baio Dias)
+- [@zignig](//github.com/zignig) (Simon Kirkby)

This comment has been minimized.

@jbenet

jbenet Jan 29, 2016

Member

awesome list!

@jbenet

jbenet Jan 29, 2016

Member

awesome list!

+- [@fazo96](//github.com/fazo96) (Enrico Fasoli)
+- [@findkiko](//github.com/findkiko)
+- [@Foxcool](//github.com/Foxcool) (Alexander Babenko)
+- [@GitCop](//github.com/GitCop)

This comment has been minimized.

@jbenet

jbenet Jan 29, 2016

Member

lol

This comment has been minimized.

@jbenet

jbenet Jan 29, 2016

Member

(i kinda like it, credit where credit is due)

@jbenet

jbenet Jan 29, 2016

Member

(i kinda like it, credit where credit is due)

This comment has been minimized.

This comment has been minimized.

@jbenet

This comment has been minimized.

Show comment
Hide comment
@jbenet

jbenet Jan 29, 2016

Member

Possible to add:

Member

jbenet commented Jan 29, 2016

Possible to add:

RichardLitt added some commits Jan 29, 2016

@RichardLitt

This comment has been minimized.

Show comment
Hide comment
@RichardLitt

RichardLitt Jan 29, 2016

Member

@jbenet Added note about Joe Armstrong, and also dealt with all comments except for the one about infrastructure blogpost. Can we publish this, you think?

Member

RichardLitt commented Jan 29, 2016

@jbenet Added note about Joe Armstrong, and also dealt with all comments except for the one about infrastructure blogpost. Can we publish this, you think?

@lgierth

This comment has been minimized.

Show comment
Hide comment
@lgierth

lgierth Jan 30, 2016

Member

I'll take care of v03x/v04x in a blog post

Member

lgierth commented Jan 30, 2016

I'll take care of v03x/v04x in a blog post

jbenet added a commit that referenced this pull request Feb 1, 2016

@jbenet jbenet merged commit 520a903 into master Feb 1, 2016

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@jbenet

This comment has been minimized.

Show comment
Hide comment
@jbenet

jbenet Feb 1, 2016

Member

LGTM thanks guys

Member

jbenet commented Feb 1, 2016

LGTM thanks guys

@jbenet jbenet deleted the feature/jan-11 branch Feb 1, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment