Skip to content
IPFS Team Planning, Management & Coordination threads
Branch: master
Clone or download
michaelavila Merge pull request #985 from ipfs/notes/20190603-go-core
Create 2019-06-03--go-core-dev-team-weekly.md
Latest commit 7bd27ac Jun 10, 2019

README.md

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

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

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.

IPFS planning in one picture

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 accross 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.

🙌🏽 IPFS Weekly Call 📞 (formerly known as IPFS All Hands Call)

This is a regular and reliable call where everyone who's working on any repository under the IPFS umbrella checks in and has a chance to either call attention to particular items, to make announcements, or to seek discussion of a topic. It's also a way for casual followers to get a high-level update on the pulse of the IPFS projects without having to follow all of the sprint calls. Newcomers are very welcome.

If you are interested in participating, please join us on Zoom.

You can find recordings of the on the Youtube playlist, IPFS All Hands 🙌🏽 📞

This call and other IPFS Community calls are tracked on the IPFS Community Calendar

If you are hosting a call for the first time or interested in learning how to do it, consult the HOST_A_CALL guide.

Weekly/BiWeekly Syncs of Working Groups, Special Interest Groups, and Related Projects

Calendar

You can consult all IPFS-related calls and events on the IPFS Community Calendar you can watch for events and sync to.

Chat

We hangout on IRC for lots of Dev Chat. You can find us on Freenode on the following channels:

  • #ipfs
  • #ipfs-dev
  • #ipfs-cluster
  • #ipfs-gui
  • #ipfs-in-web-browsers
  • #ipfs-project
  • #ipfs-infrastructure
  • #ipfs-package-managers
  • #ipfs-pinbot
  • #gx
  • #libp2p
  • #ipld

You can also access these channels through the Matrix IRC Bridge

Working Hours

As the IPFS team is all over the world, we've picked a set of "working hours" during which we can overlap. The hours are:

16:00-19:00 Z/UTC daily or
18:00-21:00 CEST daily or
12:00-15:00 EST daily or
09:00-12:00 PDT daily

We aim to be available during these hours. Your mileage may vary.

Timezone: UTC

All of our times are set according to the UTC timezone (or should be). This is much easier than adjusting times manually to accommodate different time zones, for a distributed team. If our calendar's location is set to Reykjavík, Iceland, it is because Iceland is always on UTC time. It is recommended that you know your timezone's difference from UTC for ease of scheduling. Sites like http://everytimezone.com can help with this..

Tools & Tutorials

Tools living in their own documents:

Zoom

We use Zoom for our community calls. This allows us to stream directly to YouTube (currently under maintenance), and to have calls with more than 25 users. Zoom may require a download before you are able to join. If you click on a Zoom link to a meeting room, it will automatically suggest the software to download. Please let us know if you have any issues with Zoom.

Note: Screen Sharing in Zoom under X11 requires compositor. Users of minimalist tiling window managers (i3, awesome, dwm) will share a "black screen" by default. The fix is to use third-party compositor, eg. Compton.

Contribute

Feel free to join in. All welcome. Open an issue!

This repository and all of our sprint calls fall under the IPFS Code of Conduct.

License

CC-BY-SA

You can’t perform that action at this time.