There are several major sources of information within 2i2c:
Documentation¶
The most stable form of information in 2i2c is documentation that our teams maintain. This is where most information about 2i2c exists.
See External documentation and their owners for information about documentation at 2i2c.
Google Drive¶
We have a Shared Google Drive that contains all of 2i2c’s documents that don’t fit into GitHub. It is accessible to everybody at 2i2c, using your @2i2c.org account.
It is called 2i2c Team Drive and should be accessible on the left under Shared Drives.
Google Drive doesn’t let you link to a Shared Drive directly, so here’s a link to the Engineering folder in the drive.
Navigate up one folder to find the Share Drive root.
Public GitHub Issues¶
Most of our conversations, planning, and work tracking happens in GitHub. See 2-week iterations with “Accountable Kanban” - Our default process for more information.
Private GitHub Issues¶
There are a few repositories that we use for tracking private conversations and issues. This is usually personally sensitive or identifiable information, or information that needs to be private until decisions or deals are finalized.
2i2c-org/meta: Private team and organizational conversation.
Data repositories¶
We maintain two repositories that publish snapshots of 2i2c’s data on a daily schedule, so that other tools and repos can consume them without hitting upstream APIs.
2i2c-org/data: Public data about 2i2c’s infrastructure and services (e.g. cloud usage, MAUs). Datasets are published as GitHub Releases and rendered as a browsable docs site.2i2c-org/data-private: Private financial data (Sage Intacct accounting, HubSpot deals). Datasets are published as GitHub Releases and to Google Sheets.
Each repository’s README describes the datasets it contains and how to download them from another repo.