Thanks norbert. I accept your apologies. Stef On Sat, Sep 29, 2018 at 8:39 PM Stephane Ducasse <stepharo.self@gmail.com> wrote:
Hi Peter
Just a note to say that I appretiate your attitude and we know it each other. I will try to use your tool when I will migrate my projects.
Stef
On Sat, Sep 29, 2018 at 2:32 PM Peter Uhnak <i.uhnak@gmail.com> wrote:
- you're stealing
Sorry, I absolutely did not intend the evoke the notion of "stealing". My perspective is... I am spending time to migrate someone else's code, so the last thing I want is someone burning my energy and complaining that I voided their contribution.
I don't give a fuck if someone migrates my contribution and strips the authorship (and when I do care I don't need to rely on others to prove it). But I want to cover my ass from backlash from other people, because I know it will happen and I know that people will complain (which is exactly what happened to you).
So preventing the appropriation of code is not about you taking credit for other person's code, but you being covered from them accusing you of it. (It probably sounds like I am pathologically defensive, but dealing with people is exhausting for me.)
* it is sending bad signals to potential contributors that we can scrub them anytime we want
as you yourself have said:
@People try to avoid to piss on good will of others. Yet this is what it feels like to some when traces of their contributions are voided.
And this is my third point. This "stealing" idea is mainly a matter of manners.
Again, I didn't intend "stealing". It's about preventing people from thinking "They don't give a fuck about their contributors, so why I should give a fuck about contributing?". It can be dispiriting for them, even if they don't care about the code itself. And they will complain... and who needs that?
If instead of bashing on people, we wanted to discuss on how to actually FIX the thing, here are my 2 cents: - From a copyright perspective it should have been enough to check the licence file and name the contributors there
But nobody uses the license file for that, usually there's only the original author(s) / main maintainer(s). That's why the (git) history is relevant.
- The history could have been retrieved in a separate branch and then merged (and look, we had the best of the two worlds!)
- both of the things could have been then integrated through a pull request (luckily in less than one hour :))
Yep.
And at the end, with the apport of everybody we could have got a repository with history, baseline and working on pharo 7.
Now, from a human perspective, please let's try everybody to assume the best of the other by default. That will just make all interactions much more healthy.
And please, this is not particularly directed to anybody, I've seen such remarks many times. Let's just think positive. Problems can be fixed if we talk about them, but more specifically if we are looking for solutions.
I will see how I can streamline the tool even further... maybe a service that will migrate entire smalltalkhub :)
Peter