Skip to content
  • Block or report user

    Report or block RichardLitt

    Hide content and notifications from this user.

    Learn more about blocking users

    Contact Support about this user’s behavior.

    Learn more about reporting abuse

    Report abuse
1.2k followers · 174 following · 1.5k

Highlights

Organizations

@angular @readthedocs @LearnNavi @contribute-md @opensourcedesign @nodeschool @papers-we-love @mas-collective @BeagleLab @regexhq @nodejs @ipfs @LowResourceLanguages @libp2p @pitonneux @remarkjs @adventure-js @nock @ipld @multiformats @unifiedjs @sustainers @orbitdb @maintainers @in-development-ca @opensourcecities @micromark @foss-responders

Pinned

  1. standard-readme

    A standard style for README files

    Shell 3.2k 1k

  2. low-resource-languages

    Resources for conservation, development, and documentation of low resource (human) languages.

    TeX 233 46

  3. knowledge

    💡 document everything

    HTML 165 16

  4. mntnr/name-your-contributors

    Name your GitHub contributors; get commits, issues, and comments

    JavaScript 59 17

  5. ipfs/ipfs

    Peer-to-peer hypermedia protocol

    17.9k 1.2k

  6. k88hudson/git-flight-rules

    Flight rules for git

    33.8k 2.5k

1,371 contributions in the last year

Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Mon Wed Fri
Learn how we count contributions.
Less
More

Contribution activity

July 2020

Created a pull request in ssbc/patchwork that received 2 comments

feat: Change who to follow to whom to follow

See #1306. Changed in all relevant files.

+18 −18 • 2 comments

Created an issue in ssbc/patchwork that received 2 comments

Change "Who to follow" to "Whom to follow"

I happen to like using whom. I'm aware it's a silly, old word that is almost dead. But I like it, and "whom to follow" is the correct usage of the …

2 comments
3 contributions in private repositories Jul 4 – Jul 14

Seeing something unexpected? Take a look at the GitHub profile guide.

You can’t perform that action at this time.