Where information is located

General organizational information / documents / brainstorms

We also have some organizational documents in a shared Google folder called “2i2c”. Your 2i2c address will give you access to this folder (or if you do not have access, please request it!):


The folder is organized into a few top-level folders that should be relatively self-explanatory, but don’t hesitate to ask for a quick guide.

Todos, project plans and management

2i2c uses the Projects page to keep track of the major projects that it is working on. That page has links to the location of project-specific to-do lists, deliverables, etc.

More organization-specific discussion and items we track can also be found in the private 2i2c meta repository.

Generally speaking the daily specifics of activity on a project are recorded outside of the team compass, as they are more dynamic. The important thing is that the team compass make it clear where to find this information, and that the information is kept up-to-date for all.

Marketing and communication

There are three main ways that 2i2c communicates with the outside world:

  • Twitter: @2i2c_org

    • Currently, there is nobody activately monitoring the Twitter account. We use it to post links to blog posts or major announcements in the newsletter.

  • Newsletter: using Mailchimp

    • Users sign up to the newsletter via our landing page’s contact form at 2i2c.org#contact. Email addresses are imported into Mailchimp for the newsletter.

  • Blog: [2i2c.org/blog]

    • The blog is managed by our Hugo website repository. All new posts are automatically sent to the mailing list on a weekly basis.


Who is invited to the Slack?

Currently, anyone who is interested can join the 2i2c Slack. Initially this is people that mentioned they would like to join via our blog post. Any Slack member is welcome to send an invite link to another person that would like to join.

Private vs. Public rooms in the Slack

There are a mix of private and public rooms in the Slack. In general, conversations about projects, development, etc should be in public rooms. Most conversation in the 2i2c Slack should be in public channels.

We’ll create private rooms for a few specific topics that probably warrant private conversation. By default, we’ll start with:

  • #partnerships - to discuss new partnerships with 2i2c

  • #recruiting - to discuss hiring with 2i2c

and eventually

  • #sales - to discuss new sales leads etc

Conversation about more sensitive topics like pursuing collaborations, sales, etc should be in a private room until it’s appropriate to start discussing in public channels. By default, all 2i2c staff, key volunteers, and founders will have access to all private rooms (it is only the “friends of 2i2c” and users that do not have access).

Code of Conduct

2i2c is still in the process of creating its Code of Conduct, so it does not have a 2i2c-specific CoC to apply to the Slack. In the meantime, all members of the 2i2c Slack must abide by the NumFocus Code of Conduct guidelines. If you wish to report a violation of this code of conduct in the 2i2c Slack, send an email to conduct@2i2c.org.


This section will be updated once 2i2c defines its own CoC and reporting infrastructure.

What rooms to use?

We try to keep the number of rooms to a minimum, and only add new rooms if it really feels necessary (e.g. if we keep having “off topic” conversations about the same topic in one room). Over time, we can revisit the Slack rooms that we use, and add / prune as needed.


We use the GitHub bots to track github issues that are relevant to Slack channels, and explore more integrations in the future. In general we should only use the bot to mirror comments if a repository is obviously always relevant to a channel. Otherwise, only mirror comments that are tagged with a particular label (e.g. #recruiting).