You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: published/005-2016-Feb-1.md
+96-4Lines changed: 96 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,14 @@
4
4
5
5
If you would like to get this update as an email, sign up for our [weekly newsletter](//tinyletter.com/ipfsweekly)!
6
6
7
-
Here are some of the highlights for the [February 1st](//github.com/ipfs/pm/issues/88) and [February 8](//github.com/ipfs/pm/issues/89) sprints:
7
+
Here are some of the highlights for the February sprints:
8
8
9
9
## Updates
10
10
11
11
*[**go-ipfs**](//github.com/ipfs/go-ipfs)
12
12
-[@noffle](//github.com/noffle) made [a fix](https://github.com/ipfs/go-ipfs/pull/2296) for when your FUSE connection is terminated.
13
+
-[@noffle](//github.com/noffle), [@whyrusleeping](//github.com/whyrusleeping) and [@chriscool](//github.com/chriscool) have been doing lots to make our tests greener. This'll let us get PRs in faster because we won't need to wonder whether our CI is lying to us or not. This gives us more confidence about the code we ship, and allows us to ship more often.
14
+
-[@noffle](//github.com/noffle) also made progress toward getting `go-ipfs` compatible with vanilla `go get` installation. Hope to have more tangible results to show by end of the month.
13
15
-[@RichardLitt](//github.com/RichardLitt) made a lot of documentation fixes to the CLI while working on the IPFS HTTP API.
14
16
-[@lgierth](//github.com/lgierth) improved the automated [docker image](https://github.com/ipfs/go-ipfs/pull/2308) for go-ipfs, which is now named `ipfs/go-ipfs`. Give it a try: `docker run -i --net=host ipfs/go-ipfs`. The new image is built automatically for every commit, and has automatic tags for the coming releases. It's also a few MB smaller, and doesn't require mounting a volume for the IPFS repository anymore. Instead, if there's no volume mounted, it'll generate an ephemeral identity and configuration which will be lost when the container exits. This is ideal for testing or just trying something out real quick. Images for go-ipfs 0.3.x are not provided, because the Dockerfile shipped with these version isn't suitable for Docker Hub automatic builds.
15
17
-[@chriscool](//github.com/chriscool) rewrote [the build documentation for Windows](//github.com/ipfs/go-ipfs/blob/master/docs/windows.md), which enabled [@slothbag](//github.com/slothbag) to get Windows builds working again with minimal fuss.
@@ -24,6 +26,22 @@ Here are some of the highlights for the [February 1st](//github.com/ipfs/pm/issu
24
26
- As well, thanks to [@dignifiedquire](//github.com/dignifiedquire)'s efforts, the js-ipfs API now returns promises if there isn't a specified callback, allowing both major methods used by the Javascript community to work equally well.
- [@diasdavid](//github.com/diasdavid) merged registry-static into registry-mirror and removed all of the unnecessary stuff [(this was huge)](https://github.com/diasdavid/registry-mirror/pull/33).
29
+
*[**station**](//github.com/ipfs/station)
30
+
-[@dignifiedquire](//github.com/dignifiedquire) fixed drag and drop
31
+
file uploading, and some dependency issues. So go ahead and try it
32
+
out.
33
+
*[**ipfs-geoip**](//github.com/ipfs/ipfs-geoip)
34
+
-[@dignifiedquire](//github.com/dignifiedquire) rewrote the generation
35
+
script and cleaned up the code so that now the data is consistently
36
+
reproducable and fully stored on IPFS. This ensures that geoip lookups
-[@chriscool](//github.com/chriscool) Improved fs-repo-migrations tests by checking that the objects are the same and checking that garbage collection does not change anything. He also cleaned up sharness tests.
-@RichardLitt finished logging all existing `ipfs` commands for the HTTP API Spec. This means that if you have any questions about how the HTTP API should work, you can see them either in master or as open PRs to that issue. One step closer to a fully functional API...
42
+
*[**community**](//github.com/ipfs/community)
43
+
-@RichardLitt proposed using the new [GitHub Templates]() for IPFS. What do you think about this idea? Chime in [here](https://github.com/ipfs/community/issues/108).
44
+
- We now have [a list of community events](https://github.com/ipfs/community#events-calendar) for IPFS on the ipfs/community README. Do you have any that you'd like to add? Check out past events, too.
27
45
28
46
## Work in Progress
29
47
@@ -35,72 +53,146 @@ Here are some of the highlights for the [February 1st](//github.com/ipfs/pm/issu
35
53
36
54
## Contributors
37
55
38
-
Across the entire IPFS GitHub organization, the following people have committed code, created issues, or made a comment on GitHub between February 1st (noon, GMT) and February 8th. We're autogenerating this list using [this tool](//github.com/ipfs/weekly/blob/master/tools/get_commits.py) and [this other tool](//github.com/richardlitt/name-your-contributors), so please let us know if your name isn't here.
56
+
Across the entire IPFS GitHub organization, the following people have committed code, created issues, or made a comment on GitHub between February 1st (noon, GMT) and February 29th. We're autogenerating this list using [this tool](//github.com/ipfs/weekly/blob/master/tools/get_commits.py) and [this other tool](//github.com/richardlitt/name-your-contributors), so please let us know if your name isn't here.
Thanks, and see you next week! The more people mention items they want to see in the weekly there, the easier it is to make this and send it out.
195
+
This newsletter is also a community effort. If you have cool things to share for the next weekly, drop a comment about it in [the weekly repo](//github.com/ipfs/weekly! The more people mention items they want to see in the weekly there, the easier it is to make this and send it out.
0 commit comments