[06:34:55] tgr_: in fact, i originally did use ConfigRegistry, but config registered there is inited VERY early, so I ended up not using it (so I would have MW that can access its pages). [06:36:07] (that is, unless ConfigRegistry in extension.json is sth else than you're talking about) [09:50:02] tgr_: I'm curious how, when and where exactly you combine "community config" maintained on the wiki page with config that can't be edited by the community. [09:50:47] I'm particularly trying to get an idea how this approach could work for a set of configuration variables across various core components and extensions. [09:52:17] I'm currently thinking that we want some kind of "mix-in" logic for configuration. The idea to load disjunct config sets from different sources really isn't very helpful. We need to be able to mix and match... [09:55:35] urbanecm: it would be very helpful for me to see an outline of the ideas behind ConfigRepository written down somewhere. It would be important for me to understand the ideas and requirements, so we can consider them when re-designing how we load configuration [09:55:53] (spoiler: global variables are going to go away) [12:00:28] From the Node.js project leaders, working on the worlds most popular programming language: "JavaScript occupies a relatively unique space. It is ubiquitous, yet very few companies are willing to substantially invest time, energy, and resources into it despite their reliance on it." - https://nodejs.org/en/blog/announcements/retiring-the-node-js-community-committee [12:26:10] Krinkle: what does that mean for people with nodejs installed as part of npm and stuff [12:26:52] Oh it's just a community thing [12:26:55] I should read [12:27:50] They are merging two decision making groups for the maintenance of the Node.js platform. [12:28:11] It affects developers that work on node itself [12:28:32] It does not (directly) affect the people using node to make their own software [12:29:30] But my point was to highlight perhaps the surprise that something so popular is short on people being available to lead its direction. It's small number of people (<10) doing most things [12:31:03] Not unlike PHP, which is also hugely popular (>70% of websites by some measures), and also had relatively few companies publicly and consistently investing [16:18:56] Sadly a common story in opensource. [16:21:20] duesen: we just keep a list of configuration keys which can be overridden by on-wiki configuration. They fall back to the PHP confiugration as a default, but there's no combining beyond that. [19:14:20] tgr_: ok, thanks! I guess that works for most things. I'm wondering how to make it work for things like group permissions...