Hello, On Tue, Dec 30, 2014 at 11:05 AM, Daniel Zaoui <[email protected]> wrote: > Firstly, I would like to tell it is not personal. I don't have anything > against Jaehyun. > > There was a mail > <http://sourceforge.net/p/enlightenment/mailman/message/28293302/> a > long time ago from Mike (maybe there is an updated version) concerning > the commit access. Imo, the most important points are communication (by > mail and chat) and an area of expertise. I don't feel these conditions > are filled.
I disagree with you here. Not every body has time to spend in every corner of our communication tool. What is important is that people do not feel like they are in charge of just there little corner and are willing to fix issue as they see them. In that aspect Jaehyun as prooved over time that his is willing to contribute in any area where he is see issue. Check 'git log --author "Jaehyun Cho"' to see that he did contribute to a lot of different place with small and bigger fix in efl itself. I am strongly supporting the proposal for him to be get a developper access. > According to Hermet and D1 mails, it seems that the promotion is mostly > motivated for Enventor. I don't think this is a sufficient reason to > request a commit access on all the repositories of the project. I > strongly think we should have commit access per repository. The repo > maintainers could approve in private if they see that someone that > annoys them is good and enough responsible. I don't like that development model. It create barrier for people to help in other area. So when you find a small bug that would be maybe easy to fix, you are not going to chase it, because you can commit a fix directly. Instead you are more likely to create a task and wait for someone else to fix the issue. I do think that once someone is recognized as a developer, he has to feel like he has responsibility for all source, not just his little corner. I think it is important that people when they use a tool, see a warning can easily fix it and benefit of the post review process. Of course if they make to many mistake we can revoke their developer access, but that has never happen so far and I am willing to trust people will to do the right think and fix quickly stuff when they bork things. > It may be a big change and a lot of work for Tom (+1 :P) but I really > think it is mandatory as we have more and more applications and tools > that are not related to the core. Good point, so it won't ever happen :-) -- Cedric BAIL ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
