contributor_covenant VS PHPT

While you are free to write your own or adopt one from another repository, project, or organization you respect, there exists a code of conduct written and maintained by the community known as the Contributor Covenant.

Many Open Source projects have adopted the Contributor Covenant as their code of conduct. Check this page to see a list of adopters.

https://www.contributor-covenant.org/ is (was?) the most widely adopted code of conduct in FOSS, initially drafted by a Ruby contributor, who also happens to be transgender if that's pertinent information to you. It's the genesis seed from which all this code of conduct madness stems from. Personally I'd stick with "be excellent to each other" or "say what you want, just don't insult other contributors" or something vague, ambiguous and universally understood as that. I'm not really a fan of rigorous social rules, so my view on this starts from that position.

You can adapt the guidelines provided by https://www.contributor-covenant.org/ to create your guideline.

The Contributor Covenant that the maintainer removed to "reclaim polymc from the leftoids" was added in February: https://github.com/PolyMC/PolyMC/pull/178. You can view a list of other communities that have adopted the covenant on their website.

For reference, the Code of Conduct they used is basically the same as this one: https://www.contributor-covenant.org/

Please follow the Contributor Covenant

As your audience grows, it is vital that you define clear rules to create a safe environment for everyone to participate. A common way of doing this is to define a code of conduct (CoC), which sets some basic guidelines on what kind of community interaction will not be tolerated. We decided to stick to well-established frameworks and based our CoC on the Contributor Covenant.

Those aren't the only ways I could see things happen, but that represents a few points on the spectrum. Having been participating in the English Wikipedia community since the early days, I know that collaborative writing on a worldwide scale is hard, and leads to misunderstandings and hurt feelings. Hence the reason why things like the Contributor Covenant came out, and why Linus Torvalds took such a long time accepting something. Note, things labeled "Code of Conduct" and "Contributor Covenant" are one small slice of governance. Dealing with things like the ideal public transit system create a massive extra layer of complexity. Governance, in general, is difficult.

In our latest story we show a couple of smart ways to get around some import conflicts in PHP.

The values [0, 15] represent 16 possible values, which is a power of 2.

The correct way to get an unbiased distribution from a sample of 2^x to a modulo that is not an even power of 2 is to use rejection sampling.

This is what RFC 6979 says to do https://datatracker.ietf.org/doc/html/rfc6979#section-3.2

But you can also see this technique in CSPRNG code; i.e. https://github.com/php/php-src/blob/d40726670fd2915dcd807673...

I am running this code on MacOS on Apple Silicon hardware which is crashing when using the JIT in a ZTS build of PHP, so the 1m 35s result is without JIT, it might be even faster if I could use it

49. PHP - $58,899

A little about me; I'm a web developer and have been for around 5 years, though I'd dabbled for years. I have experience with Perl and PHP but my day to day is JavaScript/TypeScript be it through NodeJS or ReactJS. I want to learn Rust for no specific reason other than it's fun to learn new things.

Consider a web application where requests are handled through NGINX as the web server and PHP as the dynamic backend language. Let’s say something in the application logic results in a fatal error or process termination. This doesn’t affect NGINX’s ability to serve a response to the client, which would most likely be an HTTP 503 - Service Unavailable message.

In the beginning, I used a technology called CGI to develop server applications written in Perl. This technology was later replaced by Microsoft’s ASP (Active Server Pages) and then PHP. PHP, which you may already know, is still powering over 77% of all the websites as of the time of writing (ever heard of WordPress?).

PHP

As Shopware is mostly based on the Symfony framework, which is in turn based on the PHP language, we should also consider learning about the basics, which will also be useful for other frameworks apart from Shopware, like Symfonycasts, symfony.com, php.net.