文件列表:

.travis.yml (217, 2023-06-28)
LICENSE (1072, 2023-06-28)
published/ (0, 2023-06-28)
published/001-2015-Dec.md (9009, 2023-06-28)
published/002-2016-Jan-5.md (4879, 2023-06-28)
published/003-2016-Jan-12.md (12903, 2023-06-28)
published/004-2016-Jan-25.md (10972, 2023-06-28)
published/005-2016-Feb-1.md (18637, 2023-06-28)
published/006-2016-March-7.md (16244, 2023-06-28)
published/006_cbase_deaddrop.jpeg (110731, 2023-06-28)
published/006_lgierth_fc00.jpg (36155, 2023-06-28)
published/006_station.png (128838, 2023-06-28)
published/007-2016-March-13.md (12718, 2023-06-28)
published/007_cbase_deaddrop.jpg (641035, 2023-06-28)
published/007_talk.png (1087001, 2023-06-28)
published/008-2016-March-21.md (10587, 2023-06-28)
published/008_webui.gif (6951965, 2023-06-28)
published/009-2016-March-28.md (17351, 2023-06-28)
published/009_lisbon.png (235151, 2023-06-28)
published/009_neo.jpg (76548, 2023-06-28)
published/009_orbit.png (152041, 2023-06-28)
published/010-2016-April-18.md (15950, 2023-06-28)
published/010_ipfs-boston.jpg (144370, 2023-06-28)
published/010_js-libp2p.png (97742, 2023-06-28)
published/010_orbit.png (169591, 2023-06-28)
published/011-2018-sep-26.md (6900, 2023-06-28)
published/012-2018-Oct-2.md (7457, 2023-06-28)
published/013-2018-oct-9.md (6789, 2023-06-28)
published/014-2018-oct-16.md (5344, 2023-06-28)
published/015-2018-oct-23.md (5495, 2023-06-28)
published/016-2018-oct-30.md (5945, 2023-06-28)
published/017-2018-nov-6.md (5931, 2023-06-28)
... ...

# Newsletter [](http://ipn.io) [](http://ipfs.io/) [](http://webchat.freenode.net/?channels=%23ipfs) [](https://github.com/ipfs/community/blob/master/CONTRIBUTING.md) Prepare and store our newsletter. - [Idea](#idea) - [Contribute](#contribute) - [This repo](#this-repo) - [Process for writing the Newsletter](#process-for-writing-the-newsletter) - [Styleguide & Suggestions](#styleguide-&-suggestions) ### [Subscribe to the IPFS Newsletter here.](http://eepurl.com/gL2Pi5) ## Idea Similar to the [Rust community's](https://this-week-in-rust.org/), we want to have a newsletter that talks about what was done in the past week by various contributors. This will help: - Keep people in the loop about what is going on at Protocol Labs and on IPFS. - Tell active contributors when new versions or tools are available. - Attribute developers who have contributed to open-source software related to IPFS. ## Contribute The Newsletter takes a _lot of work_. This work can best be done by being distributed. If you know of anything cool that happens in a given week, anything that other people might be excited about, add it to the newsletter by adding a comment about it to the PR or Issue for that week's newsletter. Here are the steps to do that: - See something cool, or make something cool. - Go to the open PR for that week's newsletter. - Add a comment about the thing. Add a link, if possible. - Revel in the knowledge you are great. Also, please help us out if you think the roundup could be better! [Open an issue!](https://github.com/ipfs/newsletter/issues/new) ## This repo - Stores the final versions for past newsletters, posted elsewhere - the blog, email, and so on; - Tracks issues related to the roundups in the [issues](https://github.com/ipfs/newsletter/issues/); - Stores tools used to make the roundups ### Process for writing the Newsletter - Open a Pull Request to create a new Markdown formatted file in the `published` folder. The naming format should be as in this example: `002-2016-jan-5.md`, for the newsletter of the sprint starting January 5th in 2016. - Collect feedback and iterate on the draft. - Images - Add files into published folder - Add using `-w` to ipfs - Use ipfs.io gateway to add files in - Merge it after: - Sign off from pertinent people - The travis build for the branch completes after each push. - Crosspost - [ipfs/ipfs#151](https://github.com/ipfs/ipfs/issues/151) - [the Blog](//github.com/ipfs/blog) - The IPFS Tinyletter, using `md2html` npm package to generate HTML - Twitter: post the blog link after it is merged and published. ### Styleguide & Suggestions - Use people's GitHub handles and not their real names. Example: @RichardLitt, and not "Richard Littauer". - Try and include everyone who has made a PR or commented on an issue. Often, issue comments are _major, pivotal_ contributions, and those should be captured! - Highlight, don't just summarize; a lot of work may be trivial, and higher signal is better noise. - In general, err on the side of giving credit to everyone involved. When people do the lion's share, mention them first. (Or even something like "@whyrusleeping and several others ... " if relevant. In the case of a release, you can link to the changelog which credits individually... but don't sweat this.) - In general, try linking larger phrases instead of single words. They're easier to notice and click on links. - In general, try highlighting _why_ something is cool. Call attention to things if 1. it is done and people should know about 2. there is a call to action -- opinions are needed. 3. it is specially useful to draw attention to something in the newsletter.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：