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

Fixing spelling mistake in README #35

Closed
wants to merge 1 commit into from
Closed

Fixing spelling mistake in README #35

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Mar 30, 2017

Nothing fancy. Just fixing a small spelling mistake.

@ottman
Copy link
Member

ottman commented Mar 30, 2017

Thanks! Can you message me on Minds.com/ottman?

@strk
Copy link

strk commented Apr 19, 2017

Does it really take a real-time chat to merge a typo fix ?
As 20 days have gone already, I'm wondering about the health of the Minds development community.

@strk
Copy link

strk commented Jun 4, 2017

Funny, got here to find if another issue was reported for the README and this PR is still not merged. I guess it is not worth to report the other issue ? Is it @ottman ?

@markharding
Copy link
Member

Thanks! We will merge when we have finalized our contributor agreement.

@markharding
Copy link
Member

@fadelardi Please can you sign https://docs.google.com/document/d/1bFZ1nQhOkvNKxD2ApHKigsFScy3GGQhMYY_batZl8rw/edit?usp=sharing ?

@ghost
Copy link
Author

ghost commented Jun 23, 2017

I'm sorry, what...?

Three months ago I fixed a small typo in a README file. I was asked to sign up for minds.com, which really wasn't necessary, and I disliked associating my professional life github profile to an online identity in a social platform, but I still went ahead with it. Now I get a link to a gdoc file asking for all my personal information which I'm not really sure why you should have, or what you intend to do with it. All this for fixing a word in a file that no one really seems concerned about. I'm sorry, but no.

How about I close this PR and you guys fix it yourselves, it's pretty simple:

prodution -> production

@strk
Copy link

strk commented Jun 23, 2017 via email

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.

4 participants