Filecoin Core Devs - What Should it Be?

[luckyparadise]

🚀 Future of Filecoin Core Devs – What Should It Be? 🚀

Why This Discussion?

Over time, participation in Filecoin Core Devs has declined, and there is uncertainty around its role compared to the Filecoin Implementers Working Group.

Rather than assuming what Core Devs should be, we should define what Core Dev means directly from those who participate (or want to participate):

• What does “Core Devs” mean to you?
• What should this group be responsible for?
• How should Core Devs be structured to make it useful for you?

What We Know

Current Ambiguity

• Some see Core Devs as a governance and decision-making group for protocol-level changes.
• Others view it as a space for technical discussion without decision-making power.
• The Implementers Working Group handles execution-focused discussions, but there’s overlap in participation and topics.

The Big Questions 🛠️

We need your direct input to shape what Core Devs should be going forward. Specifically:

1️⃣ What do you see as the role of Core Devs in the Filecoin ecosystem?
2️⃣ What structure or meeting format would make Core Devs useful for you?
3️⃣ How should we differentiate Core Devs from the Implementers Working Group?
4️⃣ What would drive better engagement and participation?

My Recommendation

I propose that we position Filecoin Core Devs as the technical core group and reference group for core development in the Filecoin ecosystem. This group would focus on:

• High-level technical direction and protocol improvements.
• Ensuring alignment across implementations.
• Serving as a central hub for technical decision-making and long-term roadmap discussions.

Meanwhile, the Implementers Working Group would focus on the practical aspects of building and maintaining implementations.

Call to Action

📢 This thread is for Core Devs and implementers to define the future of Core Devs.

If you have thoughts—even if you’ve never attended a Core Devs meeting before—drop a comment below.
Your input will directly influence how we move forward.

---

Add your thoughts below ⬇️

[Stebalien]

What does “Core Devs” mean to you?

Literally? The people building the protocol. In practice, the call includes many non-dev stakeholders. IMO, there needs to be a call containing (high-context/committed) stakeholders and devs, but maybe we should rename it to the FIP Committee call, or something like that? Or we can just accept that "core dev" means what it means, it's not a huge deal.

What should this group be responsible for?

Discussing FIPs (changes to the core protocol).

• Discussing the implementation tradeoffs.
• Discussing the economic/incentive/security impact.

IMO, there also needs to be a space to discuss tooling and the general ecosystem built around Filecoin, but that's too much to fit into a single call (there should be an Ecosystem call for that).

How should Core Devs be structured to make it useful for you?

1. Scheduled at a regular (reserved) time but convened on-demand whenever there's a new FIP and/or protocol improvement issue/question to discuss. Basically:
   1. A dev, member of the community, etc. submits a FIP and/or starts a pre-FIP discussion.
   2. A core dev proposes that this topic be brought up in a Core Dev's meeting.
2. Start with well-prepared presentations on the topics to be discussed with limited Q&A. After the presentations, we break out into separate rooms to discuss each topic unless there's too much overlap in participants.

I propose that we position Filecoin Core Devs as the technical core group and reference group for core development in the Filecoin ecosystem. This group would focus on:

• High-level technical direction and protocol improvements.
• Ensuring alignment across implementations.
• Serving as a central hub for technical decision-making and long-term roadmap discussions.

IMO:

1. We need to enable in-depth technical discussion about protocol improvements. Otherwise, devs won't show up because they won't get much use out of the meeting. I think we can avoid boring people by moving that discussion into breakout rooms.
2. For cross-implementation alignment, I think we should keep a regular implementer's sync call. This is a high-context call that doesn't involve stakeholders and/or protocol changes/direction.
3. I think this meeting should be used as a venue to discuss concrete proposals (given that a core-dev nominates the proposal for discussion) but, IMO:
   1. This isn't a great place for brainstorming (too many people).
   2. This is a good place to discuss concrete proposals that have already been posted and discussed async via the FIP discussion forum.

[masih]

What do you see as the role of Core Devs in the Filecoin ecosystem?

The role of Core Devs in the Filecoin ecosystem is crucial as they are the architects who ensure the stability, security, and evolution of the protocol. They should focus on long-term vision, code quality, and collaborative growth, working closely with other teams to align on priorities and longevity of the ecosystem.

What structure or meeting format would make Core Devs useful for you?

A meeting structure that could be beneficial might involve regular, scheduled sessions where Core Devs collaborate with other stakeholders, perhaps with dedicated time for roadmap alignment, brainstorming, and addressing pressing issues. Incorporating rotating leadership roles and guest facilitators could enhance diversity of thought.

How should we differentiate Core Devs from the Implementers Working Group?

For me this one is about scopes. Core Devs prioritise protocol design and foundational aspects, whereas the Implementers Working Group can focus on practical execution, optimisations, and application development, ensuring fluid communication channels between both. It is paramount for a tight feedback loop to exist between the two, as one cannot make effective impact without the other.

What would drive better engagement and participation?

Focusing on a product-driven approach that highlights practical use cases can be particularly effective. Encouraging contributors to work on real-world applications and challenges within the Filecoin ecosystem can make their efforts more tangible and impactful. Implement regular feedback sessions where contributors can share progress, discuss challenges, and propose solutions (i.e. a tight feedback loop). This not only keeps everyone aligned but also provides a platform for recognising achievements and encouraging experimentation.

---

In my humble opinion, the most effective attitude for Core Devs is of "Discovery." Core Devs should embrace a mindset focused on exploring new possibilities and innovative solutions to serve the community. Their role is to facilitate and nurture the exploration of pathways that lead to a more efficient and effective decentralised storage system for everyone, continuously pushing the boundaries of what is possible.