# What Github repos should we copy here?

**URL:** <https://discuss.ipfs.tech/t/what-github-repos-should-we-copy-here/26>\
**Category:** Site Feedback\
**Created:** [November 7, 2016, 5:20pm UTC](https://discuss.ipfs.tech/t/what-github-repos-should-we-copy-here/26 "2016-11-07T17:20:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dignifiedquire](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/dignifiedquire/32/8_2.png) [@dignifiedquire](https://discuss.ipfs.tech/u/dignifiedquire)\
**Post date:** [November 7, 2016, 5:20pm UTC](https://discuss.ipfs.tech/t/what-github-repos-should-we-copy-here/26/1 "2016-11-07T17:20:56Z")

</div>

As discussed before, some of the repos on [github.com](http://github.com) make sense to be consolidated into here.

Current ideas

- [ipfs/community](https://github.com/ipfs/community)
- [ipfs/faq](https://github.com/ipfs/faq)
- [ipfs/ipfs](https://github.com/ipfs/ipfs)

---

<div class="post-metadata">

**Author:** ![hector](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hector/32/178_2.png) [@hector](https://discuss.ipfs.tech/u/hector)\
**Post date:** [November 14, 2016, 5:54pm UTC](https://discuss.ipfs.tech/t/what-github-repos-should-we-copy-here/26/2 "2016-11-14T17:54:24Z")

</div>

Probably:

> **[ipfs-inactive/support](https://github.com/ipfs-inactive/support)**
>
> \[ARCHIVED\] For questions on how to get IPFS up and running smoothly - ipfs-inactive/support

---

<div class="post-metadata">

**Author:** ![flyingzumwalt](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/flyingzumwalt/32/12_2.png) [@flyingzumwalt](https://discuss.ipfs.tech/u/flyingzumwalt)\
**Post date:** [November 14, 2016, 6:21pm UTC](https://discuss.ipfs.tech/t/what-github-repos-should-we-copy-here/26/3 "2016-11-14T18:21:24Z")

</div>

There are some issues in ipfs/community that actually do belong in github, like planning and tracking work to create documentation.

There’s a parallel [discussion about consolidating the ipfs/community and ipfs/pm repositories into ipfs/ipfs](https://github.com/ipfs/community/issues/191), meaning that all of the issues that represent actual work to be done and tracked would move into that repo. Discussion here: [https://github.com/ipfs/community/issues/191](https://github.com/ipfs/community/issues/191)

---

<div class="post-metadata">

**Author:** ![hector](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hector/32/178_2.png) [@hector](https://discuss.ipfs.tech/u/hector)\
**Post date:** [November 15, 2016, 11:01am UTC](https://discuss.ipfs.tech/t/what-github-repos-should-we-copy-here/26/4 "2016-11-15T11:01:03Z")

</div>

This too:

> **[ipfs/apps](https://github.com/ipfs/apps)**
>
> Coordinating writing apps on top of ipfs, and their concerns. - ipfs/apps