Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add January 12 weekly #12

Merged
merged 8 commits into from
Jan 13, 2016
Merged

Add January 12 weekly #12

merged 8 commits into from
Jan 13, 2016

Conversation

RichardLitt
Copy link
Member

24 hours feedback session starts now. :)

@RichardLitt
Copy link
Member Author

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


## 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since December 7th.

THis should say January 4th

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

using [this tool]

Let's link to this instead:

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

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

Copy link
Contributor

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)

Copy link
Member Author

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?

Copy link
Contributor

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?

Copy link
Member Author

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.

Copy link
Contributor

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)

Copy link
Member Author

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.

@RichardLitt
Copy link
Member Author

This addresses #10

## 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@jbenet
Copy link
Member

jbenet commented Jan 13, 2016

i think these things happened + worth sharing too:

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
Copy link
Contributor

I added some of these notes, thanks!

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

@harlantwood
Copy link

(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
Copy link

NeoTeo commented Jan 13, 2016

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
Copy link
Contributor

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
Copy link

NeoTeo commented Jan 13, 2016

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.

* [**(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).
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@RichardLitt
Copy link
Member Author

Thanks for the help, @jbenet!

@eminence
Copy link
Contributor

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

rendered version

RichardLitt added a commit that referenced this pull request Jan 13, 2016
@RichardLitt RichardLitt merged commit 33940c2 into master Jan 13, 2016
@RichardLitt RichardLitt deleted the feature/jan-12 branch January 13, 2016 20:50
@RichardLitt
Copy link
Member Author

Thanks everyone! This is awesome!

awesome

mikeal added a commit that referenced this pull request Oct 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants