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. Cheers, 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
