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

Re-add Iris #1137

Closed
wants to merge 1 commit into
from

Conversation

4 participants
@ghost

ghost commented Oct 17, 2016

I think you have to undo your previous commit, @dlsniper read your article's julien's comments and I hope you will understand... if not just close this PR, I will still no have any problem with you.

Re-add Iris
I think you have to undo your previous commit which you removed Iris you are not correct,and you know it, read mines and julien's (which you posted his project) comments to your/dlsniper blogpost below:  

https://plus.google.com/+JulienSchmidt1/posts/B37CUNVSEjZ
@appleboy

This comment has been minimized.

Show comment
Hide comment
@appleboy

appleboy Oct 17, 2016

Collaborator

You still editing git history to be only contributor while closing users' pull requests is really bad idea.

Collaborator

appleboy commented Oct 17, 2016

You still editing git history to be only contributor while closing users' pull requests is really bad idea.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Oct 17, 2016

@appleboy Who did a PR which actually used inside Iris, except me ? saw me the code please,

I hope I will be not the only contribution for a long time more but I'm so far, what's the problem exactly?

I'm getting very good messages every day from the Go Community, how I manage my project is up to me I think, So far I didn't disappointed the iris users

ghost commented Oct 17, 2016

@appleboy Who did a PR which actually used inside Iris, except me ? saw me the code please,

I hope I will be not the only contribution for a long time more but I'm so far, what's the problem exactly?

I'm getting very good messages every day from the Go Community, how I manage my project is up to me I think, So far I didn't disappointed the iris users

@kirillDanshin

This comment has been minimized.

Show comment
Hide comment
@kirillDanshin

kirillDanshin Oct 17, 2016

Collaborator

@kataras damn, do you really can't understand that you have huge community and only reasons of I develop iris for more than 7 months alone are that you're closing PRs, editing git history, editing issues and comments and removing third-party licenses? there is NO another reasons. and You saw some old PRs from version 1 when iris was based onnet/http , (iris is v4 based on fasthtttp), none of the (3) PRS with less than 5 lines of code exists in the project is NEVER be a reason to remove commit author from git history. and we all using git every day and we still smart enough to see that you editing git history and it can't be a local issues with my git.

Collaborator

kirillDanshin commented Oct 17, 2016

@kataras damn, do you really can't understand that you have huge community and only reasons of I develop iris for more than 7 months alone are that you're closing PRs, editing git history, editing issues and comments and removing third-party licenses? there is NO another reasons. and You saw some old PRs from version 1 when iris was based onnet/http , (iris is v4 based on fasthtttp), none of the (3) PRS with less than 5 lines of code exists in the project is NEVER be a reason to remove commit author from git history. and we all using git every day and we still smart enough to see that you editing git history and it can't be a local issues with my git.

@ghost ghost closed this Oct 17, 2016

@kirillDanshin

This comment has been minimized.

Show comment
Hide comment
@kirillDanshin

kirillDanshin Oct 17, 2016

Collaborator

Really? I'm locked that conversation because it was merged and all discussion needs a new issue or PR. what you can say about, for example, kataras/iris#219 and kataras/iris#230?
also I did used iris before. than I got a panic inside, start looking in issues and I saw that issues. it really means that you do not respect contributors and iris' users. and it isn't awesome. you've ignored the licenses twice and it means that you did it specially.

Collaborator

kirillDanshin commented Oct 17, 2016

Really? I'm locked that conversation because it was merged and all discussion needs a new issue or PR. what you can say about, for example, kataras/iris#219 and kataras/iris#230?
also I did used iris before. than I got a panic inside, start looking in issues and I saw that issues. it really means that you do not respect contributors and iris' users. and it isn't awesome. you've ignored the licenses twice and it means that you did it specially.

@kirillDanshin

This comment has been minimized.

Show comment
Hide comment
@kirillDanshin

kirillDanshin Oct 17, 2016

Collaborator

even if the code isn't there, git history will stay with their names and commits, not yours.

Collaborator

kirillDanshin commented Oct 17, 2016

even if the code isn't there, git history will stay with their names and commits, not yours.

@dlsniper

This comment has been minimized.

Show comment
Hide comment
@dlsniper

dlsniper Oct 17, 2016

Contributor

@kataras I've sent that PR because this commit: kataras/iris@5c98c5a#diff-9879d6db96fd29134fc802214163b95aL23 basically removed those third-party licenses (again).
Also from the Github history it shows that some people did manage to get their PRs merged but you still denied them the contribution on how the project by flattening the history and not naming them.
Just disable the PRs section if you don't want people to send PRs to any of your projects.
But given how you conduct yourself here, it seems I was right about the project leadership.

