Skip to content

project proposal: Searchable Linkable Open Public Indexed (SLOPI) Communication #23

@pdurbin

Description

@pdurbin

After talking the idea out a bit at https://gitter.im/good-labs/community?at=5ccf1cbd6a84d76ed84dc3fb I'm submitting the following proposal as project. A pull request is on its way.

Searchable Linkable Open Public Indexed (SLOPI) Communication

What is it?

Messages written in the SLOPI (pronounced "sloppy") communication style are:

  • Searchable: Messages can be found using Google or other search engines.
  • Linkable: Messages have a permalink.
  • Open: Messages are in the open.
  • Public: Messages are public.
  • Indexed: Messages are indexed by search engines.

This phrasing, especially with regard to messages being searchable and linkable, is inspired by the discussion criteria of Core Infrastructure Initiative (CII) Best Practices program.

Examples of communication tools that support the SLOPI style include:

  • mailing lists with public archives
  • Gitter
  • IRC channels with public logs
  • XMPP rooms with public logs

While open source projects should endeavor to communicate in the SLOPI style whenever possible, this style is inappropriate for security, code of conduct violations, and telling co-workers on your floor that you brought in donuts.

The SLOPI style can take some getting used to if you are new to open source culture. It's ok to be a little sloppy. Please don't worry if the message you send isn't perfect. The fact that you sent it in the open is appreciated. Open source is getting friendlier. A thick skin isn't as necessary as it was in the past.

Why do we need it?

Open source projects are adopting Slack, forgetting the importance of public and open communication. How can your users and contributors know what you're thinking if the majority of discussion and decision making is done in Slack? Did you forget that you have a mailing list with public archives? Have you considered chat tools that support a SLOPI communication style?

Project Plan

  • Tell success stories of projects that have adopted a SLOPI communication style as positive role models. Link to the various tooks they use.
  • List alternatives to Slack that are SLOPI, such as Gitter, logged IRC channels, and logged XMPP rooms.
  • List blog posts that have made the argument that Slack is bad for open source.

Resources

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions