Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

made edits to the "supporting" section #1721

Merged
merged 3 commits into from
May 7, 2018
Merged

made edits to the "supporting" section #1721

merged 3 commits into from
May 7, 2018

Conversation

rubymorillo
Copy link
Contributor

Hi team,

Per rubycentral/board#5, I'm proposing updates to the "Supporting" section that clarifies the role of each major sponsor of RubyGems.org. This is one part of an ongoing effort to update messaging across RubyGems and Ruby Together. Thanks!

@rubymorillo
Copy link
Contributor Author

cc @indirect

@sonalkr132
Copy link
Member

closing in favor of #1722

@sonalkr132 sonalkr132 closed this May 7, 2018
@indirect
Copy link
Member

indirect commented May 7, 2018

@sonalkr132 because many people have said they were confused or unsure about this, I think it's a good idea to put this new, clearer explanation into both the readme and the site footer 👍

@indirect indirect reopened this May 7, 2018
@indirect indirect merged commit f4ad75a into rubygems:master May 7, 2018
@sonalkr132
Copy link
Member

Sorry I took #1722 same as this because text was same. my bad!
Thanks @rubymorillo for updating readme as well.

@adarsh
Copy link
Contributor

adarsh commented May 8, 2018

Hey, just a note that I had already opened #1720 to address this issue and used the language we agreed to with @evanphx in this PR: rubycentral/board#8.

In the discussion above, I proposed agreeing on one set of language and using it consistently across all the places one would look for it.

As such, I'm going to resolve the conflict in PR #1720 and propose we use that language here specifically.

@dwradcliffe dwradcliffe deployed to production May 21, 2018 20:57 Active
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants