On 01/10/13 14:58, Yossi Kantor wrote: > On 10/01/2013 02:20 PM, Tom Hacohen wrote: >> On 01/10/13 12:47, Tom Hacohen wrote: >>> On 01/10/13 12:06, Michael Blumenkrantz wrote: >>>> On Tue, Oct 1, 2013 at 11:51 AM, Tom Hacohen >>>> <tom.haco...@samsung.com>wrote: >>>> >>>>> On 01/10/13 11:38, Michael Blumenkrantz wrote: >>>>>> is this a joke? I'm giving him access to work on E, which he HAS been >>>>> doing >>>>>> publicly for months. He's been mentioned on the release blog and his >>>>>> commits are easy enough to find; given that I'm the (only) maintainer for >>>>>> the project, that's more than enough justification. I guess I could >>>>> discuss >>>>>> it with the rest of the developers/maintainers of the project a bit >>>>> longer, >>>>>> but I do enough talking to myself as it is. >>>>>> >>>>>> Don't throw a tantrum just because you got screwed by security today. >>>>> That's not how we work and you know it. Chris is the maintainer of that >>>>> made up library he's working on, and yet, we didn't give access to his >>>>> progeny. This is complete bullshit. >>>>> >>>> As I said in regards to that: >>>> >>>> I don't support giving commit access to unknowns based solely on their >>>> place of employ or "future" work. This is clearly a different case, as the >>>> person in question has been doing work publicly as well as being available >>>> for others to contact on IRC. Hardly an unknown. >>> No it's not, 4 commits are not enough as a proven track record. It's an >>> unknown. Also, I'm sure that if you'll ask people on the ML, no one will >>> know the nick or the name, except for JackDanielZ. >>> >>>> >>>>> Also, yeah, he's been fixing bugs in E for months, with a total of 4 >>>>> commits. >>>>> >>>> Simple fact is that a number of his patches came to me a day or two after >>>> I'd already fixed the issue because of miscommunications. Regardless, this >>>> is still far more commits than I had under my belt when I joined. >>> Well, as I've said, we haven't seen them here, as he haven't sent >>> anything to the ML. >>> All we know now is that it's a guy that doesn't know how to work with >>> open source (or maybe he does, I don't know, as I know nothing about >>> him), haven't seen any of his commits and know nothing about. >>> >>> His first 3 commits change almost no lines, and the last 2 change >>> indentation so it's hard to see. >>> >>> You getting access without any commits under your belt means nothing for >>> this discussion. >>> >>>> >>>>> Yes, you can discuss it with the rest of the developers, for example, >>>>> everyone mentioned in the "about" dialog would be a start. >>>>> >>>> Okay, so you're saying I should spend the next few months chasing down >>>> people who are long gone from the project or no longer actively develop on >>>> it. >>>> >>>> >>> No, I'm saying you should send to the ML, as all the active developers >>> from the about dialog will be there. >>> >>> See for yourself, nominate him for commit access, wait a few days, and >>> see what people think. >>> >> Btw, let me just clarify something. My problem is less with him getting >> access, and more with you not asking. >> >> -- >> Tom. >> >> >> ------------------------------------------------------------------------------ >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >> the latest Intel processors and coprocessors. See abstracts and register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk >> _______________________________________________ >> enlightenment-devel mailing list >> enlightenment-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > Hi Tom. > > 1) I'm reading this thread also. If you object Zmikes decision (and its > your full right), do it in a private correspondence. Its just (basic) > manners. > 2) Yes, I don't send a patch for every letter I type in the code. Some > of those patches are week and a half of digging in a new code and > finding a best solution > (Actually the last paches are fixes for e_fm selection which are a > complete and unusable mess not attended by anyone so far). Last time > I've checked software engineering was measured by quality (But hey, > thats just me).
Hi Yossi, This email just reinforces what I said about the lack of understanding about how open source works. 1. No. Just no. It has nothing to do with manners, and this is in every way and form not how open source works. You do such things in the open, for every one to see, not some back channel discussions. If I had said anything about you it would have been a different matter, but I didn't mention anything about your abilities, just about Mike's handling of the situation. 2. You shouldn't send a patch for every letter you type in the code, surely, and I do appreciate you digging in and looking for the right solution (which indicates you are probably good). Furthermore, your contributions are appreciated (wrt the e_fm selection). More specifically, you have fixed a bug that really annoyed me. I agree that software engineering is measured by quality, however trust is measured by quantity. Commit access is more about trust than capability. My point is and was, that no one knows you. Daniel and Yakov know you. I have met you in person, and actually looked at some of your commits. Mike has looked over your patches. But that's it. No one else knows you. -- Tom. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
