On 05/16/2017 07:09 AM, Vincent Torri wrote: > https://ffmpeg.org/developer.html#Code-of-conduct >
I don't think a code of conduct is really necessary here, my reading of this thread having spent some time talking to William on IRC in the prior is that if people communicated with some care none of this would have ever happened. I'm going to call people out here because they should know and do better. Raster your communication in this thread has been that of an utter jerk I don't think I missed anything but there was absolutely no reason why you should have started using the language and tone you did. Had you written one clear email better outlining the way the project works in a nicer tone i'm guessing this would be resolved and there would be no issue. An example of this could be yes any developer may push a simple work around fix to any repo as they see it (although if they are not active there its best to first check with someone who is) at a later date if someone comes up with a better fix they can just revert the temporary fix. Had you communicated with me in the way you communicated with William when I first joined the project I wouldn't still be here now. From everything i've seen William seems like a decent person with good intentions who has seen a problem (the lack of a decent simple text editor for enlightenment) and is trying to fix that problem we really should be encouraging people like that not putting them off. We have often spoken about ways to get people better engaged with the community both from inside and outside Samsung, what you have done in this thread is taken someone who was actively trying to get involved in our community and turned them away, which is really quite disappointing. I know your busy at TDC but I suggest that once your back you should go out of your way to try and repair the situation your poor communication has caused. There is nothing wrong with the action you did in commenting out some code (within how we tend to work as a community) but your communication around it absolutely stank. I'm also going to call out Stephen because in this thread you simply acted like a Jerk without adding anything of meaning to the discussion. To finish let me be clear if someone comes in here acting like an arse I have no problem with them being put in there place and sent away our community shouldn't have to tolerate people being arses, but in this case there was someone doing there best in good faith to do everything right by the community and they were treated appallingly by senior members of our community for no good reason and thats just not on. Now it would be nice if those involved took a step back and had a think about the way they've behaved and then deal with this again in a few days and hopefully come to a better resolution. Personally i'm looking forward to using ecrire and shipping it in openSUSE. > > On Mon, May 15, 2017 at 10:02 PM, Andrew Williams <a...@andywilliams.me> > wrote: >> Hi Team, Friends and Community, >> >> Can we please take a breath, think about how we would like to be thought of >> and consider this when we fire out emails to this list. We are a community, >> a diverse community at that, and I love it - there is something for >> everyone independent of interest, background or experience level. >> >> Looking at this email thread I am worried. Not for any particular message >> but because of the general inclination to forget that, as a community, we >> are all looking to progress the libraries, APIs and applications that >> encapsulate our understanding of what a great environment can be. Can we >> all please step back for a moment and see the good intention or reasoning >> behind the communications rather than what seems to be the reverse. >> >> Words like ownership, blame, fault and rights do not befit a community that >> has developed for so long as ours to embrace contribution from so many >> angles. I for one want to feel that we are, without exception, >> communicating in a way that we think is an example of how we would like >> others to consider approaching ourselves. Exclusive rights do not exist - >> everything we do is collaborative and at times we must resolve conflicts >> and merge multiple streams of development - that is life and it's a great >> thing to progress and deliver meaningful products for a wide community. >> >> I understand that many of these messages come from personal passion or from >> deep understanding of what we want to do - but as these are largely >> internal factors we must strive to understand both to progress forward. Can >> we please do more to understand each other as we discuss where >> understanding may be lacking or assumptions are not accurate? >> >> Imaginging for a moment if I were a completely new comer to this community >> and I saw such a discussion I would certainly be disheartened and may fail >> to get far enough to see the fantastic tech and possibilities that EFL >> should be bringing to the world. >> >> Thanks for taking the time to read, I appreciate it and hope that some >> reflection could help us to better build on the work of those both internal >> and external to the core project. >> >> Looking forward to Malta - a beer is always great for grounding >> conversation :) >> Andy >> >> On Mon, 15 May 2017 at 20:14 William L. Thomson Jr. <wlt...@o-sinc.com> >> wrote: >> >>> At this point in time. I have no interest of gaining access to >>> git.e.org repositories. I will continue any and all EFL application >>> development outside. >>> >>> I will consider my work going forward on ecrire to be a fork. I may >>> rename it and other things. I really haven't the time for the >>> mistreatment or the back and forth. >>> >>> If this is how new contributors are treated. It really explains why so >>> few things are in EFL. I am questioning how crazy I am to stay and not >>> run from this community. Though I will not hold all responsible for the >>> actions of the main person. I do not need to subject myself to such. >>> >>> Sadly I can see that leadership has already trickled down into some. It >>> is really bad all around. That people who work for Samsung conduct >>> themselves that way in public.... >>> >>> On Mon, 15 May 2017 12:44:34 -0400 >>> "William L. Thomson Jr." <wlt...@o-sinc.com> wrote: >>> >>>> On Mon, 15 May 2017 16:28:30 +0000 >>>> Andrew Williams <a...@andywilliams.me> wrote: >>>> >>>>> Hi William, >>>>> >>>>> I'm glad that is now resolved, thanks for figuring it out. >>>> >>>> Sure, I was already working on it when all the discussion came up. >>>> Which is why I commented on others committing. Does not make sense for >>>> more than one to work on same problem without discussion or >>>> coordination. >>>> >>>>> Back to the main topic of the thread - is your intention to get this >>>>> merged back up to master on git.e.org? I think that will affect the >>>>> coding style etc expectations and so forth, so I was interested in >>>>> the overall plan :) >>>> >>>> Merging back into the old repo on git.e.org was the intention. I >>>> believe I am following most if not all coding styles etc. Though maybe >>>> some places that could use some correction. The code is at least as >>>> good as what is in that old repo. >>>> >>>> How things proceed is up to others. I am continuing on with my >>>> development effort. It is pretty moot to me. For now could look to >>>> pull my changes into that repo and do that automated daily, etc. >>>> >>>> Beyond that not sure. Still concerned with working in public repos if >>>> people will just commit without any coordination or discussion with >>>> others. Otherwise I have no issue with my effort being pulled back >>>> into main repo. As for any direct commit access, that is rather moot >>>> for me. >>>> >>>> That is more if you all want the development to be official or third >>>> party effort to develop ecrire. It is up to you all to decide. My >>>> only thoughts are, if my work is being merged back into ecrire >>>> git.e.org repo and I do not have direct commit access. I would not >>>> want others working in that repo. I will not be pulling just pushing >>>> to git.e.org for any syncing. Just something to keep in mind. >>>> >>> >>> >>> >>> -- >>> William L. Thomson Jr. >>> -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
