On Mon, 15 May 2017 15:09:26 -0400 "William L. Thomson Jr." <wlt...@o-sinc.com> said:
> On Tue, 16 May 2017 02:45:26 +0900 > Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote: > > > > I addressed a bug report on IRC. I can do whatever I like in our > > repos. I build ecrire from our git. After the report I tried it on > > Wayland. It crashed I fixed it. I pushed the fix. Telling me I cannot > > do that is not your place. > > Um NO! Do you think I'm saying what you did... or what I did... because I do believe the above is very clear on what *I* did... the below then goes on to talk about something totally different... what *YOU* did. Are you wanting to tell me "No that's not what you did" (what I did) or you are confused and are thinking the above is where I am saying what *YOU* did? > Stay out of my way if you are not going to be helpful. All you have > done now, is created a fork. You can keep your old dead repo to > yourself. I will continue on as I have outside. I have stayed entirely out of your way - I haven't told you what to do or how to do it etc. > > You have got to be kidding. You can't read. You started to accuse me > > of micromanagement. It has nothing to do with bug tickets. Just > > because one exists doesn't magically make it my responsibility to go > > address it. But that's irrelevant to this. > > That is exactly what you were doing. Yet you will not do such when it > is needed like doing releases for packages that were broken with a new > EFL release. What? I didn't tell you what to do or how to do it. I stopped a segfault from happening it the fastest and most portable way I could think of in about the 30 seconds I spent on it so I can run Ecrire (compiled from our git repos) under Wayland which I could not do before. I'm wondering. Does all programming to you == micro management as it involves details? > Not to mention YOU said to wait for permission from Tom. Which I got > for taking over HIS project NOT YOURS!!!! The point of this was to pave the way to getting git commit access to take over as you have no existing commit access. Taking over maintenance of ecrire is a good reason to get such access. I'd like to see some committment to it first and to see how you do first before granting such access. Wince I now know how you want to behave below... this certainly will never happen (at least until your view of things is adjusted). > Given the FACT you have NEVER commit to that repo ever before. > https://github.com/Obsidian-StudiosInc/ecrire/graphs/contributors > > You have NO ground to stand on what so ever. You have NO legal > ownership. You have no rights as an author. The license is regular GPL > nothing Enlightenment specific etc. Thus you have NO ownership or any > involvement. Back off!!! > > Ecrire is NOT your project. It never has been. Now it definitely will > not be. Nor will I look to ever want to gain access to git.e.org repos. > Not with a crazy tyrant running around. Ok... I think we have our core issue here. You THINK that somehow the ecrire repository legally or morally belongs to a single individual and since you spoke to Tom to take over you believe it belongs to you. It does not. I could read that between the lines of your original mail I responded to and now I have it clear as daylight. First - from a copyright point of view, The fact I have now modified the code gives me legal copyright over that code. Without copyright assignment explicitly done (via a signed legally enforceable agreement), I retain copyright to any code I write... this applies equally for everyone. Not just me. This applies to efl, enlightenment, terminology, rage... any piece of code we have in git. Never have we ever taken a position of "hands off - how dare you touch any code you have never contributed to". That simply is not how we have ever worked. Tom knows this and has been around for a looooong time. Nothing I did is unusual. People do it all the time here. Look at our git repositories and find the vast majority have multiple committers. No one has ever said the above "Back off! XXX is not your project". Ever. This is the exact attitude I detected and this attitude is 100% not acceptable around here. > > Actually I had no idea what you were or were not doing. I hadn't > > looked. But sure... assume away. > > You have a terrible memory. We discussed this on IRC a few times. I > can show you logs. It would be shocking that most everyone in the > community knows Ecrire is being developed again. They likely know I am > doing that. I have been making noise on such on this list going back > several days. Long before that IRC session you speak of. I know you have some github repo with code in it. I did not know what you were doing in that repo with that code. I am not going to the github page and reading the readme.md or cloning it or seeing what is active or not. I haven't done any of that at this point. That's what I mean by "I have no idea". I'm not following it. I hadn't looked yet. I had no idea it was even actively being worked in yet in any serious way. Just because you make noise does not mean I have instantly checked up on everything you do the moment you send an email about it. > How you could miss it, despite our direct conversations. You asking me > to get permission from Tom, thus filing this ticket per your request. > That is simply amazing!! > https://phab.enlightenment.org/T5411 The above. I simply haven't looked. I just know that you have some stuff on github. I am not even sure exactly what is there. I haven't looked. > > Oh you did. WTF do you think "Rather than any of that, sadly Raster > > went and commented out the code." is meant to mean? It's "how dare > > you do anything to this code in your repo! Stop doing it". That's > > precisely what it's saying. > > No what it said was. I care less someone is working on Ecrire. I know > better. I will go in and touch a repo I have never before. Making a > commit, despite it not having any in years. It was wrong on so many > levels. > > But I come back to it was the worst thing to do technically. Removing > function. When YOU should know how to properly code such in your sleep > with your eyes closed.... Time vs. value. I spent maybe 1 minute total on it. Including running ecrire and getting a backtrace... I chose a quick portable fix. I've spent far more time on this email than that fix. My git commit log said it needs to be fixed in a better way, but this will do for now. If you read the log. I knew nothing about what code you may have had related to this issue at all. I didn't look in the grand minute I spent on this. But at least I had an ecrire binary that now worked in Wayland without instantly crashing and so would anyone else building from that repo. Crashes like this are pretty major bugs that generally require an immediate response to get them back to working again. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
