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

Update README.md #10

Closed
wants to merge 2 commits into from
Closed

Update README.md #10

wants to merge 2 commits into from

Conversation

shawnps
Copy link
Contributor

@shawnps shawnps commented Sep 15, 2016

No description provided.

@cfdreddbot
Copy link

Hey shawnps!

Thanks for submitting this pull request!

All pull request submitters and commit authors must have a Contributor License Agreement (CLA) on-file with us. Please sign the appropriate CLA (individual or corporate).

When sending signed CLA please provide your github username in case of individual CLA or the list of github usernames that can make pull requests on behalf of your organization.

If you are confident that you're covered under a Corporate CLA, please make sure you've publicized your membership in the appropriate Github Org, per these instructions.

Once you've publicized your membership, one of the owners of this repository can close and reopen this pull request, and dreddbot will take another look.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/130427991

The labels on this github issue will be updated when the story is started.

@emalm
Copy link
Member

emalm commented Sep 15, 2016

Thanks, @shawnps! Actually, as is stated elsewhere in the README, the preferred import path for this package is code.cloudfoundry.org/bytefmt, so https://godoc.org/code.cloudfoundry.org/bytefmt is the corresponding Godoc URL. Would you mind amending your PR to reflect that? Given the scope of the change, we would prefer that you squash that to a single commit.

Also, I'm afraid we need you to sign and submit a Cloud Foundry Foundation CLA, or to publicize your membership in a GitHub organization that has signed such a CLA, before we can accept your change.

Thanks,
Eric, CF Runtime Diego PM

@shawnps
Copy link
Contributor Author

shawnps commented Sep 18, 2016

@ematpl probably easier for you or someone else to make the change since it's just a link in the README (that CLA is really long and scary)

@shawnps shawnps closed this Sep 18, 2016
@shawnps shawnps deleted the patch-3 branch September 18, 2016 14:21
@emalm
Copy link
Member

emalm commented Sep 18, 2016

Thanks, @shawnps, I've updated the README with the correct URL myself, and corrected a few other typos. Sorry to hear you found the individual CLA intimidating: it's there for as much for your protection as it is for the Foundation's.

Best,
Eric

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
4 participants