Re: [PHP-DEV] Requiring DCO (Developer Certificate of Origin)

On Fri, Apr 18, 2025 at 11:41 PM Jakub Zelenka wrote: > > Hi, > > We just had some private discussions about the implication of contributing > under pseudonym. This is in general fine and we should not have problem with > it and we actually never verified the contributors so this is possibly >

Re: [PHP-DEV] Requiring DCO (Developer Certificate of Origin)

Hi On Fri, Apr 18, 2025 at 9:04 PM Sai Liu wrote: > > > Jakub Zelenka hat am 18.04.2025 18:37 CEST geschrieben: > > > Hi, > > We just had some private discussions about the implication of contributing > under pseudonym. This is in general fine and we should not have problem > with it and we act

Re: [PHP-DEV] Requiring DCO (Developer Certificate of Origin)

On Fri, Apr 18, 2025 at 7:53 PM Niels Dossche wrote: > Hi > > I have a strong suspicion of why this comes up now, but would still like > to have more openness on why this is suddenly needed. > This just seems like an extra barrier and extra work. > Since this is a policy change, doesn't this need

Re: [PHP-DEV] Requiring DCO (Developer Certificate of Origin)

  Jakub Zelenka hat am 18.04.2025 18:37 CEST geschrieben:     Hi,   We just had some private discussions about the implication of contributing under pseudonym. This is in general fine and we should not have pro

Re: [PHP-DEV] Requiring DCO (Developer Certificate of Origin)

On 18/04/2025 20:10, Marco Aurélio Deleu wrote: > One can argue that this isn’t a policy change but rather just tooling to help > enforce a policy already in place:  > https://www.php.net/license/contrib-guidelines-code.php > Hi Are you

Re: [PHP-DEV] Requiring DCO (Developer Certificate of Origin)

Marco Deleu > On 18 Apr 2025, at 14:54, Niels Dossche wrote: > > Hi > > Since this is a policy change, doesn't this need an RFC as well? > > Kind regards > Niels One can argue that this isn’t a policy change but rather just tooling to help enforce a policy already in place: https://www.p

Re: [PHP-DEV] Requiring DCO (Developer Certificate of Origin)

Hi I have a strong suspicion of why this comes up now, but would still like to have more openness on why this is suddenly needed. This just seems like an extra barrier and extra work. Since this is a policy change, doesn't this need an RFC as well? Kind regards Niels

Re: [PHP-DEV] PHP True Async RFC Stage 3

Hi Edmond! On Wed, Apr 16, 2025 at 7:02 AM Edmond Dantes wrote: > Good day, everyone. I hope you're doing well. > > I’d like to introduce the RFC for the True Async component. > > https://wiki.php.net/rfc/true_async > > This time the work took longer because I was exploring different > architect

Re: [PHP-DEV][VOTE] Add grapheme_levenshtein function

2025年4月17日(木) 16:16 Tim Düsterhus : > > Hi > > Am 2025-04-16 02:40, schrieb youkidearitai: > > The RFC for add grapheme_levenshtein function has been accepted. > > (Yes 12 / No 0) > > > > Thank you very much for voting. > > I will go to implementation. > > Great, thank you! I noticed that while you

[PHP-DEV] Requiring DCO (Developer Certificate of Origin)

Hi, We just had some private discussions about the implication of contributing under pseudonym. This is in general fine and we should not have problem with it and we actually never verified the contributors so this is possibly happening already. The only thing about it is that it might raise ques

Re: [PHP-DEV] PHP True Async RFC Stage 3

Good day, Deleu! > What happens if the coroutine didn't finish execution? does `disposeSafely()` means that it will wait until completion to safely clear it up or does it mean it will attempt to dispose and throw an exception if it fails to do so? Cooperative cancellation implies that a coroutine