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

Non developer readme contribution #3398

Merged

Conversation

denineguy
Copy link
Contributor

I have written a clear, easy-to-comprehend introduction for technologyRepo. I believe this introduction, free of complex technical terms, will swiftly and thoroughly inform anyone about the use-cases, merit, and advantages, including the celebrated features, of technologyRepo. Seasoned developers, new programmers, and even nontechnical visitors will benefit from the clear language, exposing technologyRepo to a broader range of users.

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

@denineguy denineguy closed this Feb 10, 2016
@denineguy denineguy reopened this Feb 10, 2016
@denineguy
Copy link
Contributor Author

@jnandez1986 can you please confirm that you were also and author on this pull request and that you are okay with these commits being contributed to google

@denineguy
Copy link
Contributor Author

I did author these commit, but there may have been and issue where I accidentally used an incorrect email address. I tried to resolve that by adding the correct email as the author which is denineguy@gmail.com and is the only email I will use for my github account.

@jnandez1986
Copy link

where do I confirm?

@denineguy
Copy link
Contributor Author

@jnandez1986 just add your confirmation in the comments

@jnandez1986
Copy link

I confirm

@denineguy
Copy link
Contributor Author

@jnandez1986 https://github.com/jnandez1986 has confirmed in the comments
that he was an author on this pull request and that he is okay with these
commits being contributed to google. Also I did author these commit, but
there may have been and issue where I accidentally used an incorrect email
address. I tried to resolve that by adding the correct email as the author
which is denineguy@gmail.com and is the only email I will use for my github
account.

On Tue, Feb 9, 2016 at 8:54 PM, googlebot notifications@github.com wrote:

We found a Contributor License Agreement for you (the sender of this pull
request) and all commit authors, but as best as we can tell these commits
were authored by someone else. If that's the case, please add them to this
pull request and have them confirm that they're okay with these commits
being contributed to Google. If we're mistaken and you did author these
commits, just reply here to confirm.


Reply to this email directly or view it on GitHub
#3398 (comment).

Denine N. Guy

denineguy@gmail.com

Connect with me on LinkedIn! http://goog_21599870
http://www.linkedin.com/in/denineguy

@tjsavage
Copy link
Contributor

Thanks @denineguy and @jnandez1986 for the PR! I think it's a good point that the README should include a more easy-to-comprehend overview of how the library works. We can use this as a solid starting point and maybe make a few tweaks on top. Would you mind squashing the commits a bit (and perhaps rebasing onto the latest master)?

@denineguy denineguy force-pushed the non-developer-readme-contribution branch from ceefc02 to 43cf693 Compare February 18, 2016 17:54
@googlebot
Copy link

CLAs look good, thanks!

@denineguy denineguy force-pushed the non-developer-readme-contribution branch from 43cf693 to 0729cef Compare February 18, 2016 18:01
@denineguy
Copy link
Contributor Author

@tjsavage I have squashed the commits and rebased onto the laster master. Thanks

@tjsavage
Copy link
Contributor

Thank you!

tjsavage pushed a commit that referenced this pull request Feb 24, 2016
@tjsavage tjsavage merged commit 83548a7 into Polymer:master Feb 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants