Add January 12 weekly #12

RichardLitt · 2016-01-12T20:18:52Z

24 hours feedback session starts now. :)

RichardLitt · 2016-01-12T20:25:36Z

Checked in with https://github.com/dkhamsing/awesome_bot/issues/44 concerning the SSL issue in the one link. Don't worry about it, all of the links in this PR are fine. cc @dkhamsing

eminence · 2016-01-12T20:27:40Z

drafts/2016-01-12.md

+
+## Contributors
+
+Across the entire IPFS GitHub organization, the following people have committed code since December 7th. (We're autogenerating this list using [this tool](//github.com/ipfs/weekly/pull/5), 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.


since December 7th.

THis should say January 4th

using [this tool]

Let's link to this instead:

//github.com/ipfs/weekly/blob/master/tools/get_commits.py

eminence · 2016-01-12T20:33:20Z

drafts/2016-01-12.md

+# 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).
+


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)

Sounds good to me. Want to test your powers?

Push successful! I didn't rebase/squash, though. Do you care?

I don't. Do you know how? Good to know, because in the future makes more sense to do so, I think.

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)

Cool. I am rebase and force push trigger happy, and I know it. So, I don't mind.

RichardLitt · 2016-01-12T22:03:53Z

This addresses #10

jbenet · 2016-01-13T00:49:43Z

drafts/2016-01-12.md

+## 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.


maybe add @chriscool to this thanks too-- he did most of the work i think?

jbenet · 2016-01-13T01:04:43Z

i think these things happened + worth sharing too:

(webui) The webui now has tests, and a better release process thanks to @dignifiedquire and @diasdavid. (( not sure if this was in last one ))
(archives) we are replicating the StackOverflow archive, thanks to @dignifiedquire
(gateway) the http://v04x.ipfs.io and http://v03x.ipfs.io transition gateways have gone live, thanks to @lgierth. (maybe instead of the other migration work note)
(community) http://project-repos.ipfs.io -- a project-wide repo dashboard with CI and issues -- went live, thanks very much to @harlantwood! (( this is correct, right @harlantwood? ))
(meetups) @NeoTeo, @whyrusleeping, and @diasdavid hosted a meetup in Copenhagen (-- pic if available?)

and maybe add a note about:

If you have cool things to share in this weekly, please make sure to post them in the next weekly sprint issue in the https://github.com/ipfs/pm repo.

eminence · 2016-01-13T02:02:12Z

I added some of these notes, thanks!

If anyone has details about the Copenhagen meetup, please share!

harlantwood · 2016-01-13T04:01:40Z

(community) http://project-repos.ipfs.io -- a project-wide repo dashboard with CI and issues -- went live, thanks very much to @harlantwood! (( this is correct, right @harlantwood? ))

Correct!

NeoTeo · 2016-01-13T10:29:44Z

No pics from Copenhagen event, alas.
We were all far too busy & excited to think about documenting it. We're just gonna have to redo it @whyrusleeping & @diasdavid...

eminence · 2016-01-13T14:27:38Z

pics aren't necessary, but if you had something specific you wanted to say, let me know (X number of people showed up, you hacked on IPFS, ate good food, toured the city, etc). Else I'll add something fairly generic like

@NeoTeo, @whyrusleeping, and @diasdavid hosted a small meetup in Copenhagen !

NeoTeo · 2016-01-13T14:31:02Z

For this particular meetup I'd say that is pretty accurate. We were eight in total, did a whirlwind intro of IPFS and followed up with a couple of hours of Q&A and general chatting.

RichardLitt · 2016-01-13T14:35:06Z

drafts/2016-01-12.md

