Good news. I appreciate your understanding! -Hannes
On Tue, Jan 21, 2014 at 12:11 PM, Pierre Joye <pierre....@gmail.com> wrote: > I stop now this discussion. I am not here to get constantly insulted. And I > even less inclined to repeat the same thing over and over as you obviously > not read my replies carefully. > > Enjoy your day still, > > On Jan 21, 2014 9:06 PM, "Hannes Magnusson" <bj...@php.net> wrote: >> >> On Tue, Jan 21, 2014 at 11:22 AM, Pierre Joye <pierre....@gmail.com> >> wrote: >> > On Tue, Jan 21, 2014 at 8:14 PM, Hannes Magnusson <bj...@php.net> wrote: >> >> On Tue, Jan 21, 2014 at 11:08 AM, Pierre Joye <pierre....@gmail.com> >> >> wrote: >> >>> On Tue, Jan 21, 2014 at 7:58 PM, Hannes Magnusson <bj...@php.net> >> >>> wrote: >> >>> >> >>>> Just because the people behind the tool have php.net accounts does >> >>>> not >> >>>> mean that a tool developed outside the php.net domain is >> >>>> automatically >> >>>> php.net property. This is not a corporate world that screws you over >> >>>> and you have not signed any contract with php.net forcing all your >> >>>> development to become php.net work. This is open source. >> >>> >> >>> This is total bullshit and I won't even try to argument how wrong it >> >>> is. >> >>> >> >>>> If the idea is to make it a PHP property, then we can import the >> >>>> github repo to git.php.net. That should be easy enough. Then karma >> >>>> and >> >>>> all other php.net rules of engagement will apply. >> >>> >> >>> That's not a problem and should not prevent us to publish the results >> >>> to qa.php.net as many developers and RMs requested it. >> >>> >> >>> I will ping David or Tyrael to import the repo from github and that >> >>> should solve your only issue. >> >> >> >> >> >> Why couldn't you just have replied with "Sounds good, lets import it >> >> to git.php.net!" to the first mail rather then being such an asshole? >> > >> > Please take care of your tone. >> > >> > And I did, also you forgot that this project is many years old, way >> > before we even had travisci support or the like. We have been testing >> > all commits and releases using it and provided critical feedback since >> > then. Back then git was not available in php.net and we were not >> > willing to deal with svn, just like many pecl extensions. Arguing >> > about code not being under git.php.net was a non issue, sorry. >> >> >> How is any of this related to a) you being an asshole or b) this >> project not being developed under php.net? >> >> There are literally millions of projects that are outside of php.net >> and that is awesome! The more the better! >> >> The more datapoints we have, the better! >> Matt and buddies have receieved requests to make these datapoints >> public because it was not available to php.net developers that would >> like to get their hands on it - because it wasn't developed as a >> php.net project. >> Although it may have been used by a specific group, that also has >> affiliation to php.net, there is a clear distinction. >> >> Now it seems like the project would like to join the php.net umbrella >> and that is fantastic news! >> >> With you however being an asshole and arguing unrelated crap as usual >> is not helping anyone and you should stay away and let the adults >> talk. We were doing just fine before you joined this thread. >> >> >> >> >> >> Things become much easier when you act like an adult - not to mention >> >> how massive waste of time your attitude brings. >> > >> > Excuse me but your constant opposition and FUDs spreading about >> > "corparates", "non contributors" and other totally respect-less >> > replies to the various php.net lists cause more damage than anything >> > else. And as soon as you do it with one of the guys I work with (be >> > professionally or in my free time), I will jump in the discussion and >> > put the things back to their (right) place. Whether we like it or not >> > is not really relevant. >> >> >> What is wrong with you now? >> You suddenly believe that the work of everyone that has contributed to >> php.net to be a php.net project? >> Of course not. >> Most php.net contributors have plenty of other projects they are >> working on. It doesn't make those projects php.net projects. While >> developed outside of php.net umbrella there is no way php.net will be >> forcing its pov over anything. >> >> If the authors would however like to move the project into php.net >> umbrella then fantastic! >> >> >> >> > >> > Now, if any of my replies has been insulting, please accept my >> > apologizes. But I don't see any insulting replies but facts being >> > presented in an objective (and somehow direct) manner. >> >> Great, then we agree! Thanks for you understanding in this matter. >> >> >> However, since you don't have single commit to the repo, you cannot >> force Matt to move his project to php.net >> https://github.com/OSTC/PFTT2/graphs/contributors >> >> If Matt would like us to import the repo, then I'll do that right away >> and make sure he has karma to qaweb and whatever else he needs to work >> on the integration. >> >> -Hannes -- PHP Quality Assurance Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php