wouterj

wouterj, 8 days ago

@ramsey what exactly do you want to use of AssetMapper?

It's basically a very thin wrapper (CLI commands, twig functions) to ease generating an importmap. And this integration also automatically versions assets.

I've not used AM in either Symfony or non-Symfony application, but I guess I would just generate the importmap manually in that case (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap).

wouterj, 18 days ago

@imperator @pollita see https://externals.io/message/122213#122236

wouterj, 25 days ago

@welcomattic this is a bit of misinformation unfortunately. As far as I know, it doesn't affect the PHP engine.

You can be affected by the bug in glibc if you're using the PHP iconv extension though (and enabled ISO-2022-CN-EXT in glibc).

Afaik, glibc is dynamically linked by PHP so what you need is to upgrade glibc to a patched version (which most distributions provide by now).

https://phpc.social/@heiglandreas/112319156714872060

wouterj, 1 month ago (edited 1 month ago)

@heiglandreas I might be missing something here, but these two are not in the same problem field, are they?

Symfony has a PropertyInfo component for years, which uses PHPstan and phpDocumentor's type packages (the one you're linking here!) to resolve property types. This component used to have a single Type DTO class representing all type information.

Last year, some community members proposed the TypeInfo component as a better replacement for this Type class (https://github.com/symfony/symfony/pull/52510).

wouterj, 1 month ago

@jaapio @heiglandreas yes, I saw it later this morning.
Let's keep talking and see where our needs overlap and we can work together, just like on the rst parser.

wouterj, 1 month ago

@jaapio @heiglandreas I just always get very triggered by people mentioning NIH in Symfony.

For me, it feels like we get accused of having a secret plan to get all PHP packages to start with "symfony/" in some years.

From working in this group, I know this is not the case and we're all just eager to write code and publish features (+ save ourselves maintenance time). Most of our discussions happen in the open on GitHub and we have no secret bad intentions to any individual on this world.

wouterj, 1 month ago

@jaapio @heiglandreas I realize this sometimes isn't the feeling that we get across.

Async communication, and textual async communication in particular, looses a lot of emotion and can result in bad feelings for people reading them.

Please reach out to us if this is the case, like you did. We'll learn from it, be better at communication in the future, and create new contacts with the PHP community for the better of everyone.

wouterj, 1 month ago

@heiglandreas I agree, let's become more converging as a PHP community and ping authors of relevant packages in the community reviews (if we know them ofc).

That said, I think this also applies to how we deal with it afterwards. Messages like your first post often result in a more diverging community. Let's try to understand, from both sides, and not shoot one-liners. People reading the message don't know about those "great chats" and will only remember Symfony being the bad guy.

/cc @jaapio

wouterj, 1 month ago

@Skoop the reality is that there is very little plan. If we say we don't have a roadmap, we mean it :)

For those announced at conferences, the component is just as much as a surprise for you as it is for the core team (I'm also totally not sure if that's a good thing!)

For all other components, the first time we hear about it is when the PR with a draft idea is opened. This applies to components created by core team members, and by ones created by community members.

cc @heiglandreas @jaapio

wouterj, 1 month ago

@Skoop @heiglandreas @jaapio to illustrate and be totally open about this: at the moment we have a couple components that we consider for future Symfony versions on GitHub. All of them are initiated outside of the core team (just like TypeInfo was) and currently in review, test and mature phase:

https://github.com/symfony/symfony/pull/51741
https://github.com/symfony/symfony/pull/51718
https://github.com/symfony/symfony/pull/54013
https://github.com/symfony/symfony/pull/53213

wouterj, 1 month ago

@dantleech I would expect GIS tooling, like QGis, to be able to do this. But be warned: this is yet another deep hole that has the potential to sink lots of hobby time 😅

wouterj, 1 month ago

@dantleech ah, didn't realize you were looking for something to script (I know, I could have known better).

I've made map PNGs with R and Python in the past, but that was so much copy-pasting things that I can't even recall which libraries I used. And you also need to parse gpx, although that shouldn't be too hard.

wouterj, 1 month ago

@ocramius at Symfony we use git notes for this: https://git-scm.com/docs/git-notes

Upon merging, the PR discussion is copied into a git note and attached to the merge commit.

Cc @heiglandreas @dantleech

wouterj, 1 month ago

@pierstoval @heiglandreas @ocramius @dantleech indeed, we do all merges using a small internal tool (which also checks CI checks, approval rules, etc.).

This tool uses the GitHub API to get all PR comments, dumps them to a ".notes" file and adds this file as a git note: "git notes --ref=github-comments add --file=./.notes"

wouterj, 1 month ago

@derickr @afilina @ramsey exactly this. I don't want to quit my day job, so giving me money won't help me with time management (assuming I was the sole maintainer of a package).

I feel like the best way to help these maintainers is to help them with all the "chore work" (packaging, releasing, handling CVEs, doing regular security audits, etc.).
I feel like foundations should be the driver for this, and companies should invest in these foundations (but I know it's much easier said than done)

wouterj, 1 month ago

@rob @jaapio as many others have also said, I think this is logical for projects like this.

It's no longer "innovative", there aren't many changes and as a result very little visibility for projects like this and their contributors.

wouterj, 1 month ago

@rob @jaapio I'm afraid the only way to help these packages is by having contributors that do not do this because they want it, but because they are paid to do it.

However, even if companies know their full supply chain, they can't possibly help maintaining all their dependencies up to this deep. It's a very hard problem to tackle...

wouterj, 1 month ago

@rob @jaapio I 100% agree with this.

However, you are much more likely to become a maintainer in projects with a lack of contributors in the first place (although I realise I've literally grown up inside a very extreme bubble where there is an abundance of maintainer-worthy people).

Which is why I believe foundations/companies can play a crucial role in the social side of things here, as they can help removing the need to recruit new maintainers in the first place by assisting the maintainer.

wouterj, 1 month ago

@Crell @cam it's great news though: https://compose-spec.io/

This would mean you can potentially use the same compose config to run an application using Docker, Podman, and maybe even a k8s variant.

wouterj, 3 months ago

@codito you learned about the contribution process though, which will help you next time you contribute.
My first Symfony fix was fixing a variable name in a documentation example 😅

wouterj, 3 months ago

@sebastian I gathered the information per line using find+git-blame.
The data analysis is done with a small PHP script that generates JSON.
Finally, the diagram is rendered as SVG by some custom JavaScript code.

I might one day streamline the process more and publish it to GitHub.

wouterj, 3 months ago

@thepanz this is a PR I'm preparing for Symfony. The scrollbar code is incredibly badly written at the moment. Once it's cleared up and the last bugs are fixed, I'll open a PR.

The list itself is a decoupled class, which you should be able to use for your use-case as well (actually, I was planning on improving Symfony's autocomplete question feature using this class as well in a future PR).

wouterj, 3 months ago

@graphite thanks!

The colors are from a list of HTML colors supported by browsers. Unfortunately, graphite is not yet one of them