On 09/09/13 13:51, Tom Hacohen wrote: > On 09/09/13 13:48, Christopher Michael wrote: >> On 09/09/13 13:16, Tom Hacohen wrote: >>> On 09/09/13 13:14, Stefan Schmidt wrote: >>>> Hello. >>>> >>>> On 09/09/2013 01:06 PM, Tom Hacohen wrote: >>>>> On 09/09/13 12:26, Daniel Juyung Seo wrote: >>>>>> On Mon, Sep 9, 2013 at 7:32 PM, Christopher Michael >>>>>> <cp.mich...@samsung.com>wrote: >>>>>> >>>>>>> On 09/09/13 10:22, Tom Hacohen wrote: >>>>>>>> On 09/09/13 08:45, Michael Blumenkrantz wrote: >>>>>>>>> I think I'd like to see patches being submitted/reviewed on the >>>>> mailing >>>>>>>>> list at the least before giving blanket commit access because a >>>>> person's >>>>>>>>> work fits our requirements or is something that is "needed". >>>>>>>>> >>>>>>>>> I don't really want to get into a scenario where, as a >>>>>>>>> community, we >>>>>>> give >>>>>>>>> people commit access because of who their employer is or what >>>>>>>>> they're >>>>>>>>> working on and not because they've proven that they can write good >>>>> code >>>>>>> and >>>>>>>>> fit into our workflow, and this seems to be where we've been >>>>>>>>> heading >>>>>>> lately. >>>>>>>>> >>>>>>>>> Nothing personal against this person in particular, but I've never >>>>>>> heard of >>>>>>>>> them or seen any code/reviews/fixes/documentation in relation to >>>>>>>>> the >>>>>>>>> project by them. >>>>>>>>> >>>>>>>> >>>>>>>> I completely agree, word to word. >>>>>>>> >>>>>>>> -- >>>>>>>> Tom. >>>>>>>> >>>>>>> >>>>>>> Double standards are fine. No worries. We can move the code to github >>>>>>> and work from there. Not an issue. >>>>>>> >>>>>> >>>>>> Well yeah I thought the same. >>>>>> He is supposed to work on private and even invisible project and >>>>>> its not >>>>>> even related to the efl repos. >>>>>> Then github must be the right place. >>>>>> >>>>>> Don't get me wrong. I know him in person. But he needs more time and >>>>> effort >>>>>> to get an access. >>>>>> Thank you. >>>>>> >>>>> >>>>> On a semi-related topic: this project should not be private and >>>>> invisible. >>>> >>>> Feel free. You are one of the few people who can actually do that. We >>>> used it as a convenient place for collaboration before we could make it >>>> public. But if it moves somewhere else anyway it might be fine to just >>>> delete it afterwards. >>> >>> Yeah, I can technically do it. Last time I wanted I faced objections. >>> Anyhow, let's wait to see exactly what happens with it's location and >>> I'll act accordingly. >>> >>> -- >>> Tom. >> >> Well, I can already tell you what will happen ... it will move to Git >> Hub for now. The developer working on it needs the ability to make >> changes to it ... so it has to go somewhere that he has push rights on it. > > That's good. So please let me know when I can remove the private NSA > copy from our servers. > > -- > Tom. >
Any time you want to .. assuming you are not too busy :P dh ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
