开源软件名称：

开源软件地址：

开源编程语言：

开源软件介绍：

IPFS Team Planning, Management & Coordination threads

tl:dr: We have a weekly call on Mondays. The time, date and other info for each week's call is announced in an issue in this repository. Propose agenda items for the call by commenting on the issue!

Repo Index

• Related Projects
• How We Work Together
• Teams, Roles & Structures
• Asynchronous Communitication
  • Project & Working Groups Roadmaps
  • OKR (Objectives & Key Results)
  • Tracking Repo Activity
• Synchronous Communication
  • Weekly All Hands
  • Working Groups Weekly/BiWeekly Syncs
  • Calendar
  • Chat
  • Working Hours
  • Timezone: UTC
• Tools & Tutorials
  • Lead Maintainer Protocol
  • Host a Call
  • Coordination Toolkit
  • How to create a Roadmap
  • Resources for Distributed Teams
  • Zoom
• Contribute
• License

Related Projects

IPFS leverages several related projects that each have their own planning:

• IPLD
• libp2p

How We Work Together

We use a loose agile approach. We deliberately designed a Org wide process that is very flexible, enabling each team to design an internal coordination strategy that suits their project needs, while keeping a baseline for team wide coordination around Project Wide Roadmapping and OKRs.

You might hear these terms "Working Group Roadmap", "Project Roadmap", "OKRs", "Metrics" and so on be thrown around often. If you are puzzled in how these all fit together and what is the best resource to look at, we've created the following diagram to illustrate how all of these fit together for the IPFS org.

If you are new around here, the best way to get onboarded is to focus on the "Day to Day Operations" as it will help you meet the Working Groups, understand what their top priorities for the week are, and identify more quickly places where you can contribute. Later, you can go through all the Quarterly OKRs and Yearly Planning so that you understand fully the decisions you see being made.

You can also learn more about operating in Distributed Teams at our 'Distributed Teams' Document, containing resources on tools, decision making, process and more. We have been gathering, reviewing, discussing and experimenting with many overtime and will continue to do so as we find new needs.

Teams

Meet the current Working and Research Groups at the TEAMS_ROLES_STRUCTURES document.

Asynchronous Communication

As an organization that operates at a planetary scale with multiple people from different timezones and schedules, we value tremendously the benefits of Asynchronous Communication. The art of writting things down for future selfs or future contributors is one of the key reasons that enables so many contributors to participate in the large endeavour of Distributing the Web with the IPFS Project.

Some golden recommendations:

• Prefer opening an issue vs. sending a DM
• If you find documentation missing, treat it as a bug. Once you get your answer, contribute it so that it benefits others
• Use synchronous time wisely (only if needed), convert any output into an artifact that can be used by others (avoid Tribal Knowledge)

Project & Working Groups Roadmaps

The IPFS Project & Working Group Roadmaps serve as the north star for our quarterly planning process and org alignment. You can read these at https://github.com/ipfs/roadmap

OKRs

Learn how the IPFS Org uses OKRs to track quarterly process here.

Tracking Repo Activity

We recommend trying using Octobox as a way to keep up to date with different issues, tags, notifications and so on across Github.

Synchronous Communication

Synchronous Communication is phenomenal to transfer memes rapidly, clarify any outstanding questions, deep dive into hard topics together, get to know each other better and develop trust. The main pain point with Synchronous Communication is that if you were not present, you might miss out on important information that is relevant to you and your project. To overcome this limitation, a core competency of the IPFS Org as a whole is to be stellar at taking notes and creating artifacts that represent any decision/announcement made during those synchronous conversations. The corollary being: if it ain't written down and broadcasted, it didn't happen.