I truly am sorry that for all the efforts you are putting in the project you cannot understand simple, basic, requirements. And this time around you cannot blame English on this, like it happened last time.

Contributor

dlsniper commented Oct 17, 2016

@kataras I've sent that PR because this commit: kataras/iris@5c98c5a#diff-9879d6db96fd29134fc802214163b95aL23 basically removed those third-party licenses (again).
Also from the Github history it shows that some people did manage to get their PRs merged but you still denied them the contribution on how the project by flattening the history and not naming them.
Just disable the PRs section if you don't want people to send PRs to any of your projects.
But given how you conduct yourself here, it seems I was right about the project leadership.

I truly am sorry that for all the efforts you are putting in the project you cannot understand simple, basic, requirements. And this time around you cannot blame English on this, like it happened last time.

@kirillDanshin

This comment has been minimized.

Show comment
Hide comment
@kirillDanshin

kirillDanshin Oct 17, 2016

Collaborator

@kataras I saw the f*... LICENSE and I saw these names WAS NOT inside and of course I didn't because you've added it only 17 hours ago.

screen shot 2016-10-17 at 10 02 47

Collaborator

kirillDanshin commented Oct 17, 2016

@kataras I saw the f*... LICENSE and I saw these names WAS NOT inside and of course I didn't because you've added it only 17 hours ago.

screen shot 2016-10-17 at 10 02 47

@kirillDanshin

This comment has been minimized.

Show comment
Hide comment
@kirillDanshin

kirillDanshin Oct 17, 2016

Collaborator

awesome. @kataras is now @geramaro. fukken awesome.

Collaborator

kirillDanshin commented Oct 17, 2016

awesome. @kataras is now @geramaro. fukken awesome.

@dlsniper

This comment has been minimized.

Show comment
Hide comment
@dlsniper

dlsniper Oct 17, 2016

Contributor

@kirillDanshin I think that's the point, he will not play by the rules unless he's called upon. The article he's referring to seems to have been read by a few people and it seems he would do anything to have a good image / stars on Github but otherwise wouldn't care.

From my point of view I think that we've just witnessed how the ecosystem was just broken by the latest rename of @kataras -> to @geramaro and this makes it too unstable to be used in any public usage.

@kirillDanshin if he cannot use a nice language, please don't go down to his level. Thank you.

Contributor

dlsniper commented Oct 17, 2016

@kirillDanshin I think that's the point, he will not play by the rules unless he's called upon. The article he's referring to seems to have been read by a few people and it seems he would do anything to have a good image / stars on Github but otherwise wouldn't care.

From my point of view I think that we've just witnessed how the ecosystem was just broken by the latest rename of @kataras -> to @geramaro and this makes it too unstable to be used in any public usage.

@kirillDanshin if he cannot use a nice language, please don't go down to his level. Thank you.

@kirillDanshin

This comment has been minimized.

Show comment
Hide comment
@kirillDanshin

kirillDanshin Oct 17, 2016

Collaborator

he almost fuck'd up a huge number of applications with their rename. he's back again.

Collaborator

kirillDanshin commented Oct 17, 2016

he almost fuck'd up a huge number of applications with their rename. he's back again.

@dlsniper

This comment has been minimized.

Show comment
Hide comment
@dlsniper

dlsniper Oct 17, 2016

Contributor

@kirillDanshin Please lock up the conversation, this is going nowhere, fast.

Contributor

dlsniper commented Oct 17, 2016

@kirillDanshin Please lock up the conversation, this is going nowhere, fast.

@dlsniper

This comment has been minimized.

Show comment
Hide comment
@dlsniper

dlsniper Oct 17, 2016

Contributor

and I would not be called names. If you can't have the decency to have a normal dialog, them I'm out.

Contributor

dlsniper commented Oct 17, 2016

and I would not be called names. If you can't have the decency to have a normal dialog, them I'm out.

@kirillDanshin

This comment has been minimized.

Show comment
Hide comment
@kirillDanshin

kirillDanshin Oct 17, 2016

Collaborator

yep, we're all saw this. thanks, iris now banned. good bye, @kataras.
@appleboy, @dlsniper thanks.

Collaborator

kirillDanshin commented Oct 17, 2016

yep, we're all saw this. thanks, iris now banned. good bye, @kataras.
@appleboy, @dlsniper thanks.

Repository owner locked and limited conversation to collaborators Oct 17, 2016

This issue was closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.