Hi Stef, > You see you won.
I was NOT one of the people responding or pushing Guille. And I don't consider Artifact not on github and people on both sides upset as winning... > Peter when I say that I do not have time, I really mean it. That's why I try offer people help with the migration whenever possible -- it is usually easy and fast for me to do, as I already know what I am doing. Peter On Sat, Sep 29, 2018 at 12:49 PM Stephane Ducasse <[email protected]> wrote: > My last point on it. > if the philosophy is "I do not care about my software, but you have to > do it" then do not count me in. > > Stef > > On Sat, Sep 29, 2018 at 12:47 PM Stephane Ducasse > <[email protected]> wrote: > > > > You see you won. Guille removed its repo and I understand him. > > I will now count how many months it will take for having artefact > > working in P7. > > > > > > > > Peter when I say that I do not have time, I really mean it. I have two > > reports to write for end of september. > > Not counting that updated pharo by example could be build anymore and > > that we need it for the mooc starting > > 8th of october, not counting that we have 4 new people arriving in the > > team and many many other things. > > > > Stef > > On Sat, Sep 29, 2018 at 12:41 PM Peter Uhnak <[email protected]> wrote: > > > > > > Hi Stef, > > > > > > I understand that everyone is short on time, but I consider not > preserving the history problematic for two reasons > > > > > > * it is appropriating someone else's work as one's own -- this seems > borderline illegal, or at the very least in violation of MIT license > > > * 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. > > > > > > I've invested a ton of time to alleviate this process as much as > possible, and I can tell you for a fact that people are _really_ happy that > the authorship is preserved. > > > Not to mention that the history itself is valuable if you know how to > use it (and I very regularly look when a particular piece of code was > written when debugging issues). > > > > > > That being said, if you have issues with migrating or think that it > can be streamlined even further, > > > please let me know and I'd be happy to help you or streamline the tool > even further. > > > > > > Peter > > > > > > On Sat, Sep 29, 2018 at 10:23 AM Stephane Ducasse < > [email protected]> wrote: > > >> > > >> Hi guille > > >> > > >> I deeply appreciated that you spent your time to bring Artefact to > Pharo 70 > > >> and in general all the positive energy you put around Pharo. > > >> I love Iceberg! and more! > > >> > > >> I quit these mailing-lists in the past because of these little > > >> aggressions, the "You should do that" > > >> I registered today again to this mailing list just to publicly talk to > > >> you, while I could come to your office (I will do it too). > > >> > > >> I did a port of Artefact to Pharo 60 a while ago and started to fix > > >> Artefact aspects I did not like and I would like to integrate my fixes > > >> to yours. Please let me know where it is. :) > > >> > > >> I do not care of the history because I prefer the future. If people > > >> care then this is their duties. Easy. If they are not happy. This is > > >> THEIR PROBLEM. You see people often tells me that I cannot control and > > >> that github is decentralised. It is! So enjoy but @People try to avoid > > >> to piss on good will of others. > > >> > > >> Now sorry Norbert your point that Guillemo would be rude because he > spent > > >> his time to help Milton and made sure that Artefact in Pharo 70 is > clearly > > >> out of context and misplaced. You see I did the same in > > >> github.com/olivierauverlot because I needed it. And this is like > that. > > >> Period. > > >> You are not happy. This is ok. You do not like it. This is ok too. > > >> > > >> This is several times that I noticed that your are not nice with > > >> emails so do the same than me: think about the impact on others. You > > >> have no idea about what guille is doing and what it is paid for and > > >> this is certainly not to fix Artefact. And you may notice that we know > > >> what is to work on others unmaintained code because we do it all the > > >> time, we even create documentation on systems we do not understand > > >> because some people are too busy to write method and class comments so > > >> imagine documentation. > > >> > > >> So I would like to thanks again guille and I would like to have > > >> artefact on Pharo 70. > > >> > > >> Stef > > >> > >
