# IPFS Implementer's Sync

**URL:** <https://discuss.ipfs.tech/t/ipfs-implementers-sync/14826>\
**Category:** Working Groups & Communities\
**Created:** [July 24, 2022, 11:49pm UTC](https://discuss.ipfs.tech/t/ipfs-implementers-sync/14826 "2022-07-24T23:49:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![BigLep](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/biglep/32/5869_2.png) [@BigLep](https://discuss.ipfs.tech/u/BigLep)\
**Post date:** [July 24, 2022, 11:49pm UTC](https://discuss.ipfs.tech/t/ipfs-implementers-sync/14826/1 "2022-07-24T23:49:10Z")

</div>

This is a pointer to the bi-weekly implementer’s sync that happens for those investing, creating, and maintaining [IPFS implementations](https://docs.ipfs.io/basics/ipfs-implementations/). It’s a forcing function to make sure [IPFS specs](https://github.com/ipfs/specs) and [IPIPs](https://github.com/ipfs/specs/blob/main/IPIP/0001-lightweight-improvement-proposal-process.md) are being reviewed and engaged with by key stakeholders of IPFS.

In future this may move to Discourse, but for now is [here](https://www.notion.so/IPFS-Implementers-Working-Group-778357b505cf4e0389124121a9c4afde?pvs=4).

---

<div class="post-metadata">

**Author:** ![BigLep](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/biglep/32/5869_2.png) [@BigLep](https://discuss.ipfs.tech/u/BigLep)\
**Post date:** [September 24, 2024, 12:02am UTC](https://discuss.ipfs.tech/t/ipfs-implementers-sync/14826/2 "2024-09-24T00:02:17Z")

</div>

@lidel : I assume this is on hold currently? I couldn’t find record of it at [IPFS Community Calendar · Events Calendar](https://lu.ma/ipfs)

---

<div class="post-metadata">

**Author:** ![lidel](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/lidel/32/9853_2.png) [@lidel](https://discuss.ipfs.tech/u/lidel)\
**Post date:** [September 24, 2024, 12:35pm UTC](https://discuss.ipfs.tech/t/ipfs-implementers-sync/14826/3 "2024-09-24T12:35:18Z")

</div>

Correct, [Luma shut down recurring events feature](https://help.lu.ma/p/helpart-Zn5XmZCzcTConAH/multi-session-events) and we did not reinstate sync call post-[nucleation](https://protocol.ai/blog/introducing-protocol-labs-venture-studio/), waiting for foundation, new teams and companies to re-solidify.

Open to discuss reinstating sync call if more than one entity is willing to share responsibility of running it.

In the meantime, async channels can be used:

- Filling issue at [Issues · ipfs/specs · GitHub](https://github.com/ipfs/specs/issues/)
- Starting thread in `#ipfs-implementers` at [https://docs.ipfs.tech/community/#chat](https://docs.ipfs.tech/community/#chat)