-
Notifications
You must be signed in to change notification settings - Fork 34
Introducing new policies #225
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
title: Introducing New Policies for RubyGems.org | ||
layout: post | ||
author: Marty Haught | ||
author_email: marty@rubycentral.org | ||
--- | ||
|
||
We’re pleased to introduce several key policies for RubyGems.org for community review. These include a [Terms of Service](https://rubygems.org/policies/terms-of-service), [Privacy Notice](https://rubygems.org/policies/privacy), [Acceptable Use Policy](https://rubygems.org/policies/acceptable-use), and [Copyright Policy](https://rubygems.org/policies/copyright). While these policies align with how RubyGems has always operated, the absence of formal documentation created ambiguity around acceptable use. These new policies provide clarity and transparency regarding our operations, how we protect user data, and our commitment to maintaining a safe and respectful environment for all RubyGems users. | ||
|
||
[Terms of Service](https://rubygems.org/policies/terms-of-service) | ||
The Terms of Service define the rules and guidelines for using RubyGems.org. They cover everything from account responsibilities to intellectual property rights, ensuring a fair and consistent experience for all users. | ||
|
||
[Privacy Notice](https://rubygems.org/policies/privacy) | ||
Our Privacy Notice outlines how we collect, use, and safeguard your personal information. We’re committed to protecting your data and ensuring compliance with applicable privacy laws. | ||
|
||
[Acceptable Use Policy](https://rubygems.org/policies/acceptable-use) | ||
The Acceptable Use Policy sets clear expectations for behavior on our platform. It prohibits activities that could harm the service or other users, such as abuse, spam, or malicious actions. | ||
|
||
[Copyright Policy](https://rubygems.org/policies/copyright) | ||
Our Copyright Policy outlines the rules and procedures for handling copyright-related issues so that we ensure intellectual property rights are respected. | ||
|
||
These policies aim to improve transparency around our handling of user data and to guide how we will respond to situations where we may be required to take action to ensure a secure and trustworthy ecosystem for everyone. | ||
|
||
We encourage all users to review these policies. We are seeking feedback on these policies for the next 30 days. You can provide feedback through [legal@rubycentral.org](mailto:legal@rubycentral.org) email or the [\#oss-program-ruby-central](https://rubycentralcommunity.slack.com/archives/C08J92C73N1) channel in the Ruby Central Community Slack. After the 30-day comment period, we’ll review feedback and finalize the policies with a target effective date of May 20th, 2025\. Together, we can continue to build and contribute to a vibrant, safe, and secure Ruby community. | ||
|
||
Thank you for being a part of our journey\! |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
put these as headers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting the auto-conversion to markdown didn't do anything with them.