+* [**(go-ipfs)**](//github.com/ipfs/go-ipfs) The IPFS Docker image is now tested automatically on Travis, thanks to [@ChristianKniep](//github.com/ChristianKniep), [@whyrusleeping](//github.com/whyrusleeping), and [@chriscool](//github.com/chriscool). For more, see the [go-ipfs#2064](//github.com/ipfs/go-ipfs/pull/2064) pull request.
+* [**(js-ipfs)**](//github.com/ipfs/js-ipfs) Now you can do `npm i -g js-ipfs` and use jsipfs (the javascript impl of IPFS) with bootstrap + id + version commands, fully compatible with the go-ipfs repo, thanks to [@diasdavid](//github.com/diasdavid)!
+* [**(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.
+* [**(community)**](//github.com/ipfs/community) A very cool [organization-wide dashboard](http://project-repos.ipfs.io/) that provides a status overview of all the IPFS repos.  By [@harlantwood](//github.com/harlantwood).


Link to github.com/ipfs/project-repos.

RichardLitt · 2016-01-13T14:35:33Z

Thanks for the help, @jbenet!

eminence · 2016-01-13T14:50:19Z

great stuff all. i think we are closing in on the final version for this week, so last call for reviews

rendered version

Add January 12 weekly

RichardLitt · 2016-01-13T20:52:02Z

Thanks everyone! This is awesome!

First draft of IPFS Weekly #12

RichardLitt mentioned this pull request Jan 12, 2016

Sprint January 11th ipfs/team-mgmt#79

Closed

RichardLitt force-pushed the feature/jan-12 branch from b9d231c to 811d528 Compare January 12, 2016 20:27

eminence reviewed Jan 12, 2016
View reviewed changes

Add January 12 weekly

38fd5fd

RichardLitt force-pushed the feature/jan-12 branch from 811d528 to 38fd5fd Compare January 12, 2016 20:29

eminence reviewed Jan 12, 2016
View reviewed changes

eminence added 2 commits January 12, 2016 15:39

Added link to the Jan 5th sprint issue in the PM repo

e148254

Include link to the latest preview of the new distributions page

6bba6b4

jbenet reviewed Jan 13, 2016
View reviewed changes

eminence added 2 commits January 12, 2016 20:57

Added some new notes based on feedback from jbenet

eac70e1

chriscool is cool too!

39224b7

RichardLitt reviewed Jan 13, 2016
View reviewed changes

eminence added 2 commits January 13, 2016 09:43

Add correct link to project-repos, not community

67585ec

Added note about Copenhagen meetup

56ff661

Small edits

edb17fe

RichardLitt added a commit that referenced this pull request Jan 13, 2016

Merge pull request #12 from ipfs/feature/jan-12

33940c2

Add January 12 weekly

RichardLitt merged commit 33940c2 into master Jan 13, 2016

RichardLitt deleted the feature/jan-12 branch January 13, 2016 20:50

jennwrites mentioned this pull request Oct 2, 2018

First draft of IPFS Weekly #12 #55

Merged

mikeal added a commit that referenced this pull request Oct 2, 2018

Merge pull request #55 from ipfs/renrutnnej-patch-1

0422f58

First draft of IPFS Weekly #12

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add January 12 weekly #12

Add January 12 weekly #12

RichardLitt commented Jan 12, 2016

RichardLitt commented Jan 12, 2016

eminence Jan 12, 2016

eminence Jan 12, 2016

eminence Jan 12, 2016

RichardLitt Jan 12, 2016

eminence Jan 12, 2016

RichardLitt Jan 12, 2016

eminence Jan 12, 2016

RichardLitt Jan 12, 2016

RichardLitt commented Jan 12, 2016

jbenet Jan 13, 2016

jbenet commented Jan 13, 2016

eminence commented Jan 13, 2016

harlantwood commented Jan 13, 2016

NeoTeo commented Jan 13, 2016

eminence commented Jan 13, 2016

NeoTeo commented Jan 13, 2016

RichardLitt Jan 13, 2016

RichardLitt commented Jan 13, 2016

eminence commented Jan 13, 2016

RichardLitt commented Jan 13, 2016


		## Contributors

		Across the entire IPFS GitHub organization, the following people have committed code since December 7th. (We're autogenerating this list using [this tool](//github.com/ipfs/weekly/pull/5), 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.

		# 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).

Add January 12 weekly #12

Add January 12 weekly #12

Conversation

RichardLitt commented Jan 12, 2016

RichardLitt commented Jan 12, 2016

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

RichardLitt commented Jan 12, 2016

Choose a reason for hiding this comment

jbenet commented Jan 13, 2016

eminence commented Jan 13, 2016

harlantwood commented Jan 13, 2016

NeoTeo commented Jan 13, 2016

eminence commented Jan 13, 2016

NeoTeo commented Jan 13, 2016

Choose a reason for hiding this comment

RichardLitt commented Jan 13, 2016

eminence commented Jan 13, 2016

RichardLitt commented Jan 13, 2016