Ivy Apology

[pedromorgan]

I am suprised @ivy go-gomail#104

• I first even research other forks first.... cos an olde.darker.shade of grey hacker
• I created the go-mail org from our frustration/realisation, to try and move things forward, as maintainer missing The maintainer is missing.  go-gomail/gomail#104
• I forked it, into new "project/org", and then setup travis etc all..

And then I added @ivy as an "owner" moving forward..

• Adding you @ivy as owner was a bad idea in hindsight, maybe
• cos after a chat on gitter also.. but we agree idea is to maintain+future

once i was away..

• you removed me from gh-organisation, of go-mail and moving forward
• So "go-mail" is now completely yours, thanks for the hijack Thankz..
• I am reminded in future to avoid @ivy

So now you have gone off onto your own planet... which is fine..

• such as renaming namespace, big snag that one
• and renaming a project+function is not good et all..

But good luck, keep up with the rest of us and this project is now exactly what the original problem was.

Irony

• "owner" missing/uncontactable et all = @alexcesaro
• two owners and moving forward, need more
• @ivy removed owners, thanks.. Never been evicted before ;-)))

Good luck on your new independent maintainable fork,

• have fun and goodbye u hijacker and backstabber

[pedromorgan]

If u apologise, and change it back to gomail, then fine...

[theckman]

@pedromorgan have you considered reaching out to GitHub Support to report the malicious activity by @ivy?

[theckman]

@pedromorgan you can use this link to report @ivy for abuse, that way GitHub support can address it:

• https://github.com/contact/report-abuse?report=ivy+%28user%29

[ivy]

@pedromorgan Thank you for coming forward to talk about this. I appreciate that you care about this project. However, as it stands, gomail has been essentially dormant for the last two years. So far, I’ve made good progress in tackling some of the small the issues, but there's still a lot of work to be done. Removing you from the team was a difficult decision, however it wasn’t without reason. In just a couple hours you managed to break backwards compatibility, ruin perfectly good documentation, and trashed continuous integration so that every build was testing against Go 1.7 only.

Yes, I renamed the package. No, I don't believe it breaks compatibility. I've asked you a few times now to explain your reasoning and I'd still like to hear your justification now.

I also want to be clear that I'm not taking your project away from you. It isn't yours. It's the community's and if you still want to be involved I'll be more than happy to continue working with you.

I respect your feelings, and I realize now that the situation could've been handled more considerately. I would also like you to know that this wasn't personal, and it wasn't done with malicious intent. This project has a lot of potential and I want it to have its best chance to survive.

Sincerely,
Ivy

[theckman]

@ivy I really appreciate that you're wanting to take this project and make it better. Continuing the maintenance of a useful but unmaintained project is extremely important. I think the unfortunate issue is that it's not your project, and as a member of the Go community I don't personally want you trying to claim the project on our behalf.

@pedromorgan forked the project, and decided they were going to take the time to take the project the direction they want. They trusted you, and gave you power within the project to help them reach their goals. If you disagree with their actions, or the direction they are taking, create your own fork that is better and encourage people to use it.

Do not become a malicious actor trying to get what you want, it comes across as being petty and being unable to work constructively with others.

But you took that path, you committed yourself to malicious actions, and did things that will make people severely question if they can trust you as a project maintainer. You abused the trust that was given to you by someone else, so it makes me wonder if you are going to continue to make knee-jerk reactions like this? How can we trust you?

I'd love to work with someone who is passionate like you on my own personal projects, but what you did made it so that if we ever had the opportunity to collaborate together I would have a hard time trusting you. That's extremely unfortunate, and I'm sure it's not what you'd hoped to convey.

[pedromorgan]

Thankyou @theckman You have explained my feelings to the T.

[pedromorgan]

@ivy is cool though, there's energy in there ;-)

[pedromorgan]

Need to tweet this gem..

I respect your feelings, and I realize now that the situation could've been handled more considerately. I would also like you to know that this wasn't personal, and it wasn't done with malicious intent. This project has a lot of potential and I want it to have its best chance to survive.

[pedromorgan]

@theckman re its not abuse... but maybe it is..

I trusted @ivy thats the problem, Instead different actions completely

[theckman]

@pedromorgan The closest analogy that I can think of would be a hostile takeover of an IRC channel, where one of the channel operators goes rogue and removes the other operators due to a disagreement. In situations like that the network operators are often the ones who handle the situation, while treating the hostile takeovers of channels as abuse. This is why I was treating this as the same.

In this specific case, you'd replace channel operators with GitHub org owners. You'd replace the NetOps with GitHub Staff.

[cryptix]

@pedromorgan you resorted to quite a lot of namecalling in your initial issue. Also why didn't you answer any of @ivy' explanations? They seem reasonable without knowing any of the backstory here.

[ivy]

@theckman You can trust me, but I realize that I am going to have to earn that trust. I anticipate that it will take some time and it isn't going to be easy.

I am a team player, and I want to work with you all to make this project better. I can't however, do that if we aren't communicating. You'll see in the chat logs that I spent several hours trying to work with @pedromorgan without success.

Just because things didn't work out between @pedromorgan and I, doesn't mean that this situation will be the new norm. I would have chosen to work on another fork had @pedromorgan not offered me co-ownership. Forking again after our disagreement would have only served to distract this project more and add further confusion. I know that Pedro initially forked this project with the expectations of leading it, but ultimately, he did the opposite of that. I don't think it was intentional, but I made the choice to remove him from the organization, so the project could move forward.

[pedromorgan]

@cryptix look at this fork..
https://github.com/go-mail/mail/commits/v2

and go-gomail#104

@ivy is a bot

[ivy]

I want to be clear that even though I've closed the issue, I'm still willing to continue our discussion.

Edit: @pedromorgan, I'm a bot?

[pedromorgan]

discuss with who ?

[pedromorgan]

@ivy only question I have is..

1. what motives u for gomail
2. How many emails u sent with it
3. Can u cut and paste the new log here..